AWS Signature Version 4 is replacing AWS Signature Version 2 for signing S3 API requests

Hello,

We're contacting you because we detect you are using AWS Signature Version 2 (SigV2) to sign and authenticate your S3 API requests. 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. SigV4 provides improved security and performance over SigV2. Please update your applications to use the latest versions of our AWS tools and SDKs to take advantage of the improved security and avoid impact. The table below lists out the SDKs with the necessary minimum version to use SigV4 by default. Note, if you are using pre-signed URLs with the Java, Javascript (Node.js) or Python (Boto/CLI) SDKs, you will need to set the correct region and set SigV4 in the client configuration.

SDK version using SigV4 by default

Tool version using SigV4 by default

Please visit the S3 documentation site to get more information on using SigV4[1].
You can find the list of changes between SigV2 and SigV4 here[2].
You can find our post regarding SigV2 in our AWS forums[3].
Feel free to contact AWS Support if you have any questions or concerns[4].

[1] https://docs.aws.amazon.com/general/latest/gr/signing_aws_api_requests.html
[2] https://docs.aws.amazon.com/general/latest/gr/sigv4_changes.html
[3] https://forums.aws.amazon.com/ann.jspa?annID=5816
[4] https://docs.aws.amazon.com/awssupport/latest/user/getting-started.html

Sincerely,
Amazon Web Services