- Newest
- Most votes
- Most comments
I understand your frustration with this situation. It's a challenging edge case that can occur after a previous denial of production access for Amazon SES. Here are some steps you can take to address this issue:
-
Wait for a cooling-off period: AWS may have a temporary restriction on reapplying after a denial. This period is typically around 14 days, but it can vary. If you haven't already, wait for at least two weeks before attempting to reapply.
-
Try the SES Production Access Request page directly: Visit the SES Production Access Request page in the AWS Console. This should allow you to submit a new request, even with a Basic plan.
-
Use the AWS CLI: If the console method doesn't work, you can try submitting your request using the AWS Command Line Interface (CLI). While this method may not allow for as much detail as you'd like, it's still a valid option to get your request submitted.
-
Provide detailed information: When you do manage to submit your request, make sure to provide a clear and detailed description of your use case. Include information about the improvements you've made since your last request, such as:
- Implementation of DNS records (DMARC, DKIM, SPF)
- Your bounce handling policy
- Spam management procedures
- Any other relevant improvements
-
Contact AWS Support: If you're still unable to submit a new request, consider contacting AWS Support through other available channels, such as community forums or social media, to ask for guidance on how to proceed in your specific situation.
-
Consider a temporary support plan upgrade: As a last resort, you might consider temporarily upgrading to a support plan that allows you to open a technical support case. This would enable you to explain your situation in detail and seek assistance in submitting a new production access request.
Remember, AWS takes email sending privileges seriously to maintain the service's reputation and prevent abuse. Be patient and persistent in your efforts to reapply, focusing on demonstrating your improved email practices and commitment to following AWS policies.
Sources
Unable to submit AWS SES "out of sandbox request" due to edge case. | AWS re:Post
Production Access to Amazon SES Denied - what to do? | AWS re:Post
FAQs: Amazon SES production access requests | AWS re:Post
answered a year ago
Relevant content
asked a year ago
- AWS OFFICIALUpdated 5 months ago

This answer is incorrect. 1) check 2) this page doesn't seem to exist? only the "get set up page" which doesn't work. 3) CLI gives the ConflictException error 4) not relevant 5) is what im trying to do here 6) maybe, but not really a solution