I use Amazon S3 IAM users to give out highly limited access to select paths within our bucket. They work fine with Transmit as long as the initial path is specified properly. They do not work with Cyberduck at all. I've tried putting the bucket in the hostname, leaving it out, adding the path to the hostname, no dice. It looks like Cyberduck is sending a HEAD / on bucketname.s3.amazonaws.com, which doesn't work.
The text was updated successfully, but these errors were encountered: