Unable to Request SES Production Access: "The request configuration has conflicts" Error

Question

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 on the responses. The ticket was closed in 14 days.

A week back, when I was ready with the application and wanted to go ahead with the SES "Get set up" was not allowing me to raise another ticket and showed that there was an existing ticket. I couldn't reopen the existing ticket, because it was more than 14 days old.

So I checked the support ticket console, and the only relevant SES category that I could raise the ticket for was the "Quota Increase: SES Service Limits". I raised the ticket there and also posted in rePost if there is another solution. The rePost post got a reply and directed me to raise a production access ticket via the link https://eu-west-2.console.aws.amazon.com/ses/home?region=eu-west-2#/account/request-production-access.

I used the link to raise the ticket for production access. The support replied that there is a mismatch in the region and my project ARN. Of course, my project is in ap-south-1, but I raised the request without changing the region. I apologised to the staff for the confusion, but instead of helping, they just replied by denying my request (ok, that's fair).

Now, when I try to raise the production request in the correct regions with the link https://ap-south-1.console.aws.amazon.com/ses/home?region=ap-south-1#/account/request-production-access, I get the error "**The request configuration has conflicts.**"

I am not sure what is the right way forward for me to get production access to SES.

Vaishakh_K · Answer

Hello,

Thank you for reaching out, and we understand your concern. I'd like to help point you in the right direction.

**Regarding your SES Production access request:**

SES Production access requests are evaluated based on several factors. Some common reasons, requests may not be approved include:
- Insufficient detail about your email sending use case (e.g., type of emails, recipient list acquisition method).
- No clear opt-in/opt-out process for recipients.
- Lack of bounce and complaint handling mechanisms.

For more details on the requirements, please refer to:
- [Moving out of the Amazon SES sandbox](https://docs.aws.amazon.com/ses/latest/dg/request-production-access.html)
- [Amazon SES sending review process FAQs](https://docs.aws.amazon.com/ses/latest/dg/faqs-enforcement.html)

**Recommended next steps:**

Since this involves account-specific details that cannot be reviewed on a public forum, I'd recommend:

1. **For SES Production access** – Open a support case via the AWS Console (**Support -> Create Case -> Service Limit Increase -> SES Sending Limits**). In your request, please include:
   - A detailed description of your email sending use case.
   - How your recipient email list is procured/maintained.
   - How you plan to handle email bounces and complaints.

2. **For billing/refund concerns** – Open a billing support case via the AWS Console (**Support -> Create Case -> Account and Billing Support**). The billing team can review and assist with your refund request.
   - Direct link: https://console.aws.amazon.com/support/home#/case/create?issueType=customer-service

These teams will have visibility into your account and will be best positioned to assist you.

re:Post Agent · Answer

I understand your frustration with the SES production access request process. This appears to be an edge case in the AWS SES request system where you're unable to submit a new request after previous attempts.

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

1. Try accessing the SES Production Access Request page directly in the correct region (ap-south-1). If you're still seeing the "The request configuration has conflicts" error, try using a different browser or clearing your browser cache.

2. As an alternative method, you can try using the AWS CLI to submit your production access request. 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.

3. Open a new support case explaining your situation in detail. Reference your previous case IDs and explain the issues you've encountered with submitting a new request. Ask for guidance on how to proceed.

4. While waiting for a resolution, continue using the sandbox environment to build a positive sending history. This can actually help your case when you do get to submit a proper production access request.

When you do get to submit a new request, make sure to include comprehensive information about:
- The specific 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)

Since you're a relatively 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. This helps ensure the overall quality of the service and prevents abuse.  
**Sources**  
[Not able to request Production Access to SES | AWS re:Post](https://repost.aws/questions/QUXJsW3F2EReyGoYBUARNrSw/not-able-to-request-production-access-to-ses)  
[Production Access to Amazon SES Denied - what to do? | AWS re:Post](https://repost.aws/questions/QUqX7WIGpnQyqh0mowcTEQ3A/production-access-to-amazon-ses-denied-what-to-do)  
[SES Production request denied | AWS re:Post](https://repost.aws/questions/QUZ0fFKCdIQmyM-nwLoEdROQ/ses-production-request-denied)

Unable to Request SES Production Access: "The request configuration has conflicts" Error

Add your answer

Relevant content