SES AWS错误code:SignatureDoesNotMatch,状态code:403状态、错误、AWS、SES

2023-09-11 11:12:32 作者:┧普罗旺斯的狗尾巴草ミ

试图通过亚马逊SES发送邮件时403

我收到一个AWS错误code:SignatureDoesNotMatch,状态code。

我已经证实了我现在用的是我通过 HTTPS创建正确的凭据:/ /console.aws.amazon.com/iam/home?#users 并错误仍然存​​在。

我想我已经在IAM /家庭创建的证书,其实全球的,但我不知道我做错了进一步。整个错误是:

  

AWS错误code:SignatureDoesNotMatch,状态code:403,AWS请求   ID:XXX,AWS错误类型:客户端,AWS错误消息:签名过期:   20140314T031111Z现在比20140317T15116Z(20140317T151111Z更早    - 5分钟),用户代理:AWS-SDK-PHP2 / 2.5.3狂饮/ 3.8.1卷曲/ 7.22.0 PHP / 5.3.10-1ubuntu3.10扔进   /url/Vendor/Aws/Common/Exception/NamespaceExceptionFactory.php上线   91

实际的code是code,我从拉:的http://docs.aws.amazon.com/aws-sdk-php/latest/class-Aws.Ses.SesClient.html#_sendEmail

我从我的本地环境射击这个脚本。

我会在哪里能够找到凭据,将工作?

解决方案

这看起来像一个时钟偏差问题。您发送的请求的计算机的时间是从亚马逊SES服务器的时间也不同。这是造成你的签名是无效的。您的凭据可能是罚款。纠正你的机器的时钟同步或与NTP服务器。

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

关于AWS Codedeploy的使用 小结

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?

解决方案

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.