Every new Amazon SES account starts in sandbox mode - a restricted environment designed to let you test your integration before sending to real recipients. In 2026, sandbox mode imposes three hard limits: 200 emails per 24-hour period, 1 email per second, and delivery only to email addresses you've manually verified in SES (AWS, Amazon SES FAQ, retrieved 2026-06-07).
These limits exist because AWS monitors sender reputation across all SES accounts. A single bad actor sending spam through SES damages the shared IP pool reputation for every legitimate sender. The sandbox prevents new accounts from doing damage while AWS evaluates the legitimacy of your sending use case.
Key Takeaways
- Sandbox mode limits you to 200 emails/day to verified addresses only - you can't reach your real subscriber list.
- Production access requires a support request describing your opt-in process, email type, and bounce/complaint handling.
- Most legitimate senders are approved within 1 business day; vague requests can delay approval by days.
- After approval, your initial production quota is 200 emails/day - you request increases separately.
For the Mailblast-flavoured walk-through of these same AWS forms, see Moving out of the AWS SES Sandbox and Raising your AWS SES sending limit in the help docs. For the wider SES setup picture, see our SES setup guide.
What Sandbox Mode Means in Practice
Sandbox mode is not a trial period with limited features - it's a delivery restriction. Every email you send in sandbox mode must go to an address you've explicitly verified by clicking a confirmation link in an AWS verification email.
This means you can:
Test your technical integration (SMTP connection, API calls, template rendering)
Verify your domain setup (DKIM, SPF, DMARC)
Send test emails to your own verified email addresses
You cannot:
Send to your actual subscriber list
Send to customers or prospects
Test campaigns at any meaningful volume (200/day is roughly one small test per day)
The sandbox is a useful environment for confirming your technical setup before you go live. Most teams spend 1–3 days in sandbox, then immediately request production access.
How to Request Production Access
Navigate to the SES console → Account Dashboard → Request Production Access.
AWS provides a form with several fields. What you write here determines approval speed.
Use case description field - what to write:
A vague description ("I want to send marketing emails") gets slower review or denial. A specific description gets same-day approval for most legitimate senders.
Include:
Who you're sending to: Describe your audience and how they opted in (e.g., "customers who signed up at our website checkout and checked the marketing email consent box")
What you're sending: Describe the email type (newsletters, promotions, transactional, or all three)
Your consent collection method: Double opt-in or single opt-in; how you record consent
How you handle bounces: Describe your SNS setup or the frontend tool that handles suppression
How you handle unsubscribes: Every marketing email includes a one-click unsubscribe; you process requests within X days
Expected monthly volume: Give a specific number
Example approval-ready description:
We operate a B2B SaaS product (yourtool.com) and send weekly product update newsletters and occasional promotional emails to subscribers who signed up via our website. All subscribers opt in via a double opt-in process: they enter their email, receive a confirmation email, and are only added to our list after clicking the confirmation link. We process all bounces and complaints via Amazon SNS and our frontend tool (Mailblast) which automatically suppresses future sends to bounced or complaining addresses. We expect to send approximately 20,000 emails per month.
What Happens After Approval
Approval grants you production access - but doesn't immediately give you unlimited sending. Your initial production quota is typically 200 emails/day in the first 24 hours, scaling automatically as AWS observes your sending behavior.
Most accounts see their limits increase to:
50,000 emails/day within the first 7–14 days of consistent sending
200,000+ emails/day after 30 days of clean sending history
If you need higher limits faster, you can submit a separate quota increase request through AWS Support at any time.
Requesting Sending Limit Increases
Once in production, sending limit increases are routine. In the SES console under Account Dashboard, you'll see your current sending quota and a button to request an increase.
AWS evaluates increase requests based on:
Your current bounce and complaint rates (must be in safe zones)
Your sending history and consistency
The additional volume you're requesting
Requests for reasonable increases from senders with clean records are typically approved within 24–48 hours (AWS, Managing Amazon SES sending limits, retrieved 2026-06-07). For the full criteria AWS uses when auto-raising quotas (and what to write in a manual request), see Raising your AWS SES sending limit and our SES deliverability guide.
Common Reasons for Production Access Denial
Insufficient use case description. AWS can't approve what it doesn't understand. More detail is always better.
No mention of consent practices. AWS requires that marketing email goes only to people who explicitly opted in. Not mentioning how you collect consent raises a flag.
No bounce/complaint handling described. AWS monitors your complaint rate. If your request doesn't describe how you handle complaints, reviewers assume you haven't set it up.
Unrealistic volume claims. Claiming you'll send 10 million emails/month as a new account raises scrutiny. Start with realistic near-term volume.
Account flags from sandbox abuse. If you've used the sandbox to try sending to non-verified addresses (which fails but is logged), this can flag your account for slower review.
Frequently Asked Questions
How long does Amazon SES production access approval take?
Most legitimate requests are approved within 1 business day. Requests with insufficient detail may take 3–5 business days or require follow-up from AWS. Providing specific, complete information about your consent practices and bounce handling in the initial request minimizes review time.
Can I send to my list while waiting for production access?
No. Sandbox mode only delivers to manually verified addresses. You cannot reach your actual subscriber list until production access is approved. Use the waiting period to complete your technical setup: verify your domain, configure DKIM, and set up bounce/complaint handling.
What's the sending limit after Amazon SES production access is approved?
Initial production access typically provides a 200 emails/day quota that scales automatically as you send. Most accounts reach 50,000+ emails/day within 30 days of consistent clean sending. You can request specific limit increases at any time through AWS Support.
Does being in Amazon SES sandbox affect deliverability?
No - sandbox mode is purely a sending restriction, not a deliverability issue. Your test sends to verified addresses will arrive normally. Once you move to production, your deliverability is determined by your domain reputation, IP warm-up, and list quality, not by sandbox history.