Skip to content

Not able to request Production Access to SES

0

In April, I had just created my AWS account, by mistake I had raised a request for production access, but I could not follow up to the responses. The ticket was closed in 14 days.

Now, when I am ready with the application and want to go ahead with the SES "Get set up" is not allowing me to raise another ticket and shows that there is an existing ticket. I cant re-open the existing ticket, as it is more than 14 days.

In short, I don't have any way to raise another ticket to get production access to emails. Any help would be great!

asked a year ago584 views

2 Answers
0
Accepted Answer

I understand your frustration with being unable to submit a new SES production access request after your previous ticket was closed. This appears to be an edge case in the AWS SES request system.

Here are some steps you can take to address this situation:

  1. Try accessing the SES Production Access Request page directly. You should be able to submit a new request even with a Basic plan by visiting the SES console and navigating to the production access request section.

  2. If the console interface continues to show issues, try using a different browser or clearing your browser cache.

  3. As an alternative method, you can submit your production access request using the AWS CLI. While this might not allow you to provide as much detail as the console form, it's a valid option to get your request submitted.

  4. When you do manage to submit your request (whether through CLI or console), provide comprehensive details about your use case, including:

  • The types of emails you plan to send (transactional, marketing, etc.)
  • Your estimated email volume
  • How you'll handle bounces and complaints
  • Your methods for ensuring compliance with email best practices
  • Implementation of proper email authentication (SPF, DKIM, DMARC)
  1. Make sure your Amazon SES account contains at least one verified identity before submitting the request.

  2. Review the AWS Acceptable Use Policy and AWS Service Terms to ensure your use case complies with them.

Since you're a new AWS customer, it's worth noting that AWS often requires users to build trust by using the sandbox environment for a while before granting production access. While working to resolve your submission issue, you can continue using the sandbox environment to build a positive sending history.
Sources
Unable to submit AWS SES "out of sandbox request" due to edge case. | AWS re:Post
SES Production request denied | AWS re:Post
Production Access to Amazon SES Denied - what to do? | AWS re:Post

answered a year ago

0

I have the exact same problem. Years ago, I submitted a request, and now I want to recreate it, but no matter how many times I try with the AWS CLI, it won't let me. I've tried everything, even paying for the next business support plan so they could help me, but the AI ​​support keeps responding, and I haven't been assigned an AWS support representative to help me. I need to unblock this. Please help.

"We have not received a response from you regarding case 954640605"

answered 7 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.