- Newest
- Most votes
- Most comments
Sandbox restrictions on new accounts are frustrating but there are specific things you can do to get each one approved faster.
For SES production access: The most common reason requests are rejected or delayed is insufficient detail in the submission.
Make sure your request clearly states: Your expected sending volume per day The type of emails being sent (transactional alerts, not marketing) How recipients are added to your system (user registration with explicit consent) How you handle bounces and complaints Submit via SES console → Account dashboard → Request production access: https://docs.aws.amazon.com/ses/latest/dg/request-production-access.html
For End User Messaging (SMS) production access: SMS requests require additional detail around use case. Explicitly state this is a transactional emergency alert system for vulnerable individuals, not promotional messaging. This categorisation matters and speeds up approval: https://docs.aws.amazon.com/sms-voice/latest/userguide/sandbox.html
For Bedrock model access: Bedrock access is granted per model and per region. Go to the Bedrock console → Model access → Request access and select the specific models you need. Include your use case in the request. Healthcare and safety use cases are generally approved: https://docs.aws.amazon.com/bedrock/latest/userguide/model-access.html
If requests keep getting rejected: Open a support case under Service Limit Increase and reference your project URL in the description. A human reviews these and a clear legitimate use case like an emergency monitoring app for vulnerable individuals is exactly the kind of project AWS approves.
Reference: AWS Service Quotas and limit increases: https://docs.aws.amazon.com/general/latest/gr/aws_service_limits.html
