Answer first: Request an Amazon SES sending quota or sending-rate increase through the AWS Service Quotas console (select your region → Amazon Simple Email Service → Sending quota or Sending rate). Success is higher when you document specific projected volume, keep bounce rates under ~5% and complaint rates under ~0.1%, show list consent and automated suppression via SNS, and describe a clear production use case. AWS targets a response within 24 hours; additional information can extend that.
Why SES Quota Increases Matter for Transactional and Business Email
Hitting the daily sending quota or maximum send rate stops legitimate mail. For SaaS onboarding, order confirmations, or password resets this creates immediate customer-visible failures. SES quotas are per AWS Region and count recipients, not just messages. Sandbox accounts start at 200 messages per 24 hours and 1 message per second; production quotas are higher but still finite until raised.
This guide focuses on preparation and the request itself. For the numbers and how limits work, see our Amazon SES Sending Limits and Quotas Explained and Amazon SES Sandbox vs Sending Quota. Moving out of the sandbox is covered separately in How to Move Amazon SES Out of the Sandbox.
When to Request vs Wait for Automatic Increase
AWS can automatically raise quotas when you regularly approach the current ceiling, maintain low bounce and complaint rates, and send real production traffic to external addresses. If volume is growing steadily and reputation metrics are healthy, waiting can be simpler.
- Request manually when you have a known peak (product launch, holiday campaign, onboarding surge) that will exceed current limits before automatic adjustment occurs.
- Request when automatic increases have not arrived after consistent high-quality volume.
- Do not request while still in the sandbox; complete the production-access request first.
Preparation Checklist Before You Submit
Reviewers look for concrete evidence that the increase matches real, compliant traffic. Vague or disproportionate requests are frequently reduced or denied.
- Current usage and projected volume: State exact current daily average and peak, plus the specific new daily quota and send rate you need (for example, “raise from 50,000 to 150,000 messages per day and from 14 to 40 messages per second”). Tie the number to a documented list size, campaign cadence, or transaction rate.
- Reputation metrics: Include recent bounce rate (ideally well under 5%) and complaint rate (ideally under 0.1%). Pull these from the SES Reputation dashboard.
- List source and consent: Describe how addresses were collected (double opt-in preferred, single opt-in with clear consent language, or transactional only). Avoid purchased or scraped lists.
- Automated handling: Confirm SNS notifications for bounces and complaints are configured and that you suppress addresses automatically. See Amazon SES Suppression Lists.
- Unsubscribe and feedback loops: Show a working one-click or preference-center unsubscribe for any marketing mail and that you honor it promptly.
- Use-case description: Clear paragraph on what the mail is (transactional receipts, product notifications, etc.) and why volume will rise.
- Monitoring in place: Mention CloudWatch alarms or SES event destinations for throttling, bounce spikes, and complaint rates. Related: Amazon SES Rate Limit Errors.
How to Submit the Request in Service Quotas
- Open the AWS Service Quotas console.
- Select the correct AWS Region in the top-right dropdown (quotas are regional).
- In the navigation pane choose AWS services, then Amazon Simple Email Service (SES).
- Select “Sending quota” or “Sending rate” and follow the prompts to request an increase.
- Enter the new value and the supporting details from the checklist above.
Documented SLA is up to 24 hours. Support communication is English-only. If AWS needs more information the timeline extends. Approved increases take effect immediately.
What Happens If the Request Is Denied or Reduced
Common reasons include incomplete evidence, rates that appear too high relative to history, or use cases that do not match AWS policies. You can submit a new request after improving metrics or providing clearer documentation. There is no fixed waiting period, but repeating an identical weak request is unlikely to succeed. Continue sending high-quality mail in the meantime so automatic increases remain possible.
How We Analyzed This
Guidance is drawn from the current AWS documentation on managing and increasing SES sending quotas (Service Quotas console flow and 24-hour SLA), observed review criteria in AWS support threads, and ArawaMail’s published SES guides. ArawaMail is a separate platform with its own transactional sending limits and Cloudflare-managed authentication; it does not replace the SES quota process. For teams that want managed inboxes plus sending without operating SES quotas, see ArawaMail vs Amazon SES and our transactional email overview.
FAQ
When should I request a quota increase instead of waiting for automatic adjustment?
Request when you have a concrete near-term volume increase that will exceed current limits, or when consistent production traffic has not triggered an automatic raise. Automatic increases favor accounts that stay near the ceiling with low bounce and complaint rates.
What evidence most improves approval odds?
Specific numbers, low recent bounce/complaint rates, proof of consent and list hygiene, working SNS bounce/complaint handling, and a clear use-case description.
How is a quota increase different from leaving the sandbox?
Sandbox exit is a one-time production-access request that raises you from the 200/day default. Quota increases apply after you are already in production and need higher daily volume or send rate.
How long does approval take?
AWS documents up to 24 hours for sending-quota or sending-rate requests. Extra questions from Support can extend the timeline.
Can I request increases for both quota and rate at once?
Yes. Submit separate requests if needed; both are handled through the same Service Quotas console path.