SES Production Access Denied for No Stated Reason

Question

I asked to be moved from SES Sandbox to Production and was prompted for more detail.  We are a legitimate business that sends high quality transactional emails with a low bounce rate, should be a minimial risk case.  We send out about 250,000 transactional emails per month from a dedicated server but want to make our email sending more scalable.  I received the following after providing more detail:
"We reviewed your request and determined that your use of Amazon SES could have a negative impact on our service. We are denying this request to prevent other Amazon SES customers from experiencing interruptions in service.  For security purposes, we are unable to provide specific details."
I reopened the case and provided more detail and was once again denied with no detail.  I complained that there was no legitimate reason provided.  I once again received a denial, this time with the cryptic "unable to provide specific details" message again.

re:Post Agent · Answer

I understand your frustration with having your Amazon SES Production Access request denied without specific feedback. This is unfortunately a common experience that many AWS users face.

When AWS denies SES production access requests, they typically provide limited details due to their security policies. The denial message often cites concerns about potential impact on their service deliverability without specific explanations.

Here are some steps you can take to address this situation:

1. **Review your use case thoroughly**: Ensure it fully complies with AWS's Acceptable Use Policy and Service Terms.

2. **Wait and build trust**: If you're a newer AWS customer, this could be a factor. AWS often requires users to build trust by using the sandbox environment for a while before granting production access.

3. **Reapply with more comprehensive details**: Submit a new request with very detailed information about:
- The specific types of emails you plan to send (transactional, etc.)
- Your estimated email volume
- How you'll handle bounces and complaints
- Your methods for ensuring compliance with email best practices

4. **Implement proper email authentication**: Make sure you have SPF, DKIM, and DMARC properly configured and describe your plans for handling bounces and complaints.

5. **Open a new support case**: Create a fresh support case explaining your situation, referencing the previous case ID, and asking for guidance on how to proceed.

AWS takes email sending privileges seriously to maintain the service's reputation and prevent abuse. While waiting for production access, you can continue using the sandbox environment with its limitations to build a positive sending history that demonstrates responsible use of the service.

If you continue to face rejections despite these efforts, you might need to consider alternative email service providers for your transactional emails.  
**Sources**  
[SES Production request denied | AWS re:Post](https://repost.aws/questions/QUZ0fFKCdIQmyM-nwLoEdROQ/ses-production-request-denied)  
[Production Access to Amazon SES Denied - what to do? | AWS re:Post](https://repost.aws/questions/QUqX7WIGpnQyqh0mowcTEQ3A/production-access-to-amazon-ses-denied-what-to-do)  
[SES Production access request denied with no information | AWS re:Post](https://repost.aws/questions/QUO0zYv-bwRmOHRU0DD_-Kgw/ses-production-access-request-denied-with-no-information)

SES Production Access Denied for No Stated Reason

Add your answer

Relevant content