The Amazon SES sandbox is the restricted mode every new Amazon SES account starts in, separately in each AWS Region. While you are in it, you can only send to verified addresses, with a cap of 200 emails per 24 hours at 1 email per second. To get out, you open the SES console, go to Account dashboard, then View Get set up page, then Request production access. AWS says it gives an initial response within 96 hours.
The form takes two minutes. Getting it approved takes preparation. This guide covers what AWS checks, the current form field by field, a written request for a newsletter you can adapt, and how to answer when AWS asks for more information or says no.
Key takeaways
- Sandbox limits: verified recipients only, 200 emails per 24 hours, 1 email per second, per Region.
- Verify a domain first: AWS calls domain verification before the request a best practice that gets approvals through faster.
- The form is short: mail type, website URL, up to 4 extra contacts, contact language and an acknowledgement. Your website and your follow-up replies carry the real argument.
- Have a written use case ready: consent source, list size, volume, and how you handle bounces, complaints and unsubscribes. AWS often asks for exactly this.
- Approval is per Region: production access in us-east-1 does nothing for eu-west-1.
What the Amazon SES sandbox restricts
AWS puts every new account in the sandbox to stop fraud and abuse. You can use every SES feature while you are there; the limits are about who you can send to and how much. The current restrictions, from the AWS production access documentation:
| Item | In the sandbox | With production access |
|---|---|---|
| Recipients | Only verified email addresses and domains, plus the SES mailbox simulator | Any recipient |
| Sending quota | 200 emails per 24-hour period | Varies by use case (shown on your Account dashboard) |
| Sending rate | 1 email per second | Varies by use case |
| Sending authorization | Neither you nor a delegate can send to non-verified addresses | Normal |
| Account-level suppression list | Bulk actions and suppression-management API calls disabled | Available |
| Sender identities | Must be verified | Still must be verified (From, Source, Sender, Return-Path) |
If you try to mail an unverified recipient while in the sandbox, SES rejects the message. Over SMTP you will see:
That error also appears when the sender is unverified, so check both sides before assuming it is a sandbox problem.
Testing while you wait
The SES mailbox simulator works inside the sandbox. Send to success@simulator.amazonses.com, bounce@simulator.amazonses.com, complaint@simulator.amazonses.com, ooto@simulator.amazonses.com or suppressionlist@simulator.amazonses.com to confirm your app processes deliveries, bounces and complaints correctly. Simulator mail does not count toward your daily quota or your bounce and complaint rates, though it is billed like normal mail and still limited by your send rate.
Before you request: what makes approval faster
Reviewers decide on very little information: your account, your verified identities, your website and anything you write in the case. Fix the obvious gaps before you click submit, because you cannot edit your details while a review is open.
- Pick the Region you will actually send from. Sandbox status and identities are per Region. Requesting access in the console's default Region and then sending from another one is a common, avoidable mistake.
- Verify your sending domain, not only an address. AWS states that verifying a domain before requesting production access helps get the request approved faster, and with a verified domain you can request access straight from the Get set up page. Set up Easy DKIM, a custom MAIL FROM and DMARC while you are there; our guide on how to verify a domain in Amazon SES has the exact records.
- Make the website match the mail. The URL you submit should show a working signup form, what subscribers will receive and how often, a privacy policy, and a real business identity. A parked domain or a "coming soon" page is a weak signal.
- Wire up bounce and complaint handling. Create an SNS topic or configuration-set event destination for Bounce and Complaint events and confirm, with the simulator, that your app suppresses those addresses. Turn on the account-level suppression list once you are out (in the sandbox its bulk actions are disabled).
- Prove unsubscribes work. A visible unsubscribe link in every marketing email, honored right away. Gmail already requires one-click unsubscribe for marketing mail from senders of more than 5,000 messages a day, so you need it regardless.
How to request production access in the SES console
These are the current field names in the SES console (checked against the AWS documentation in November 2026):
- Open the Amazon SES console and switch to the Region you plan to send from (top right).
- In the navigation pane, choose Account dashboard.
- In the banner that says "Your Amazon SES account is in the sandbox", choose View Get set up page, then Request production access.
- Mail type: choose Marketing or Transactional, whichever describes the majority of your mail.
- Website URL: the site that explains what you send.
- Additional contacts: up to 4 email addresses, comma-separated, that should receive account communications.
- Preferred contact language: English or Japanese.
- Acknowledgement: tick the box confirming you only send to people who explicitly requested your mail and that you have a process for bounce and complaint notifications.
- Choose Submit request. A banner confirms the request is under review.
UseCaseDescription parameter of the SES v2 PutAccountDetails API is marked deprecated. Your written explanation now goes into the support case if AWS asks for it, which is why you should prepare it in advance.Requesting access with the AWS CLI
Useful when you set up several Regions or automate account setup:
--production-access-enabled \
--mail-type MARKETING \
--website-url https://example.com \
--additional-contact-email-addresses ops@example.com \
--contact-language EN \
--region us-east-1
What to put in each field
| Field | Good answer | Avoid |
|---|---|---|
| Mail type | Marketing, if newsletters and promotions are most of your volume | Picking Transactional because it sounds safer, then sending campaigns |
| Website URL | The page with your signup form, or your home page if it links to it clearly | A login page, an app store link, a domain with no content |
| Additional contacts | A shared inbox someone reads daily (ops@, email@) | A personal address that leaves with an employee |
| Acknowledgement | Tick it only if the bounce/complaint process already works | Ticking it with nothing wired up |
A production access request that works for a newsletter
Write this once, keep it in a document, and paste it into the case when AWS asks for details (or add it proactively as a reply after submitting). Replace every bracketed value with true, specific numbers. Vague answers ("we follow best practices") are what get requests stalled.
Sending domain: [news.acme-outdoor.example], verified in SES with Easy DKIM,
custom MAIL FROM [bounce.news.acme-outdoor.example] and DMARC p=none.
What we send: a weekly newsletter (gear guides, new products, occasional
promotions) to subscribers who signed up on our website. Mail type: Marketing.
How we collect consent: signup form at [https://acme-outdoor.example/newsletter]
and an unchecked opt-in box at checkout. New subscribers receive a
confirmation email and are only added after clicking it (double opt-in).
We do not buy, rent or share lists. Current list: [18,400] confirmed
subscribers, all collected since [2023].
Volume: one send per week to the full list, plus a welcome email to new
signups (about [40] per day). Expected [80,000] emails per month,
peak [18,500] in one day.
Bounces: SES Bounce events go to an SNS topic consumed by our sending
platform. Hard bounces are suppressed immediately and never mailed again.
We also use the SES account-level suppression list.
Complaints: Complaint events are processed the same way; the address is
suppressed immediately. We alert our team if the complaint rate goes
above 0.05% or the bounce rate above 2%.
Unsubscribes: every email has a visible unsubscribe link and a
List-Unsubscribe header; requests are applied immediately.
Subscribers who have not opened or clicked in [6] months are removed.
Example of our content: [link to a past issue on the website]
Why this works: it answers the exact questions in the AWS sending review FAQ (how you acquired the list, how subscribe and unsubscribe work, how you track bounces and complaints) before anyone asks. The volume line also tells AWS what quota you need, which helps them size your initial limits.
Adapting it to other use cases
- SaaS product updates: say recipients are registered users, link your terms and notification settings page, and separate product announcements from account email.
- Ecommerce: distinguish order emails (transactional) from promotions (marketing); choose the mail type that is the majority by volume.
- Agency or platform sending for clients: explain how you vet clients, whether each client verifies its own domain, and how you stop a bad client from sending. Reviewers scrutinize multi-tenant use cases more.
Why AWS denies production access (and how to respond)
Requests are reviewed by the AWS Trust & Safety team, not by the general support engineers. Per the AWS Knowledge Center FAQ on production access, regular support cannot see the reason for a rejection or overturn it, and the conversation happens by email in the case. AWS rarely explains a denial in detail, but the patterns are consistent:
| Likely reason | What the reviewer sees | Fix before you reply |
|---|---|---|
| Brand-new account, no history | An AWS account created days ago asking to send marketing mail | Verify the domain, test with the simulator, and give specific numbers in your reply |
| Website does not match | Placeholder site, no signup form, no privacy policy | Publish the signup page and privacy policy, then reply with the URL |
| List source unclear | "We will email our leads" or "imported contacts" | State how every address opted in; drop any purchased or scraped segment |
| Cold outreach | Prospecting or "lead generation" campaigns | SES is not the right tool for unsolicited mail; AWS will not approve it |
| No bounce/complaint process | No mention of SNS, suppression or monitoring | Describe the exact pipeline and alert thresholds |
| Vague volume | "Millions of emails" | Give list size, frequency, monthly and peak daily volume |
When AWS asks for more information
This is the most common outcome for marketing requests and it is not a denial. Reply in the same case (Support Center), answer every question asked, and paste the full use-case text above. Keep it factual and specific. Short replies tend to restart the cycle.
When the request is denied
- Read the case reply; if it names a reason, fix that first.
- Review the AWS Acceptable Use Policy against your use case. If your model depends on unsolicited mail, no wording will change the answer.
- Reply to the case asking for reconsideration, listing the changes you have already made (not plans).
- If the Get set up page lets you submit a new request, do it only after the fixes are live.
If AWS will not approve you, other providers (SendGrid, Mailgun, Postmark and others) have their own reviews and may be a better fit. A setup that connects more than one provider also protects you if any single one pauses your account; see multi-server email routing.
After approval: initial quota, Regions and next steps
Once approved, the sandbox banner disappears and you can mail any recipient. AWS does not publish a fixed starting quota: the SES quota documentation says that outside the sandbox the daily quota and send rate "vary based on your specific use case". Check the real numbers under Account dashboard > Sending limits.
- Quotas grow with good sending. AWS may raise them automatically when you send close to your quota with low bounces and complaints. You can also request more through Service Quotas. Details and the throttling errors to plan for are in our guide to Amazon SES sending limits.
- Each Region is separate. Production access, quotas, identities and DKIM records are all per Region. Repeat the request in every Region you send from.
- Your reputation is now monitored. AWS places accounts under review at a 5% bounce rate or 0.1% complaint rate and may pause sending at 10% or 0.5% (from the SES enforcement FAQ). Our guide to Amazon SES bounce and complaint handling covers the pipeline.
- Do not send the whole list on day one. A new domain going from zero to 20,000 emails in an hour looks like a compromised account to mailbox providers. Ramp up with a schedule from our IP and domain warm-up guide.
- Know the cost. New SES accounts start on the Essentials plan at $0.16 per 1,000 emails, and you can switch to à la carte pricing at $0.10 per 1,000 (as of November 2026). See Amazon SES pricing for the full breakdown.
If you want a campaign tool on top of your approved SES account, eMailBase connects to SES as your own sending server, checks your SPF, DKIM and DMARC records, and can follow a warm-up schedule for new domains. You still own the AWS account and pay AWS directly. The full picture of running campaigns this way is in our pillar guide to Amazon SES email marketing.
Frequently asked questions
How long does it take to get out of the Amazon SES sandbox?
AWS says its support team provides an initial response within 96 hours. If they need more information, the case stays open until you reply, so a complete answer on the first follow-up is the fastest route. Plan your launch around the full 96 hours, plus time for one round of questions.
Can I use Amazon SES for marketing newsletters?
Yes. The production access form has a Marketing option for one-to-many promotional mail. What AWS will not accept is unsolicited mail: purchased lists, scraped addresses and cold prospecting. Opt-in newsletters with working unsubscribes are a normal SES use case.
Do I have to leave the sandbox in every AWS Region?
Yes. Sandbox status is unique per Region. If you send from us-east-1 and eu-west-1, you need production access, verified identities and DNS records for both.
Does getting production access cost anything?
No. There is no fee for the request itself. You pay per email sent (and for optional add-ons such as dedicated IPs) once you start sending, at the same rates as in the sandbox.
What happens if my bounce or complaint rate gets too high after approval?
The enforcement steps AWS documents are a review period and a sending pause. Under review you can still send but must fix the cause; if you do not, or the problem is serious, AWS can pause sending. A paused account cannot send until AWS accepts your fix, which you explain by replying to the case it opened.
Getting out of the Amazon SES sandbox is mostly about showing evidence before AWS asks for it: a verified domain in the right Region, a website that shows how people subscribe, a working bounce and complaint pipeline, and a specific written use case ready to paste. Do that work first and the request is a two-minute form; skip it and you will spend a week in back-and-forth replies.


