10

I'm getting a AWS Error Code: SignatureDoesNotMatch, Status Code: 403 when trying to send a mail through Amazon SES.

I have confirmed that I am using the correct credentials which I created via https://console.aws.amazon.com/iam/home?#users and the error still persists.

I assume the credentials I've created on the iam/home are in fact global but I do not know what I am doing wrong further. The entire error is:

AWS Error Code: SignatureDoesNotMatch, Status Code: 403, AWS Request ID: xxx, AWS Error Type: client, AWS Error Message: Signature expired: 20140314T031111Z is now earlier than 20140317T15116Z (20140317T151111Z - 5 min.), User-Agent: aws-sdk-php2/2.5.3 Guzzle/3.8.1 curl/7.22.0 PHP/5.3.10-1ubuntu3.10 thrown in /url/Vendor/Aws/Common/Exception/NamespaceExceptionFactory.php on line 91

The actual code is code I pulled from: http://docs.aws.amazon.com/aws-sdk-php/latest/class-Aws.Ses.SesClient.html#_sendEmail

I am firing this script from my local environment.

Where would I be able to find credentials that would work?

starball
  • 20,030
  • 7
  • 43
  • 238
Derek Gardiner
  • 165
  • 1
  • 8

2 Answers2

24

This looks like a clock skew issue. The time of the machine you are sending the request from is too different from the Amazon SES server's time. This is causing your signature to be invalid. Your credentials are probably fine. Correct your machine's clock or sync up with an NTP server.

Jeremy Lindblom
  • 6,437
  • 27
  • 30
  • 13
    Thanks dude, I ran `sudo ntpdate ntp.ubuntu.com` and then executed the code again and it worked! You saved me! – Derek Gardiner Mar 17 '14 at 18:54
  • I think this might be happening to me: http://stackoverflow.com/questions/23700422/aws-iam-user-policies-for-ses-not-working My EC2 servers are in SaoPaulo/Brazil (sa-east-1) and I'm using SES in North Virginia (us-east-1). How can I find out what is time SES is set since I can't access the server? – Vini.g.fer May 16 '14 at 17:06
  • 1
    Thank you @DerekGardiner for posting that command. This was exactly my problem too. I'm running a local vagrant box for running my Ruby on Rails app. Everytime the computer went into hibernate, and I forgot to shut down the vagrant box, the clock on the vagrant box would get out of sync. This was the exact fix I needed! – BoomShadow Apr 22 '15 at 06:48
  • @DerekGardiner actually your comment saved me :D – GusDeCooL Jun 05 '15 at 12:27
0

Along with this solution I have done the following.

1) I have created the user with PowerUser policy in IAM. 2) Updated the secret/access key in my code.

Now it's working.

Not sure why SMTP credentials(Which are created under SES Dashboard) are not working.

user2890599
  • 11
  • 1
  • 1
  • 3