We submitted two AWS support cases for a new account in eu-west-1: one requesting SES production access and another requesting SMS End User Messaging production access. The account is new, but it belongs to an established AWS Organization with multiple active accounts and a clean operational history.
Both requests include detailed information about the business use case, expected sending patterns and volumes, recipient consent and opt-in procedures, bounce and complaint handling, compliance practices, and destination countries. However, we have received no meaningful acknowledgment or timeline, even though previous SES reviews were handled more quickly.
These approvals are blocking a customer onboarding project with a firm delivery deadline, so we are considering backup providers such as Twilio for messaging and Resend for email. Has anyone recently experienced similar delays with SES or SMS production access? Is this normal with Basic Support, and does upgrading the AWS Support plan provide faster handling for these reviews?
2 Answers
Treat this as a launch-risk issue rather than just a support-ticket delay. Keep both cases focused and include the expected volume, recipient source, opt-in process, unsubscribe path, bounce and complaint handling, and destination countries. Reply to the existing cases with concise updates instead of opening duplicates.
At the same time, keep a fallback provider ready and make your application able to switch providers without a large code change. AWS Organization history may help, but a new account requesting both SES and SMS access can still enter manual review. I would not let a customer deadline depend entirely on one approval queue. After approval, start with low volume and monitor bounces and complaints closely.
Run two tracks in parallel. For SES, ask for a modest initial quota rather than the eventual target, provide sample messages, explain exactly how recipients consent, and document the full bounce and complaint workflow—including suppression updates, ownership, and what happens after a complaint. Include contact, abuse, and privacy information for the sending domain.
Reviewers mainly want confidence that the account will not become a spam source and that someone can stop problematic traffic quickly. Keep a backup email provider available for the first customer launch, even if SES remains the long-term choice. Also plan SES and SMS separately because their approval and sender requirements can fail for different reasons.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures