Why is AWS SES support not responding to an urgent Production Access request?

Question

We have been waiting since August 23, 2026 for a concrete response regarding our Amazon SES Production Access request.
At this point, the situation is beyond frustrating.
We are in the final production-readiness phase of our platform, and transactional email is a critical dependency for account verification, password resets, enquiries, and system notifications. This is not some optional feature we can simply ignore while AWS takes its time.
We have already provided everything requested:
•	a detailed explanation of our transactional email use case,
•	recipient acquisition and consent procedures,
•	bounce and complaint handling,
•	verified domain and DKIM configuration,
•	confirmation that we do not use purchased, rented, scraped, or third-party mailing lists,
•	and even a dedicated public review page created specifically so AWS could independently verify the service.
And what have we received in return?
No concrete decision. No meaningful status update. No explanation. Practically no useful support at all.
I have worked with many hosting, infrastructure, software, and cloud providers over the years, and I genuinely cannot remember experiencing support this poor for something this straightforward and this important.
For a company the size of Amazon, this is embarrassing.
AWS presents itself as enterprise-grade infrastructure, but when a legitimate customer needs a simple production-access review completed, the experience is apparently to submit everything requested and then wait in silence while a production launch is being blocked.
That is not serious support.
If nobody at AWS is capable of reviewing this request and providing a concrete answer immediately, we will simply move our transactional email infrastructure to another provider.
And frankly, after this experience, we are also reconsidering whether we want to use AWS services at all going forward.
Why should we build critical infrastructure around a provider when getting a basic response from support is this difficult?
Someone from AWS Support needs to escalate this case immediately and provide an actual decision, not another generic acknowledgement.
At the moment, Amazon SES may be technically impressive, but the support experience around it has been absolutely dreadful.
If this is considered acceptable support for production infrastructure, then choosing another provider is becoming a very easy decision.

re:Post Agent · Answer

I understand your frustration with the delay in your Amazon SES Production Access request. While I don't have visibility into the specific status of your case, I can help clarify the process and suggest next steps.

Amazon SES Production Access requests are carefully reviewed to maintain the service's high deliverability rates and sender reputation. The review process examines your use case, compliance with AWS policies, and email sending practices. While most requests are processed within 24 hours, some cases require additional review, particularly for new accounts or complex use cases.

For your immediate situation, I recommend adding detailed correspondence directly to your existing case through the AWS Support Center at https://console.aws.amazon.com/support/. In your update, you can reiterate the business impact and request a status update on the review timeline. The support team handling your case will have the most current information about any outstanding requirements or review status.

If response times are a concern for your business-critical workloads, you may also want to review your AWS Support plan options. Higher-tier support plans offer faster response times and additional support channels that can be valuable when you have production dependencies.

Regarding your production readiness concerns: while waiting for Production Access approval, ensure your application can gracefully handle email service unavailability, as this is a best practice regardless of provider. Consider implementing retry logic and appropriate user messaging for any email-dependent workflows.

The AWS Support Center remains your best channel for case-specific updates and to communicate the urgency of your production timeline to the team reviewing your request.

AWS Support - Sage · Answer

Hi,

I understand the urgency of your request and want to help you get the help you need. While cases are answered in the order they're received, we've also made sure to share your requests with our internal teams.

Continue to monitor your case for updates. I apologize for the concern this has caused.

\- Sage A.

mzb · Answer

Hello,

Please do not send us another generic request for information that has already been provided.

We are asking for an actual review and decision on our Amazon SES production access request.

Your own message states that an initial response is provided within 24 hours. We submitted this request on August 23, 2026, and have already supplied extensive additional information covering our sending use case, recipient handling, transactional email flows, bounce and complaint procedures, domain verification, DKIM configuration, and the nature of the emails we intend to send.

We have also provided a publicly accessible review page specifically for the AWS review team, so that our service and use case can be independently reviewed despite the main application currently being protected by maintenance mode during final production-readiness testing.

Our use of Amazon SES is straightforward:

transactional and event-driven email only,
registered users and direct platform interactions only,
no purchased, rented, scraped, or third-party mailing lists,
verified sending domain,
DKIM configured and enabled,
bounce and complaint handling in place,
no unsolicited bulk email.

At this point, repeating the same questionnaire instead of reviewing the information already provided is not an acceptable support process.

We are not asking for another acknowledgement. We are asking for someone to review the case, make a decision, and provide a concrete response.

If this case cannot be properly reviewed and resolved by August 26, 2026, we will proceed with another transactional email provider.

We cannot allow an unanswered SES access request to continue blocking our production deployment.

Please escalate this case to the appropriate team and provide a substantive response rather than another generic template.

Why is AWS SES support not responding to an urgent Production Access request?

Add your answer

Relevant content