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: