Skip to content

Amazon SES Production Access request pending for over a month with no response after follow-ups

-1

Hello AWS Team,

I'm looking for guidance regarding an Amazon SES Production Access request that appears to be stuck.

Details:

Region: ap-south-1 Case Type: SES Production Access Case Created: May 31, 2026 Current Status: Reopened

On the same day the request was created, AWS requested additional information about my use case. I provided all the requested details immediately, including my email-sending process and intended use.

Since then:

I have followed up multiple times through the original support case. I also opened another support case requesting a status update, but it was interpreted as a sending limit increase request rather than a follow-up on the pending production access review. My original production access case remains in the Reopened state, and I have not received any response from the SES review team for over a month.

I'm not requesting a sending limit increase through this post. I'm simply trying to understand whether this delay is expected and if there is any way to have the existing production access case reviewed or routed to the appropriate team.

If any additional information is required from my side, I'd be happy to provide it.

Has anyone experienced a similar delay, or is there an AWS-recommended process for escalating a production access request that has been pending for this long?

Thank you for your time and assistance.

2 Answers
1

Hi there,

I'm sorry to hear about this experience.

I've passed along your concerns on your support case for review.

Continue monitoring your case for updates.

— Aimee K.

AWS
EXPERT

answered 3 months ago

EXPERT

reviewed 3 months ago

0

I understand your frustration with the delay in your Amazon SES Production Access request. While I don't have visibility into your specific case status, I can provide some guidance on the process and next steps.

Amazon SES Production Access requests do require review by the SES team, and response times can vary depending on the complexity of the use case and current queue volumes. The team may need additional time to thoroughly review applications to ensure compliance with AWS policies and email best practices.

Since you've already provided the requested information and followed up through your existing case, the best course of action is to continue adding correspondence directly to your original production access case through the AWS Support Center (https://console.aws.amazon.com/support/). When adding updates, clearly reference that you're following up on the production access request and reiterate that you've provided all requested information.

A few suggestions:

  • Ensure your correspondence is added to the correct case (the original production access request)
  • Clearly state that you're awaiting review of your production access application, not requesting a limit increase
  • Confirm that all previously requested information has been provided

The AWS Support Center remains your primary channel for case updates and is the most direct way to communicate with the team handling your request.

answered 3 months ago

EXPERT

reviewed 3 months ago

AWS
EXPERT

revised 3 months 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.