Reputation: 1553
The error Throttling failure: Maximum SigV2 SMTP sending rate exceeded.
suddenly started to appear in our .NET application though there were no exceeding any quota (14 mails per second or 50000 per day) in our AWS Sending Statistics.
I can see many similar issues about Throttling – Maximum sending rate exceeded
on StackOverflow but I'm confused about SigV2
in my error message.
Searching in other resources like this one gave me the idea that this issue started to happen recently from about October 20, 2020, and there is no exact answer to why this happened. The only solution I can see is to migrate from using SigV2 signing process to the new method.
The question is: Why this happened and can this issue be solved without changes in the application code?
Upvotes: 3
Views: 3288
Reputation: 76
This is not a service quota issue. The issue you are facing is due to excessive authentication requests from your side. This issue will not occur if you renew your SMTP credentials in the SES console to use Sigv4 credentials.
https://docs.aws.amazon.com/ses/latest/DeveloperGuide/smtp-credentials.html
Upvotes: 6
Reputation: 9364
As you can see your daily rate exceeded
But you can open a case and increase your maximum rate
Upvotes: 1