Amazon SES watches two numbers on every account. If either gets too high, AWS can stop your email, including the sign-in codes and receipts your product depends on.
The levels
| AWS reviews the account | AWS may pause sending | |
|---|---|---|
| Bounce rate | 5% | 10% |
| Complaint rate | 0.1% | 0.5% |
AWS publishes these in its enforcement FAQ. They apply to the whole account, not to one app.
What counts
A bounce here means a hard bounce: the address does not exist, or the domain does not. A full mailbox or a slow server is a soft bounce, which SES retries and does not count against you in the same way.
A complaint is a recipient pressing "this is spam". The level is low on purpose. One complaint in a thousand emails is enough to start a review.
Email you send to the SES mailbox simulator counts for neither, so it is safe to test with.
Why you find out late
SES does not show you a bounce unless you ask it to. By default the only signal is the account-wide rate in the console, and a warning email once you have crossed a level. To see individual bounces you need a configuration set that publishes events, and something to receive them.
That gap is where problems grow. Common causes:
- A signup form with no email confirmation, collecting typos and fake addresses.
- An old list, imported and emailed in one go.
- One app on a shared account behaving badly while the others pay for it.
How to stay under
- Confirm addresses at signup. A sign-in code or a confirmation link keeps typos out of your list.
- Stop sending to addresses that hard-bounced or complained. SES has an account-level suppression list that does this for you. Turn it on.
- Watch the rates per app. The account number tells you there is a problem. A rate per app tells you where.
- Get an alert at the review level, not after it.
NoDramaMail does the last two: it shows bounce and complaint rates per source against the AWS levels, and emails you when one reaches the review level. Its setup command also turns on the account-level suppression list.