Original Plan: Support for SigV2 ends on June 24, 2019. (see original Forum post below)
Revised Plan: Any new buckets created after June 24, 2020 will not support SigV2 signed requests, although existing buckets will continue to support SigV2 while we work with customers to move off this older request signing method.
Original post from 6/11/2018:
AWS Signature Version 4 (SigV4) is recommended for signing S3 API requests over AWS Signature
Version 2 (SigV2) as it provides improved security by using a signing key rather than your secret access
key. SigV4 is currently supported in all AWS regions while SigV2 is only supported in regions launched
prior to Jan 2014. S3 will stop accepting requests signed using SigV2 in all regions on June 24, 2019, any
requests signed using SigV2 made after this time will fail. The signature version is set in your software,
please update your applications to use the latest versions of the tools and SDKs to take advantage of the
improved security and avoid impact.
This is an announcement migrated from AWS Forums that does not require an answer