- Newest
- Most votes
- Most comments
No longer business support and it allows to do this directly from SES Console or via the AWS CLI:
Option 1: Using the AWS Console
- Go to the Amazon SES Console.
- Navigate to Account Dashboard.
- Click “View Get set up page” and then “Request production access”.
- Fill out the form: o Mail Type: Choose Transactional. o Website URL: Provide a valid URL that describes your app or service. o Use Case Description: Clearly explain your use case (e.g., transactional emails like password resets, verification codes). o Additional Contacts: Add up to 4 email addresses. o Preferred Language: Choose English or Japanese. o Acknowledgement: Confirm you’ll only send to users who’ve opted in and that you handle bounces/complaints.
Option 2: Using AWS CLI
aws sesv2 put-account-details \
--production-access-enabled \
--mail-type TRANSACTIONAL \
--website-url https://yourdomain.com \
--additional-contact-email-addresses info@yourdomain.com \
--contact-language EN \
--use-case-description "Transactional emails for mobile app users"
Hey,
Hope you're keeping well.
You don’t need a Business Support plan to request SES production access. In the AWS console, go to SES > Account Dashboard > Sending limits and choose “Request production access,” which will open the Service Quotas request form. Provide clear details about your use case, email types, expected volumes, and how you handle bounces and complaints, as this is what the SES team evaluates. Make sure your domain is fully verified with SPF, DKIM, and DMARC, and that you emphasize it’s strictly for transactional emails to opted-in users. Approval usually takes 1–2 business days if all compliance requirements are met.
Thanks and regards,
Taz
answered 9 months ago
Relevant content
asked 24 days ago
asked 2 months ago

Thank you so much for this detailed response! This is exactly what I was looking for. Update on my situation: Option 1 (Console): I can see the "Request production access" option in my SES Console, which is great news that this process has been simplified. Option 2 (CLI): When I tried the CLI approach, I got:
An error occurred (ConflictException) when calling the PutAccountDetails operation: None
This appears to be because I already have an existing case (173810619900626) from a previous request attempt that shows "More information needed" status. The CLI won't allow duplicate requests. Current status:
Existing case shows "Resolved" but with "More information needed" Cannot reopen the case without Business Support subscription CLI blocked due to existing case conflict Console form available but unsure if it will conflict with existing case
Questions for the community:
Has anyone successfully used the console form when they had an existing case? Should I proceed with the console form despite the existing case, or could this create complications? Any recommendations on handling the existing case situation?