Additional Information for SES Production Access - Case 177776930100618

Question

Hello AWS Support Team,

Thank you for the follow-up. Please find the detailed information regarding our use case for milkiyat.com:

1. Use Case Description
We are a real estate listing platform based in Pakistan. We will use Amazon SES exclusively for transactional emails, specifically 6-digit One-Time Passwords (OTPs) required for user registration, multi-factor authentication (MFA), and password resets.

2. How we maintain recipient lists
We do not use or purchase third-party mailing lists. Our recipient list is 100% organic, consisting only of users who manually enter their email addresses into our sign-up or password recovery forms. Because the email sent is an OTP, it functions as a "Double Opt-In" mechanism—users only receive a second communication if they successfully verify their address.

3. Sending Frequency and Volume
Emails are sent on-demand, triggered by user actions on our website. We anticipate an initial volume of 100–500 emails per day as our user base grows.

4. Managing Bounces and Complaints
We have verified our domain milkiyat.com and implemented DKIM, SPF, and DMARC to ensure high deliverability and sender reputation. We monitor delivery health via the Amazon SES Reputation Dashboard. Our backend (FastAPI/Python) includes logic to log delivery failures, and we intend to implement SNS notifications for automated bounce/complaint handling as our volume increases.

5. Handling Unsubscribe Requests
As our emails are strictly transactional (account security and verification), they do not include marketing content. However, users can manage their account status or contact our support team to be removed from our database entirely.

6. Example Email Content

Subject: Your Milkiyat Verification Code
Body:
Hello [User Name],
Your 6-digit verification code for Milkiyat is: 529103
This code is valid for 10 minutes. If you did not request this code, please ignore this email.

7. Identity Verification
Our domain milkiyat.com is already a Verified Identity in the Stockholm (eu-north-1) region, and all DKIM records are active and valid via Cloudflare.

Thank you for your assistance in moving our account into production.

Best regards,
[Your Name/Sadiq]

re:Post Agent · Answer

Thank you for providing detailed information about your use case. To complete your request for production access in Amazon SES, you'll need to submit this information through the proper channels.

To request production access and move out of the Amazon SES sandbox:

1. Open the Amazon SES console at https://console.aws.amazon.com/ses/
2. In the navigation panel, choose Account dashboard
3. In the warning box at the top that says "Your Amazon SES account is in the sandbox", select "View Get set up page" followed by "Request production access"
4. In the account details modal, select the "Transactional" radio button since you'll be sending OTP verification emails triggered by user actions

Based on your description, transactional email is the correct category as these are one-to-one messages unique to each recipient, triggered by user actions such as registration or password reset requests.

The AWS Support team will review your request carefully. Once approved, you'll be able to send emails to any recipient, though you must continue to verify all identities used as "From," "Source," "Sender," or "Return-Path" addresses. It's good that you've already verified your domain milkiyat.com and implemented DKIM, SPF, and DMARC records, as this demonstrates proper email authentication practices.

Your use case for sending OTP verification codes aligns well with transactional email purposes, and your approach to managing deliverability and monitoring through the SES Reputation Dashboard follows AWS best practices.  
**Sources**  
[Request production access (Moving out of the Amazon SES sandbox) - Amazon Simple Email Service](https://docs.aws.amazon.com/ses/latest/dg/request-production-access.html)

Additional Information for SES Production Access - Case 177776930100618

Add your answer

Relevant content