←Back to AWS Concepts

Amazon SES Sandbox ​

The Amazon SES sandbox is a restricted environment where all new Amazon SES accounts begin. It allows users to explore SES capabilities in a controlled manner while protecting AWS’s infrastructure from misuse.

What the Sandbox Environment Includes ​

In the sandbox, you can only send emails to verified recipients, meaning you must first confirm ownership of an email address or domain before using it as a destination. This restriction ensures that new accounts cannot be used for spam or abuse, while still allowing safe and realistic testing.

To prevent large-scale misuse, the sandbox enforces both a sending quota and a sending rate. The quota limits you to 200 emails per 24 hours, while the rate restricts sending to 1 email per second. These limits encourage careful pacing and discourage aggressive or careless mass sending during the early stages of use.

Despite these constraints, the SES sandbox gives you full access to features such as SMTP sending, event publishing, bounce/complaint tracking, and email templates. This makes it ideal for development and integration work, letting teams validate their email infrastructure in a safe environment.

To move beyond the sandbox and reach unverified recipients or higher volumes, users must apply for production access by submitting a request through the AWS Support Center.

Practical Guide

Learn how to successfully apply and maintain AWS SES production access with our detailed step-by-step guide.

How the Amazon SES Sandbox Works ​

When your account is created, it automatically begins in sandbox mode. Emails can only be sent to domains or email addresses you’ve verified. Address verification is done via a confirmation email link, while domain verification requires adding DNS records.

Your daily sending quota is capped at 200 emails, and your sending rate is restricted to 1 message per second. These numbers are not adjustable in the sandbox and are enforced globally across your SES usage. However, all core SES functionality is available, making the sandbox a complete but limited version of the service.

If you attempt to exceed the send rate, SES will return a Throttling error. And if you try to send to an unverified recipient, SES will block the request. These safeguards help ensure only intentional, approved usage during the sandbox phase.

Why Amazon Implements the SES Sandbox ​

Amazon SES uses the sandbox model as a reputation safeguard for both AWS and the wider email ecosystem. It minimizes the risk of new users causing spam, phishing, or policy violations that could harm AWS's deliverability with major mailbox providers.

It also acts as a staging ground for users to build confidence with SES. While the sending limits may feel restrictive, they provide a safe space to test features, verify setup (e.g., SPF, DKIM, DMARC), and monitor delivery feedback. This gradual ramp-up process ensures that only compliant, trusted senders are allowed into production.

Understanding AWS SES Sandbox Exit Requirements ​

To move your SES account from sandbox to production, you must submit a formal request through the AWS Support Center. Your request should explain how you collect opt-in consent, what types of content you send (e.g., transactional or marketing), and how you handle bounces and complaints.

AWS will also evaluate whether you follow authentication best practices and whether your email content meets professional standards. Including an unsubscribe mechanism, a valid reply-to address, and clear sender identity increases the chances of approval. Maintaining a bounce rate below 5% and a complaint rate under 0.1% is strongly recommended for a smooth review process.

Frequently Asked Questions About AWS SES Sandbox ​

How long does my account have to stay in the sandbox? ​

There’s no mandatory waiting period. You can apply for production access immediately, but a short history of successful test sending can help demonstrate readiness.

Can I still use SES effectively while in the sandbox? ​

Yes. The sandbox includes full access to SES capabilities, so it’s suitable for development, integration, and validation of your sending system even if delivery is limited to verified addresses.

How do I verify a recipient email address? ​

Go to the SES console, select "Email Addresses", and click "Verify a New Email Address". An email with a confirmation link will be sent. Once clicked, the address becomes verified.

What happens if my production request is denied? ​

AWS typically provides a reason such as lack of opt-in evidence or missing unsubscribe links. You can revise your setup and reapply. If needed, AWS Support may clarify next steps.

Related Content ​

Send Consistent-looking & beautiful emails today!

Email communication is part of your product! Don't let it ruin your user's experience with your brand

Get started