Amazon SES Sending Limits: How to Get Out of the Sandbox and Scale

Amazon Simple Email Service (SES) is the gold standard for reliable, cost-effective raw email delivery. Yet, for many developers and SaaS founders, the initial experience feels like hitting a brick wall. When you create a new Amazon SES account, AWS automatically places you in a restricted environment known as the “sandbox.”

The sandbox prevents accidental spamming and protects IP pool reputation, but it also means you cannot send to unverified addresses or scale your application. To build a production-ready setup, you need to understand how these limits work, how to draft a successful production access request, and how to manage your quotas as you grow.

What the SES Sandbox Actually Limits

When your AWS account is in the sandbox, Amazon SES enforces strict boundaries to verify that you are a legitimate sender:

• The 24-Hour Sending Quota: You are limited to sending a maximum of 200 messages per 24-hour period.
• The Maximum Send Rate: Your throughput is throttled at 1 message per second.
• Verified Recipients Only: You can only send email to verified email addresses and domains that you personally own and have validated within your SES console. If you try to send to an external user, SES will reject the API call.

These constraints exist because AWS uses shared IP pools for sandbox accounts. If a bad actor signed up and immediately blasted spam, it would degrade the reputation of those IPs, causing deliverability issues for legitimate senders. AWS evaluates your lift requests manually to ensure you have a valid, compliant use case.

How to Request Production Access

To move out of the sandbox, you must submit a formal request via the AWS Support Center. AWS engineers review these requests to protect their network, so generic or vague answers will result in a quick rejection.

Preparing Your Support Case

Navigate to the AWS Console, open the Support Center, and create a new case for “Service Limit Increase” under the “SES Service Limits” category. When filling out the form, pay close attention to these key details:

1. Mail Type: Clearly specify whether your mail is transactional (e.g., password resets, magic links, purchase receipts) or marketing (e.g., newsletters, product updates, user onboarding sequences).
2. Website URL: Provide your active company URL (e.g., https://sendops.dev) so reviewers can verify your business legitimacy.
3. Use Case Description: Explain exactly how your application generates email. Instead of writing “We need to send emails to users,” write a precise description: “Our SaaS application sends automated transaction receipts to registered users when they purchase a subscription, and password reset links upon request. We also send a weekly product update to users who have explicitly opted in via our signup form.”
4. Handling Bounces and Complaints: AWS wants to know how you process failures. Explain that you have configured Amazon SNS notifications to handle bounces and complaints automatically, and that you instantly suppress addresses that bounce or complain to preserve your sending reputation.
5. Unsubscribe Mechanisms: For marketing or bulk mail, explain how you handle opt-outs. Note that your templates include an explicit unsubscribe footer and that opt-out actions are processed instantly.

Typical Approval Timelines

AWS typically reviews and responds to production access requests within 24 to 48 hours. If they need more information, they will reply to the support ticket. Once approved, your daily sending limit usually jumps from 200 to 50,000 emails per day, and your send rate limit increases from 1 to 14 messages per second.

After Production Access: Managing Quotas as You Scale

Getting out of the sandbox is just the first step. As your application grows, you will eventually approach your initial 50,000 daily limit.

Requesting Quota Increases

AWS monitors your sending volume. If you regularly use a significant portion of your daily quota while maintaining excellent deliverability metrics, AWS may automatically increase your quotas. However, if you have an upcoming launch or marketing campaign and need an immediate bump, you can request an amazon ses quota increase through the same support portal. Always request increases at least a week before you actually need them.

Dedicated IPs vs. Shared IP Pools

By default, your production emails are sent via Amazon’s shared IP pools. This is highly cost-effective and sufficient for most senders under 100,000 emails per month. However, if you scale to hundreds of thousands of emails weekly, you should consider dedicated IP addresses. Dedicated IPs isolate your reputation from other senders, but they require a “warm-up” period to establish trust with major inbox providers.

Rate Pacing and Throttling

Your maximum send rate (e.g., 14/sec or 50/sec) is a hard ceiling. If your application attempts to push a batch of emails faster than this rate, the SES API will return a ThrottlingException or MessageRejected error. You must implement client-side rate limiting or a queue-and-retry mechanism in your codebase to smooth out large batches.

What Triggers a Quota Pause or Account Suspension

Your production access is not permanent. AWS continuously monitors your account health using two primary metrics:

• Bounce Rate: The percentage of sent emails that fail to deliver. You must keep your bounce rate under 5%. If your bounce rate exceeds 10%, AWS may pause your sending capabilities entirely.
• Complaint Rate: The percentage of recipients who mark your email as spam. Your complaint rate must remain under 0.1%. A complaint rate exceeding 0.2% is highly critical and will trigger an immediate review or suspension warning.

If you send marketing campaigns to an old list with typos or stale addresses, your bounce rate will spike. If you make it difficult to unsubscribe, users will click the spam button, driving up complaints. Setting up real-time alerting on these metrics is your only line of defense against sudden account pauses.

Operational Checklist for Scaling SES Sends

Before you start sending high volume, ensure your infrastructure meets modern standards:

• Authenticate Your Domains: Implement DKIM, SPF, and a custom MAIL FROM domain to ensure your emails pass DMARC alignment.
• Configure SNS Notifications: Set up Amazon SNS topics for bounce and complaint events. Ensure your application consumes these events to immediately update your suppression list.
• Set Up Real-Time Monitoring: You need a clear window into your SES health. While AWS CloudWatch tracks raw numbers, you should have a dedicated dashboard that flags quota utilization and delivery metrics.

Rather than building custom observability tooling from scratch, engineering teams can use SendOps to turn their raw Amazon SES setup into a complete email marketing and operations platform. SendOps sits directly on top of your own AWS account, giving you instant visibility into your bounce rates, complaint rates, and quota usage. It adds contacts, segments, campaigns, and alerting without forcing you onto an expensive managed provider or taking over your underlying infrastructure. Keep your cost-effective SES delivery, and let SendOps handle the platform layer.