AWS S3 Command Line Clients for Windows, Linux, Mac. Backup to S3, upload, retrieve, query data on Amazon S3.

S3cmd Home | S3cmd Download | FAQ / KB

S3cmd: FAQ and Knowledge Base

Main Page > Browse Categories > Common Errors > Why does s3cmd complain about invalid signature after upgrading from older s3cmd?

Why does s3cmd complain about invalid signature after upgrading from older s3cmd?

S3cmd 0.9.5 added support for buckets created in European Amazon data center. Unfortunately the change has broken access to existing buckets with upper-case characters in their names. This regression has long stayed unnoticed and has only recently been fixed in s3cmd 0.9.8.4.

Therefore if you are suddenly getting errors like:

ERROR: S3 error: 403 (Forbidden): SignatureDoesNotMatch

after upgrading from s3cmd 0.9.4 or older to 0.9.5 or newer, you are advised to upgrade even further to s3cmd 0.9.8.4 or newer to regain access to your upper-case named buckets.

User Comments

There are no user comments for this topic.

Attachments
No attachments

Did this help you?

Yes

No

Statistics
52% found this information useful

Other Options
Printable Version

Download S3Cmd

A printable version of the entire FAQ and Knowledge Base is also available.

For further queries or questions, please contact us.