Free tool
SES production access request writer
New SES accounts start in the sandbox: you can only email verified addresses, up to 200 a day. AWS decides who gets out, and vague requests get refused. Answer these questions and get a clear request you can paste into the console.
Access is granted per region.
AWS reviewers visit it.
Say what triggers each email and who receives it. At least 80 characters.
Your honest estimate.
At least 40 characters.
Describe what you actually do or will build.
Still needed: Mail type, Website URL (https://…), Use-case description (at least 80 characters), At least one kind of email, Expected emails per day, How you obtain recipients (at least 40 characters), Bounce handling, Complaint handling, Suppression strategy.
How this works
Nothing is invented. The request is built only from your answers, in your words, with plain section headings. Blank questions are left out rather than filled in, and it never claims that AWS will approve you. It runs in your browser, so your answers aren't sent to us.
Why requests get denied
- A use case that says “sending emails to customers” and nothing else.
- No answer for bounces and complaints. AWS wants to see you'll handle both.
- Purchased or scraped lists. These are against the AWS Acceptable Use Policy and are routinely refused.
- No working website, or a site that doesn't match the use case.
Check that your domain's records are right first with the SES DNS checker: reviewers look for an authenticated sender.