django-ses: AWS SES Signature V4 : Can't find the request header in the log
I was using django-ses 0.8.5 as my email backend and I could see the request header in my application log, which belonged to signature V3.
Final headers: {'Content-Type': 'application/x-www-form-urlencoded; charset=UTF-8', 'User-Agent': 'Boto/2.49.0 Python/3.7.0 Linux/4.14.209-160.335.amzn2.x86_64', 'Date': 'Sun, 14 Feb 2021 20:32:57 GMT', 'X-Amzn-Authorization': 'AWS3-HTTPS AWSAccessKeyId=AKIEXAMPLEDTA,Algorithm=HmacSHA256,Signature=adWwLkredkdhfhfhhhdhxxxpxKa6o=', 'Content-Length': '44640', 'Host': 'email.us-east-1.amazonaws.com'}
according to the AWS announcement, they are moving to signature version 4. So I have updated Django-ses 0.8.5 to 1.0.3 latest.
these are my current versions django-ses == 1.0.3 boto3 == 1.17.7 botocore=1.20.7
But, After I update these, I can’t see the request header in my application logs to identify the signature version. could you please advise on this?
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Reactions: 9
- Comments: 16 (8 by maintainers)
Glad I found this. Just upgraded django-ses to the latest to hopefully stop these nag emails from Amazon!
[Action Required] Migrate to Signature Version 4 to continue using Amazon SESReleased v2.0.0: https://pypi.org/project/django-ses/2.0.0/
Give it a try. Thanks so much for testing!
Hi! is there any update regarding this problem? AWS are going crazy with notifications because I’m using V3 in front of V4.
Thank you!
It’s possible #199 would fix this, if you’d like to give it a try.