- Newest
- Most votes
- Most comments
I understand your frustration with the SES sandbox removal process. While I don't have specific information about your case in the sources provided, here are some general steps to help you move forward:
First, ensure your request includes all required information:
- A clear description of your use case and how you'll use SES
- Details about how you handle bounces and complaints (you mentioned you have this)
- Information about your email sending practices and compliance with anti-spam policies
- Your process for managing recipient lists and obtaining consent
If your requests are being rejected without clear explanation, try these approaches:
-
Review the rejection message carefully - Even brief rejections often contain clues about what's missing or concerning to the review team.
-
Be very specific in your next request - Provide concrete details about your bounce/complaint handling infrastructure, including specific mechanisms (SNS topics, configuration sets, etc.).
-
Demonstrate email best practices - Explain your list management, double opt-in processes, unsubscribe mechanisms, and how you maintain list hygiene.
-
Start with a lower sending limit request - Rather than requesting maximum limits immediately, ask for a modest increase that matches your actual near-term needs.
-
Open a support case - If you have a support plan, create a case specifically asking for feedback on why your requests are being rejected and what specific information or changes would make your request acceptable.
The key is providing enough detail to demonstrate you're a legitimate sender who understands email best practices and AWS's acceptable use policies.
Hello,
I fully understand your frustration regarding SES production access. I've relayed your concerns internally to our Support team for review.
Continue to monitor your case for further updates from our team: go.aws/support-center.
- Doug S.
Relevant content
- asked a year ago
- asked 9 months ago
- asked 9 months ago
- AWS OFFICIALUpdated a year ago
