You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description
Class SesApiTransport, SesHttpTransport still use AWS SES API V3 signature.
Beginning October 1st, 2020, Amazon SES will only support requests signed using Signature Version 4. If you use an older version of the AWS Signature, you must adopt AWS Signature Version 4 prior to that date.
How to reproduce
Send an email with SES API and look for header X-Amzn-Authorization: AWS3-HTTPS [...], meaning you are using V3 signature. Plus you get a warning in SES API Console.
Possible Solution
Implement V4 Signature or use AWS PHP SDK.
It seems it has been fixed in branch 5.1. But documentation lacks a warning and it's not clear if you have to composer require async-aws/ses manually or if a dependency has been included (composer.json says it's not required).
Symfony version(s) affected: 5.0.10
Description
Class
SesApiTransport
,SesHttpTransport
still use AWS SES API V3 signature.Beginning October 1st, 2020, Amazon SES will only support requests signed using Signature Version 4. If you use an older version of the AWS Signature, you must adopt AWS Signature Version 4 prior to that date.
How to reproduce
Send an email with SES API and look for header
X-Amzn-Authorization: AWS3-HTTPS [...]
, meaning you are using V3 signature. Plus you get a warning in SES API Console.Possible Solution
Implement V4 Signature or use AWS PHP SDK.
Additional context
https://docs.aws.amazon.com/ses/latest/DeveloperGuide/using-ses-api-authentication.html
https://docs.aws.amazon.com/general/latest/gr/signature-version-4.html
The text was updated successfully, but these errors were encountered: