Cannot Add folders/files to S3 newly created buckets

NetDrive3
1

NetDrive version: 3.7.687
Windows/Mac Version: Windows Server 2012 R2

I’m able to connect to my newly created S3 bucket but I’m not able to browse to any of the subfolders. They aren’t listed as an option when mounting. Additionally, when I browse the mounted drive I do not see them.

This may be related or may be a separate issue, but when I try to create a folder in the mounted S3 drive I get the following windows error:
Error 0x8000FFFF: Catastrophic failure

I’m able to add a file without an error but it doesn’t actually save to the bucket.

After about 7 hours it starts working fine… My old NetDrive version 3.6.548 - works fine with newly created bucket. Please investigate. You can find attached logs in Verbose mode. Thank you!
logs.zip (143.1 KB)

2

Hello

We will review the log files soon, then let you know the result.

Regards.

4

Hello,

Any update?

5

Sorry for the late response. I wll check and get back to you.

7

Will be nice to hear any news…)

8

Sorry I forgot to reply. We test with newly created buckets and had no problem. According to the log file your S3 credential doesn’t have necessary permission to access to newly created bucket. Please check the permission policies on your IAM Management Console of AWS.

9

First of all problem is still appears. Second - about what permissions you are speaking about? We creating the bucket and only after 4-7 hours we can access it… What happening with permissions?

10

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.