Skip to content

Urgent: Amazon SES Production Access Request Pending for 6+ Days (Case ID: *************)

-1

Hello,

I am writing to kindly request an AWS moderator or support engineer to help look into my pending Amazon SES production access case, which has been stuck with no response for over 6 days (more than 4 business days) since being reopened.

  • Case ID: ***************
  • Region: eu-central-1 (Frankfurt)
  • Date Reopened: July 22, 2026

Our original request to remove the SES sandbox limits was unfortunately rejected because the reviewer noted that our domains (zenith-groove.com, mnsci-tech.com, etc.) were "not verified" in Amazon SES. However, this seems to be a misunderstanding or a region oversight during the review. All of our domains have been fully verified with DKIM in the Frankfurt (eu-central-1) region under our account.

On July 22, we reopened the case and provided clear, comprehensive screenshot evidence of:

  1. Fully verified domain identities in the eu-central-1 region.
  2. Highly clean sandbox sending metrics (0.03% bounce rate and 0.00% complaint rate).
  3. Active SNS feedback notifications configured for bounce and complaint handling.
  4. Functional unsubscribe mechanisms implemented in actual sent emails.

We also sent a follow-up message on the case, but we have received no replies or updates so far. Our business operations and system deployments are currently at a complete standstill due to this delay.

Could a moderator please kindly flag this Case ID (***************) internally to the SES / Trust & Safety team so that they can review the screenshots we provided and expedite the approval? We have strictly implemented all best practices.

Thank you very much for your time, support, and assistance.

*Edit: Removed Case ID - Roman Z.

2 Answers
0

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.

AWS
EXPERT

answered a month ago

EXPERT

reviewed a month 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.

0

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

AWS
MODERATOR

reviewed a month ago

EXPERT

reviewed a month ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.