{"id":3926,"date":"2023-05-29T10:43:26","date_gmt":"2023-05-29T10:43:26","guid":{"rendered":"https:\/\/mailbluster.com\/blog\/?p=3926"},"modified":"2025-04-26T09:51:08","modified_gmt":"2025-04-26T09:51:08","slug":"increasing-ses-limits","status":"publish","type":"post","link":"https:\/\/mailbluster.com\/blog\/increasing-ses-limits","title":{"rendered":"How To Increase SES Limits: Empower Amazon SES"},"content":{"rendered":"\n

To exceed the SES limits you set when getting out of the Amazon SES sandbox<\/a>, you need to request an AWS SES sending limit increase for your SES quotas. Increasing your SES quotas allows you to scale your email-sending capabilities based on your business requirements. <\/p>\n\n\n\n

To go beyond SES limits, follow the guidelines provided in this article to initiate an AWS SES sending limit increase for AmazonSES<\/a>. <\/p>\n\n\n\n

However, before we delve into that, let’s understand the difference between increasing SES quotas and getting out of the sandbox.<\/p>\n\n\n\n

Difference Between Increasing SES Limits and Getting Out of the Sandbox<\/h2>\n\n\n\n

Amazon SES offers two features related to increasing email-sending capabilities: getting out of the sandbox and requesting the AWS limit increase for your SES quota. Here’s an explanation of each:<\/p>\n\n\n\n

\n
\n
\n
\n
\n
\n
Getting Out of the Sandbox<\/strong><\/th>Increasing SES Limits<\/strong><\/strong><\/th><\/tr><\/thead>
Your account is placed in the sandbox when you start using AWS SES. The sandbox provides a controlled environment to test and evaluate SES without the risk of misuse. In the sandbox, there are certain restrictions on email sending to prevent abuse. These restrictions include sending emails only to verified email addresses and limiting the number of emails you can mail daily.<\/td>Once you are out of the sandbox and in the production environment, you may have certain sending limits imposed on your AWS SES account. These limits are in place to ensure the stability and deliverability of your emails and prevent abuse. The specific limits depend on various factors, such as your AWS account’s age, sending history, and compliance with SES policies.<\/td><\/tr>
Getting out of the sandbox means moving from this restricted environment to a production environment. After getting out of the sandbox, you can send emails to any recipient, not just verified addresses, and the sending limits are increased.<\/td>You can request a sending quota increase if you need to send more emails than your account’s default limits allow. This involves submitting a request to AWS to raise your sending limits.<\/td><\/tr>
To get out of the sandbox, you must submit a request to AWS and follow their verification process. This involves providing additional information about your use case and verifying your email addresses or domains.<\/td>After providing information about your sending patterns, email content, and relevant business justifications, AWS will review your request and increase your sending limits if they think you are a valid sender.<\/td><\/tr><\/tbody><\/table>
Getting Out of the Amazon SES Sandbox vs. Increasing SES Limits<\/figcaption><\/figure>\n<\/div><\/div>\n<\/div>\n<\/div>\n<\/div><\/div>\n<\/div>\n<\/div>\n\n\n\n

In summary, getting out of the sandbox is the initial step to moving from a restricted environment to a production environment with fewer limitations on email sending.<\/p>\n\n\n\n

On the other hand, requesting a quota increase is done after leaving the sandbox to raise the sending limits beyond the default values imposed on your AWS account.<\/p>\n\n\n\n

How to Request for Increasing SES Limits?<\/h2>\n\n\n\n

After successfully getting out of the sandbox environment, you can request the AWS limit increase for your SES quota, as mentioned.<\/p>\n\n\n\n

Here is a video that can help you understand the guideline more clearly.<\/p>\n\n\n\n

\n