- Newest
- Most votes
- Most comments
I know this delay creates challenges to get your business in full production.
I've reached out internally to emphasize the urgency and to relay the updates you provided. As I can't go into account or case specifics over re:Post, keep an eye on your case thread for additional guidance.
- Randi S.
I understand you're waiting for a response on your existing case regarding Amazon SES production access. While I can't directly intervene in or expedite specific support cases, I can offer some guidance on next steps.
For updates on your pending case, the best course of action is to add correspondence directly through the AWS Support Center at https://console.aws.amazon.com/support/. This ensures your message reaches the support engineer assigned to your case and maintains a clear record of all communication.
Regarding Amazon SES production access requests, it's important to ensure that all domain identities are verified in the specific AWS Region where you're requesting production access. When submitting evidence of domain verification, make sure the screenshots clearly show the region selector and that all domains are in a "Verified" status in that region.
If you haven't received a response within the expected timeframe for your support plan, you can also review your AWS Support plan options to understand response time commitments. Different support tiers offer different response times, and upgrading your support plan may provide faster responses for future cases if needed.
Continue to provide any additional information requested through the Support Center, and the team will work to resolve your case as quickly as possible.
answered a month ago
Relevant content
- AWS OFFICIALUpdated 4 years ago

You must recognize that this delay was caused by your company’s negligence—specifically, the rejection of our application due to your failure to acknowledge the authentication records we had compiled.