Can't see files and folders in my S3 bucket

[jensbaumgart]

I successfully connected to my amazon S3 bucket. But I can't see the contained files and folders.
I can create files and folders in the bucket. See attached screenshot.

Cyberduck Version 8.1.1 (36550)
macOS 12.0.1 (21A559)

[fishcharlie]

@jensbaumgart Do you have the correct IAM roles/permissions setup?

[edwinv]

I'm experiencing the same issue. The S3 bucket and IAM policy have been in place since 2018. I was always able to list and update files. With the last version of Cyberduck, listing of subfolders in the bucket suddenly throws this error:

I've reconfirmed the policy by using the AWS cli tool, this lists the bucket contents without issues. This confirms for me a possible bug in Cyberduck.

Related: #12596, #11883, #11896

[jensbaumgart]

The bucket is an external bucket. How to connect to an external bucket? I tried to put the bucket name in front of the server name, but this did not help. I still do not see the content of /

[dkocher]

Please do not set a region specific endpoint for the hostname. Refer to Access single bucket.

[jensbaumgart]

I put the bucket name in front of the server name. With this, I get the same result.
Then I entered the bucket name in the path field of the bookmark. This results in error message "Cannot read bucket location"
My colleagues using S3 Browser on Windows can access the bucket using "Add external bucket".

[jensbaumgart]

if I use S3 REST API, I see all objects in the bucket (jbtest and others not shown in Cyberduck):
https://s3-eu-central-1.amazonaws.com/hcp-XXXXXXXXXXXXXXXXXXXX?list-type=2

[dkocher]

Make sure your IAM policy allows s3:GetBucketLocation.

[jensbaumgart]

I have no access to these settings. I only have access key, secret key and bucket name.

[dkocher]

This is possibly fixed with #12694. Please try the latest snapshot build 8.2.0.36660.

[jensbaumgart]

Can't find download for 8.2.0.36660. Can you provide a link?

[dkocher]

See Preferences → Update or https://update.cyberduck.io/nightly/

[jensbaumgart]

The issue persists with version Version 8.2.0 (36663)
Tried all combinations:
put bucket in path: yes/no
put bucket in server name: yes/no

[dkocher]

Please provide logging output with Debug option enabled.

[jensbaumgart]

cyberduck copy.log

[jensbaumgart]

We finally found the issue: our paths contained a //. After removing the //, everything works fine.