Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I use Transmit, Cyberduck, and Espresso, all of which support connecting to Amazon S3. But for some reason, I can only connect to my S3 storage successfully in Transmit; Cyberduck and Espresso both fail with generic errors like "login failed."

I know that I have the correct access key ID and secret access key because, as I said, I have no problem connecting in Transmit. I even imported my Transmit bookmark directly into Cyberduck, and yet I still can't connect through it.

Any ideas? I've gone back and forth comparing Transmit's settings to Cyberduck and Espresso and I can't find anything that would explain the discrepancy.

share|improve this question
up vote 3 down vote accepted

Under the assumption that you have created an IAM user with a dedicated policy it might miss the s3:ListAllMyBuckets action. If so, you can browse a single bucket in Cyberduck by connecting to instead of the default S3 hostname. Refer to

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.