Unfortunately, this is because of hilarious complexity in bucket naming; it's not always correct to use bucket-name.s3.amazonaws.com virtual-hosted notation, as version 1.3 does currently. I have a few buckets that have been sadly unique-ified using the public part of the AWS credential, and the simplest rendition with that results in buckets with upcases.
For these, the non-virtualhosted s3 endpoint needs to be used.
A gory account of the restrictions (including interesting implications for those who want to use SSL and dots in their bucket names, not forbidden by AWS guidelines) is here:
Unfortunately, this is because of hilarious complexity in bucket naming; it's not always correct to use
bucket-name.s3.amazonaws.com
virtual-hosted notation, as version 1.3 does currently. I have a few buckets that have been sadly unique-ified using the public part of the AWS credential, and the simplest rendition with that results in buckets with upcases.For these, the non-virtualhosted s3 endpoint needs to be used.
A gory account of the restrictions (including interesting implications for those who want to use SSL and dots in their bucket names, not forbidden by AWS guidelines) is here:
https://github.com/heroku/WAL-E/issues/24#issuecomment-3257283