Skip to content
This repository

SignatureDoesNotMatch error #31

Open
nechmads opened this Issue February 21, 2012 · 7 comments

6 participants

nechmads Andrey Koleshko silent-e Miguel Ping Johnny Shields Drew Blas
nechmads

I'm using this gem with rails 3.1.1 and whatever I do I keep getting error:
AWS::SES::ResponseError (SignatureDoesNotMatch - The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.)

I'm sending this using the ActionMailer configuration option

Andrey Koleshko

The same issue. It seems to me that SES has changed API and we have this error now...

silent-e

Could be that Amazon recommends not using your Access Key and Secret to send via SMTP. From their SMTP Settings page...

"Note: Your SMTP credentials are not the same things as your AWS access key ID and secret key! Never supply your AWS credentials in response to any requests for SMTP usernames and passwords - use your SMTP credentials instead."

I am successfully using my access key ID and secret but am considering not using the gem and changing my setup to use my SMTP credentials.

Would love to see the gem update.

Miguel Ping
mping commented July 06, 2012

Any update on this?

Miguel Ping
mping commented July 06, 2012

Got it. You need to use AWS access keys, found here:
https://portal.aws.amazon.com/gp/aws/securityCredentials

Here's a guide to getting the access keys:
http://docs.amazonwebservices.com/ses/latest/GettingStartedGuide/GetAccessIDs.html

Johnny Shields

Would it be possible to modify the aws-ses gem so we use the SMTP credentials rather than the AWS credentials (or give a choice to use one or the other?)

Is there any chance that Amazon may disallow using AWS credentials in the future?

Drew Blas
Owner
Johnny Shields

Ah OK got it, thanks! Sorry I'm a bit of a newbie to this...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.