AWS SES production access: how to get approved in under 24 hours
Every new AWS SES account starts in sandbox mode — you can only send to verified email addresses, and your daily sending limit is 200. To send real campaigns, you need production access. Here's how to get approved, fast.
What sandbox mode actually means
| Restriction | Sandbox | Production (default) |
|---|---|---|
| Recipient addresses | Verified only | Anyone |
| Daily quota | 200 emails | 50,000 emails |
| Max send rate | 1 email/second | 14 emails/second |
| From address | Verified only | Any verified domain address |
| Bounce notifications | Simulated only | Real SNS notifications |
| Dedicated IPs | Not available | Available ($24.95/mo each) |
How to submit the request
AWS SES console → Account Dashboard → Request Production Access. Fill out the form carefully — what you write here determines whether you wait 4 hours or a week.
Form fields: exactly what to write
Mail type
Select Marketing if sending newsletters or promotional email. Select Transactional for receipts, password resets, and notifications. If you need both, select Marketing — it covers transactional too when specified in the description.
Website URL
Your actual live business website. AWS reviewers visit the URL. Make sure it is live, loads correctly, clearly describes your business, has a visible privacy policy link, and shows how visitors can subscribe to your email list. A coming-soon page is a rejection signal.
Use case description — word-for-word template
We operate [describe your business — e.g. "a SaaS product helping small businesses with X"] and use AWS SES to send [marketing newsletters / transactional emails / both] to customers and subscribers who have explicitly opted in via [double opt-in form on our website / account creation flow / checkout process].
Our current list has approximately [X] opted-in subscribers. We send [frequency — e.g. "one newsletter per week and automated onboarding sequences"]. We handle unsubscribes using SES Mailbox, which automatically processes RFC 8058 list-unsubscribe headers and one-click unsubscribes. Hard bounces and spam complaints are suppressed immediately via SNS notifications.
Our opt-in process: [describe in 1–2 sentences — e.g. "Visitors enter their email on our homepage. They receive a confirmation email and must click a link to confirm before receiving any campaigns."]. Expected monthly send volume: [X] emails.
Approval timeline data
| Scenario | Typical time |
|---|---|
| Well-written request + established domain (1+ year) + live website | 4–12 hours |
| Good request + newer domain (3–12 months) | 12–24 hours |
| Average request + new domain | 1–3 business days |
| Vague description or no website | 2–5 business days or rejected |
| First appeal after rejection | 1–3 business days |
| Submitted on a Friday | Add 1–2 business days to above |
Common rejection reasons and fixes
- Vague use case description: "I want to send marketing emails" → use the template above instead
- No website or broken website: fix it before applying; AWS reviewers visit the URL
- Domain created very recently (days ago): wait 7–14 days before applying
- No privacy policy on the website: add a basic privacy policy page
- Missing or invalid DNS records: set up SPF, DKIM, and DMARC before submitting
- History of policy violations on linked AWS accounts: contact AWS Support first
If you get rejected: the appeal process
- Reply directly to the rejection email — do not open a new support case
- Acknowledge the specific concern AWS raised
- Provide more detail about your opt-in process
- Include a sample of the confirmation email subscribers receive
- Link to your privacy policy and unsubscribe mechanism
- If you have existing subscribers, state the list size and source clearly
What happens after approval: scaling limits
Default production: 50,000 emails/day, 14 emails/second. To increase: Account dashboard → Request sending limit increase. Fill out a similar form. Increases are typically approved within 24 hours and scale to millions per day for legitimate high-volume senders.
Before you submit: make sure your domain has valid SPF, at least one DKIM signature, and a DMARC policy set to p=none with a rua address. AWS reviewers check DNS. Missing records are a yellow flag even if not an outright rejection reason.
Frequently asked questions
How long does AWS SES production access take to approve? +
Typically 4–24 hours for well-written requests from established domains. New domains (created within the last 7 days) often take 1–3 business days as AWS performs additional verification. Requests submitted on Friday afternoons often wait until Monday. Vague use case descriptions are the single most common cause of delays.
Can I be approved for production access on a brand new domain? +
Yes, but it takes longer. AWS prefers domains with at least some history and a visible website. If your domain was just created, consider waiting 7–14 days before applying, adding content to your website, and setting up SPF, DKIM, and DMARC records first. A domain with proper DNS records and a live website signals legitimacy.
What happens if AWS SES production access is rejected? +
Reply directly to the rejection email (do not open a new support case). Provide more detail about your opt-in process, include a sample confirmation email that subscribers receive, and link to your privacy policy and unsubscribe mechanism. First-time rejections for legitimate businesses are overturned on appeal in the vast majority of cases within 1–3 business days.
Does production access have a sending limit? +
Yes. The default production limit is 50,000 emails per 24 hours and 14 emails per second. To increase this, submit a new sending limit increase request in the SES console under Account dashboard → Request production access (the same form, updated). Most legitimate senders get limit increases approved within 24 hours.
Can I use AWS SES for cold email outreach? +
No. AWS SES requires prior consent from recipients. Cold email campaigns (sending to people who have not opted in) violate AWS Acceptable Use Policy and will result in account suspension, often permanently. AWS actively monitors complaint rates and takes swift action against spam sources. SES is for opted-in marketing and transactional email only.
What is the difference between marketing and transactional mail type in the application? +
Marketing covers newsletters, promotional campaigns, and any email whose primary purpose is commercial. Transactional covers receipts, password resets, account notifications, and other emails triggered by user actions. If you need both, apply for Marketing — it is the higher bar and the approval covers transactional use as well. You can specify both in the use case description.