AWS S3 bucket access error (Failed to list Amazon S3 directories, Code 37007000030) - fw 6.9.5

[midnightjulep]

Hi community!

I'm on 6.9.5 and trying setting up sync with AWS S3 bucket hosted outside the default us-east-1 region. I cannot make this work.

associated error codes: 37007000030

associated error messages: Failed to list Amazon S3 directories, Failed to list directory

error trigger: browsing S3 bucket folders

but if ignoring error and continuing setup, this ends up in error.

In the Amazon S3 session log it keeps trying for some time:

Mar 16, 2119 00:28:52 AMAmazon S3 service started.
Mar 16, 2119 00:28:52 AMStarting to index local drive. This could take a while. Please wait.
Mar 16, 2119 00:29:04 AMIndexing local drive is complete.
Mar 16, 2119 00:29:04 AMStarting to scan cloud drive for changes. It could take a while. Please wait.
Mar 16, 2119 00:30:25 AMAmazon S3 service started.
Mar 16, 2119 00:30:25 AMStarting to index local drive. This could take a while. Please wait.
Mar 16, 2119 00:30:28 AMIndexing local drive is complete.
Mar 16, 2119 00:30:28 AMStarting to scan cloud drive for changes. It could take a while. Please wait.

From system logs:

Mar 15 23:42:50 prdfile ng-csd[28449]: E0315 23:42:50.782362 28449 S3ErrorMarshaller.cpp:69] Encountered S3Error
Mar 15 23:42:50 prdfile ng-csd[28449]: PermanentRedirect
Mar 15 23:42:50 prdfile ng-csd[28449]: The bucket you are attempting to access must be addressed using the specified endpoint. Please send all future requests to this endpoint.
Mar 15 23:42:50 prdfile ng-csd[28449]: E0315 23:42:50.782848 28449 S3FS.cpp:89] Failed to fetch children. parent = Node metadata: { id = /, isFolder = 1, isTrashed = 0, name = /, localName = /, path = /, mi
meType = , size = 0, createdTime = 2018-12-12T13:16:24.000000Z, modifiedTime = 2019-03-15T22:42:49.000000Z, checksum = , parentId = , isShared = 0, oneDrive = OneDriveSpecific: { driveId = , isRemote = 0, r
emoteId = , remoteDriveId = } }, parentPath = /, pageToken = , maxKeys = 1000, HTTP_TRANSPORT_ERROR: The bucket you are attempting to access must be addressed using the specified endpoint. Please send all
future requests to this endpoint.

what I've tried:

1) selecting an existing bucket from some eu-* region: failed

2) MightyNas, create one for me pleease in some eu-* region: failed

3) played with custom urls: failed multiple times

4) to confirm my issues, created a new bucket in the us-east-1 region: ReadyNas wins

Given the IAM user used to perform this has the correct permissions on the resources involved, I've snatched through CloudTrail logs and found the Nas was stuck at trying to retrieve bucket location (GetBucketLocation) by issuing requests always to the us-east-1 region, no matter what custom url I specified.

Some examples (you can easily filter for DORAYAKI ua):

eventtime eventname awsregion sourceipaddress useragent requestparameters
1 2019-03-16T00:29:39Z GetBucketLocation us-east-1 x.x.x.x [DORAYAKI/1.0] {"host":["s3.us-east-1.amazonaws.com"],"bucketName":"my-bucket-name","location":[""]}
2 2019-03-16T00:29:03Z GetBucketLocation us-east-1 x.x.x.x [DORAYAKI/1.0] {"host":["s3.us-east-1.amazonaws.com"],"bucketName":"my-bucket-name","location":[""]}
3 2019-03-16T00:26:31Z GetBucketLocation us-east-1 x.x.x.x [DORAYAKI/1.0] {"host":["s3.us-east-1.amazonaws.com"],"bucketName":"my-bucket-name","location":[""]}
4 2019-03-16T00:21:20Z GetBucketLocation us-east-1 x.x.x.x [DORAYAKI/1.0] {"host":["s3.us-east-1.amazonaws.com"],"bucketName":"my-bucket-name","location":[""]}
5 2019-03-16T00:16:17Z GetBucketLocation us-east-1 x.x.x.x [DORAYAKI/1.0] {"host":["s3.us-east-1.amazonaws.com"],"bucketName":"my-bucket-name","location":[""]}
6 2019-03-16T00:12:56Z GetBucketLocation us-east-1 x.x.x.x [DORAYAKI/1.0] {"host":["s3.us-east-1.amazonaws.com"],"bucketName":"my-bucket-name","location":[""]}
7 2019-03-16T00:12:51Z GetBucketLocation us-east-1 x.x.x.x [DORAYAKI/1.0] {"host":["s3.us-east-1.amazonaws.com"],"bucketName":"my-bucket-name","location":[""]}
8 2019-03-16T00:12:51Z ListBuckets us-east-1 x.x.x.x [DORAYAKI/1.0] {"host":["s3.us-east-1.amazonaws.com"]}

And yes if you ask I've also tried switching browser(!)

Any suggestion or workaround to this?

tnx!

mj

[midnightjulep · Accepted solution]

It turned out it was a misconfiguration by my side and I finally made it working.

[midnightjulep · Accepted solution]

It turned out it was a misconfiguration by my side and I finally made it working.