I'm in a bit of a bind here! I requested production access for SES to send Cognito verification emails, password reset emails, and a welcome email from my domain, but my request got denied. After reopening the case, they still said no. I initially thought the Cognito custom message Lambda trigger might help, but it turns out AWS doesn't pass the verification code to the Lambda function, so that's a no-go.
My app relies heavily on AWS services like Cognito, Lambda, IVS, and DynamoDB. Right now, I have two not-so-great options: either let users receive verification emails from AWS's default domain, which feels unprofessional, or scrap everything and switch to a different authentication provider, which would be a huge hassle.
We're about to launch our beta, and this is the last hurdle. Do we need to have actual users before this can be set up? Is there a minimum spending requirement for approval? Has anyone successfully navigated getting production access approved or found a way to escalate the request?
1 Answer
It's usually tougher to get production access with newer accounts. I've heard that accounts need to be older and have some usage before getting approved. Maybe wait a little longer or try adding some usage to your account to demonstrate it's not just sitting idle.
Thanks for the insight! My account's about 1.5 months old. Sounds like I might need to build it up a bit more before trying again.