Rejected SES, follow up after closed ticket

Question

I created my free tier account for my new project and requested SES production access on the 15th January. It had all the necessary steps (I think) but was rejected. There were no reasons so I continued to build out other parts of my application. Fundamentally I need to send out forgot password links, verification codes, welcome emails to registered users and email out to users who have subscribed to updates on the application. I assume a lot of this is due to mass spam protection and honestly I'm not going to be emailing many folk unless my application suddenly becomes mega successful (the dream?) but the main blocker is only being able to mail people on my allow list. I could use cognito but that only solves half the problem since I can't handle the subscription part.

I'm now due to go live in the next week so I thought I would make the request again. So.... since more than 15 days passed, my case was permanently closed. I could only make a related case but couldn't really find anything specific to SES other than IP limit increase. I created a general ticket instead but this has been sitting unresolved for over a week now.

I'm not sure I'm comfortable turning this into a paid account if Amazon aren't able to support me with SES.

I see many people getting rejected and lots of automated responses so is it worth just ditching Amazon for the time being because I'm in danger of not being able to actually launch my application.

Any advice?

Kidd Ip · Answer

Your intended use case covering password resets, verification codes, welcome emails, and subscription updates falls within the category of transactional messaging and is generally considered acceptable under Amazon SES guidelines. However, it is essential to clearly demonstrate that all recipients have provided explicit opt‑in consent and that robust anti‑spam safeguards are in place. Without this assurance, AWS frequently denies production access requests from newly established accounts due to the absence of an established sender reputation.

https://docs.aws.amazon.com/ses/latest/dg/request-production-access.html

Christopher · Answer

I'm not quite sure why the downvotes, was something not put properly?

Fundamentally the request was for transactional, but the main concern right now is a case that was opened on 2026-02-25 21:00:19 but is still in unassigned.

Running the following looks like I'm still in some kind of intermittent state:

$ aws sesv2 put-account-details \
--production-access-enabled \
--mail-type TRANSACTIONAL \
--website-url REDACTED \
--additional-contact-email-addresses REDACTED \
--contact-language EN

aws: [ERROR]: An error occurred (ConflictException) when calling the PutAccountDetails operation: None

Rejected SES, follow up after closed ticket

Add your answer

Relevant content