SES Request Production Access - Stuck with no solutions
First of all, I currently have a basic support plan as I do not think that it makes sense to pay $29/month just to get SES production access.
I submitted my first request in March when my account was still fresh. At the time, the associated support case was rejected because the account was fresh and they wanted to see more activity. It has been 2 months now, I have a whole ton of services set up, my bills exceed $500/month. Yet I cannot seem to find a way to get production access.
10 days ago, I went back to the old case, but I could not reopen it due to it being > 14 days old. So I opened a new related case. It stayed unassigned for a week. So I added a reply with more details. Still nothing. It has been 10 days, and the case has not been assigned. I read other similar questions, one answer suggested using CLI, did not work because the case was rejected already. Another recommended going for another request through https://us-east-1.console.aws.amazon.com/ses/home?region=us-east-1#/account/request-production-access. (I am sure that I am in the correct region), but with that I got "The request configuration has conflicts." Tried incognito, does not work. So now I am stuck with no way of getting production access. No other way to contact support, no chat option. $29/month just to get basic support is ridiculous. I cannot wait a few months to get such a basic service.
Does anybody have any ideas?
- Language
- English
asked 2 months ago90 views
- Newest
- Most votes
- Most comments
Hello.
You do not need a paid AWS support contract to remove the Amazon SES sandbox.
Since applications are often rejected for new AWS accounts, some people avoid using Amazon SES and instead use SendGrid to circumvent these problems.
https://www.reddit.com/r/aws/comments/1dkd9fj/new_accounts_cant_get_out_of_ses_sandbox/?tl=ja
As mentioned in the post below, a second application may also be rejected.
https://repost.aws/ja/questions/QUO0zYv-bwRmOHRU0DD_-Kgw/ses-production-access-request-denied-with-no-information
- 2 months ago
I understand that they might reject it again. My problem is that I cannot even get them to look at it.
I understand your frustration with the production access request process. Based on the standard procedure, when you submit a request for production access, the AWS Support team should provide an initial response within 24 hours. Each request is reviewed carefully to prevent misuse of the system for sending unsolicited or malicious content.
Regarding your specific situation with the conflicting request error, this typically occurs when there's already an open production access request for your account. Even though your previous case may appear closed or unassigned, there might still be a pending review in the system that's preventing you from submitting a new request through the console.
Here are a few suggestions:
-
Check for pending requests: There may be an active production access review that hasn't been fully processed, which would block new submissions.
-
AWS CLI approach: While you mentioned the CLI didn't work because the case was rejected, you might want to try submitting a fresh production access request via CLI rather than trying to reference the old case. This can be particularly useful for automating or troubleshooting the submission process.
-
Account activity: Since you've now established significant account activity with over $500/month in bills and multiple services running, this should address the initial concern about account freshness.
The "conflicts" error you're encountering suggests a system-level issue with overlapping requests rather than an account eligibility problem. Unfortunately, without access to higher support tiers, resolving technical issues with the request system itself can be challenging. The support case route should be the primary channel for addressing this type of blocking issue, even with a basic support plan.
Sources
Request production access (Moving out of the Amazon SES sandbox) - Amazon Simple Email Service
answered 2 months ago
Relevant content
asked a year ago
