Why is my Amazon SES account still stuck in the sandbox?
Asked by
MellowPine47
I've been waiting several weeks for my Amazon SES production access request to be approved. In my request, I explained how I plan to track bounces and complaints and manually remove hard-bounced addresses. When I tried closing the support case and submitting a new request, the same case simply reopened. Is there something missing from my explanation or account setup that could be delaying approval?
Answers
Make sure your sending setup is complete too: verify your domain and configure DKIM, SPF, and DMARC where appropriate. Clearly document your expected sending volume, who receives the messages, how recipients opted in, and what safeguards prevent repeated delivery to bounced or complaining addresses.
Reply to this answer
The review process can be inconsistent, and an open request being reopened does not necessarily mean it was denied. Add a detailed update to the existing case rather than repeatedly closing and recreating it. Be specific and thorough about your automated controls, list-management process, and email content.
Reply to this answer
Some accounts are approved quickly, while others receive more scrutiny based on account history, region, or configuration. The strongest request is one that demonstrates a production-ready system: automated suppression, complaint monitoring, unsubscribe handling, authentication, and a clear explanation of how you will maintain list quality.
Reply to this answer
SES approval reviewers usually want to see automated handling for bounces, complaints, and unsubscribes—not just a promise to clean the list manually. Explain how your system processes notifications, suppresses invalid addresses, manages opt-outs, and keeps bounce and complaint rates low. Including examples of your emails and unsubscribe flow may also help.
Reply to this answer
Add your answer
Answers are reviewed before publication.
Related Discussions