With credentials that are authorized to a particular path, I get "I/O Error: Connection failed. Cannot read container configuration".
The config is not completely vanilla and I do have issues with several other clients as well (Cloudberry, S3Browser) but can act normally with some others (Transmit, S3Fox).
I will attach my IAM policy, Cyberduck connection config, and Cyberduck log output. Please let me know if I can provide anything more. I have replaced my real bucket name with "bucket-name" but that is the only change.
Also: I get the same error with "*" for actions in the attached IAM policy.
Sorry for not replying earlier. I am just investigating this issue. We are sending a HEAD request against the bucket to test the bucket is accessible given the login credentials. This fails for this bucket because the IAM user does not have read permission for the bucket itself.