Default settings fail in new regions due to outdated signature_version default.
markstos opened this issue · comments
The undocumented default signature_version is "2".
The leads to code that runs in some regions but not others, which could lead to surprising or unexpected failures when identical code is deployed in multiple regions.
This official AWS page documents which regions don't support Signature Version 2. The failing defaults causes downstream projects like ec2-consistent-snapshot to also fail when deployed in new regions.
Reference: alestic/ec2-consistent-snapshot#87
Note the Paws project is already defaulting to version 4 signatures: pplu/aws-sdk-perl#139 (comment)
I set the default to 4 in 0.32 which I just released to CPAN. Thanks for the ticket.