When we create a new bucket we add permission to the new bucket using AWS Identity and Access Management (IAM) console. I will show you our S3 policy below.
After creating new bucket named ‘new.bucket.test.bdrive.com’ we added following lines to the policy which attached to the s3 user account we are using on NetDrive.
{
"Version": "2012-10-17",
"Statement": [
{
"Sid": "VisualEditor0",
"Effect": "Allow",
"Action": [
"s3:ListAllMyBuckets",
"s3:GetBucketLocation",
"s3:CreateBucket" <<<-- need this to create new bucket
],
"Resource": "*"
},
{
"Sid": "VisualEditor1",
"Effect": "Allow",
"Action": "s3:ListBucket",
"Resource": [
"arn:aws:s3:::bdrive_unittest_root",
"arn:aws:s3:::nd-region-test",
"arn:aws:s3:::nd-test-eu-west-1",
"arn:aws:s3:::nd-test-frankfurt",
"arn:aws:s3:::netdrive-test",
"arn:aws:s3:::test.bdrive.com",
"arn:aws:s3:::test.netdrive.net",
"arn:aws:s3:::new.bucket.test.bdrive.com", <<<-- added permission to new bucket
]
},
{
"Sid": "VisualEditor2",
"Effect": "Allow",
"Action": [
"s3:PutObject",
"s3:GetObject",
"s3:DeleteObject"
],
"Resource": [
"arn:aws:s3:::bdrive_unittest_root/*",
"arn:aws:s3:::nd-region-test/*",
"arn:aws:s3:::nd-test-eu-west-1/*",
"arn:aws:s3:::nd-test-frankfurt/*",
"arn:aws:s3:::ndtest-yammer-attach/*",
"arn:aws:s3:::netdrive-test/*",
"arn:aws:s3:::test.bdrive.com/*",
"arn:aws:s3:::test.netdrive.net/*",
"arn:aws:s3:::new.bucket.test.bdrive.com/*", <<<-- added permission to new bucket
]
}
]
}
With this permissions added we can access the newly created bucket immediately.
Would you please check you already have necessary permissions set on the policy which is attached to the S3 user you use on NetDrive?
In the other hand if you already set the permission it’s somewhat strange that you can only access the bucket after 4-7 hours. If you do not have permission it’s not possible to access the bucket even after 4-7 hours.