-
Notifications
You must be signed in to change notification settings - Fork 108
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deprecate signature v2 and signature v3 authentication #83
Comments
I'm getting this warning from AWS but I'm already running version 0.7.1 (the advice in email is to update to latest). |
The latest version doesn't have #82 merged, so as long as the code path you're taking in this lib is relying on sigv2, you'll get notifications from AWS. |
So, sorry, but when is #82 going to be merged for release? |
Okay great thanks for this advice. However when I implemented this I got an error:
My initializer:
When I remove |
You're getting this error because something is off when AWS compares the signature computed server-side versus the signature computed in this lib. Try providing the region as well, it's used for sigv4 signature calculation (in 'sig_v4_auth_signature'. I don't know particularly know this lib or ruby, but I guess the sigv4 implementation may not be properly handling this, or something else (timestamp?). |
Sadly this is not working for me. I was anyway on the default domain for SES.
However I still get the error. Any idea why this is the case? |
I also get an error like this, has anyone solved this problem |
@svmax provided solution for this in next issue:
|
Thanks @volonterx - looks like that is far more significant than just adding signature_version: 4 into the options. Before I go using it though when can we expect the formal release? The Amazon emails suggest previous versions are already deprecated and I'm "in breach" by not using V4.
|
@makrmark, here #78 (comment) @dnalbach said that @drewblas has no activity on GitHub since November '20, so it highly likely that it will be never released. If as temporary solution you want to use "78-sigv4-problem" PR, make sure you provided :signature_version and :region in settings.
Yeah, as I can see from #79 diff it has changes in structure and format of data that are not compatible with signature v3. |
Thanks @volonterx that's good advice - I updated to the official gem now and all appears fine. Will monitor for further messages from AWS :-) |
thanks everyone, to summarize: in gem "aws-ses",
github: "zebitex/aws-ses",
branch: "78-sigv4-problem",
require: "aws/ses" in Rails
.application
.reloader
.to_prepare do
ActionMailer::Base.add_delivery_method(
:ses,
AWS::SES::Base,
access_key_id: ENV["AWS_ACCESS_KEY_ID"],
secret_access_key: ENV["AWS_SECRET_ACCESS_KEY"],
signature_version: 4,
region: ENV["AWS_SES_REGION"]
)
end (the |
Even simpler: gem "aws-ses", github: "sertangulveren/aws-ses", require: "aws/ses" @sertangulveren's branch works directly by just defaulting to signature version 4. Maybe @sertangulveren can fork the gem to something like gem "aws-ses-v4" if @drewblas is not responsive? I don't mind forking it if @sertangulveren doesn't want to. That's too bad to lose that work, it fits so nicely in Rails. ❤️ |
Switching to the official |
The gem aws-ses-v4 worked for me after uninstall the original aws-ses gem. Thanks @sertangulveren ! gem uninstall aws-ses |
You may want to check out https://github.com/tablecheck/mail-ses. It uses the official AWS SDK under the hood. |
AWS SES is deprecating those 2 signing methods for authentication. The only method supported in the future will be signature v4.
The text was updated successfully, but these errors were encountered: