

# Managing your Amazon SES sending limits
<a name="manage-sending-quotas"></a>

Your Amazon SES account has a set of sending quotas that regulate the number of email messages that you can send and the rate at which you can send them. Sending quotas benefit all Amazon SES customers because they help to maintain the trusted relationship between Amazon SES and email providers. Sending quotas help you to gradually ramp up your sending activity and decrease the likelihood that email providers block your emails because of sudden, unexpected spikes in your email sending volume or rate.

The following quotas apply to sending email through Amazon SES:
+ [**Sending quota**](quotas.md)—The maximum number of emails that you can send in a 24-hour period. This quota is calculated on a rolling time period. Every time you try to send an email, Amazon SES determines the number of emails that you sent in the previous 24 hours. As long as the total number of emails that you have sent in the past 24 hours is less than this daily maximum, your send request is accepted and your email is sent.

  If sending a message would exceed the daily maximum for your account, your call to Amazon SES is rejected.
+ [**Sending rate**](quotas.md)—The maximum number of emails that Amazon SES can accept from your account each second. You can exceed this quota for short bursts, but not for sustained periods of time.
**Note**  
The rate at which Amazon SES accepts your messages can be less than the maximum send rate for your account.
+ [**Maximum message size (MB)**](quotas.md)—The maximum email size that you can send. This includes any images and attachments that are part of the email after MIME encoding. For example, if you attach a 5MB file, the attachment size in the email after MIME encoding will be \$16.85MB (about 137% of the original file size).
**Note**  
We recommend you upload your attachments to cloud drives and include the URL of cloud drive attachment to reduce email size and improve deliverability. SES cannot guarantee that large emails will end up in the recipient mailbox as different mail servers will have varying size based policies.

Your Amazon SES sending quotas are separate for each AWS Region. For information about using Amazon SES in multiple AWS Regions, see [Regions and Amazon SES](regions.md).

When your account is in the Amazon SES sandbox, you can only send 200 messages per 24-hour period, and your maximum sending rate is one message per second. When you submit a request to have your account removed from the sandbox, you can also request that your quotas are increased at the same time. For more information about having your account removed from the sandbox, see [Request production access (Moving out of the Amazon SES sandbox)](request-production-access.md).

When your account has been removed from the sandbox, you can request additional quota increases at any time by creating a new case in the AWS Support Center. For more information, see [Increasing your Amazon SES sending quotas](manage-sending-quotas-request-increase.md).

**Note**  
Sending quotas are based on recipients rather than on messages. For example, an email that has 10 recipients counts as 10 against your quota. However, we don't recommend that you send an email to multiple recipients in a single call to the `SendEmail` API operation, because if the call fails, the entire email is rejected. We recommend that you call `SendEmail` once for every recipient.
+ To increase your sending quotas, see [Increasing your Amazon SES sending quotas](manage-sending-quotas-request-increase.md). 
+ To monitor your sending quotas by using the Amazon SES console or the Amazon SES API, see [Monitoring your Amazon SES sending quotas](manage-sending-quotas-monitor.md).
+ For information about the errors your application receives when you reach your sending quotas, see [Errors related to the sending quotas for your Amazon SES account](manage-sending-quotas-errors.md).

# Increasing your Amazon SES sending quotas
<a name="manage-sending-quotas-request-increase"></a>

Your account has the following quotas per your current region that can be increased.


| Resource | Default quota | Description | 
| --- | --- | --- | 
| Sending quota | 200 | Maximum number of emails that you can send in a 24-hour period for this account in the current AWS Region. | 
| Sending rate | 1 | Maximum number of emails that Amazon SES can accept each second for this account in the current AWS Region. | 

## Automatically increased sending quotas
<a name="automatically-increased-sending-quotas"></a>

When your account is out of the sandbox and you're sending high-quality production email, we might automatically increase the sending quotas for your account. Often, we automatically increase these quotas before you actually need them to be increased.

To qualify for automatic rate increases, all of the following statements have to be true:
+ **You send high-quality content that your recipients want to receive** –Send content that recipients want and expect. Stop sending email to customers who don't open your email.
+ **You send actual production content** – Sending test messages to fake email addresses can have a negative effect on your bounce and complaint rates. Also, sending messages only to internal recipients makes it difficult to determine if you're sending content that customers want to receive. However, when you send your production messages to non-internal recipients, we can accurately assess your email-sending practices.
+ **You send near your current quota** – To qualify for an automatic quota increase, your daily email volume should regularly approach the daily maximum for your account without exceeding it.
+ **You have low bounce and complaint rates** – Minimize the number of bounces and complaints that you receive. Having a high number of bounces and complaints can have a negative impact on your sending quotas.

## User requested increased sending quotas
<a name="user-requested-increased-sending-quotas"></a>

If your current sending quotas aren't adequate for your needs and we haven't automatically increased them, you can request an increase: 
+ **Sending quota or Sending rate** – Increase requests for either of these can be submitted through the *AWS Service Quotas console*. 

**To request an increase on your Amazon SES sending quotas using the Service Quotas console.**

1. Open the [Service Quotas console](https://console.aws.amazon.com/servicequotas/).

1. Select the region that you want the increase for by using the dropdown in the upper right-hand corner of the console (next to your account number).

1.  In the navigation pane, choose **AWS services**.

1. Choose **Amazon Simple Email Service (SES)**.

1. Choose a quota, and follow the directions to request a quota increase.

**AWS Support team SLA for increase requests types**  
In order to prevent our systems from being used to send unsolicited or malicious content, we have to consider each request carefully. If we're able to do so, we'll grant your request within the specified times listed below for the type of increase requested. However, if we need to obtain additional information from you, it might take longer to resolve your request. We reserve the right not to grant your request if your use case doesn't align with our policies.  
**Sending quota or Sending rate**: Up to 24 hours.

**Note**  
While the Service Quotas console is available in many different languages, the actual support is only provided in English. 

# Monitoring your Amazon SES sending quotas
<a name="manage-sending-quotas-monitor"></a>

You can monitor your sending quotas by using the Amazon SES console or through the Amazon SES API, whether by calling the Query (HTTPS) interface directly or indirectly through an [AWS SDK](https://aws.amazon.com/tools/), the [AWS Command Line Interface](https://aws.amazon.com/cli/), or the [AWS Tools for Windows PowerShell](https://aws.amazon.com/powershell/).

**Important**  
We recommend that you frequently check your sending statistics to ensure that you are not close to your sending quotas. If you are close to your sending quotas, see [Increasing your Amazon SES sending quotas](manage-sending-quotas-request-increase.md) for information about how to increase them. Don't wait until you reach your sending quotas to consider increasing them.

## Monitoring your sending quotas using the Amazon SES console
<a name="manage-sending-quotas-monitor-console"></a>

The following procedure shows you how to view your sending quotas using the Amazon SES console.

****

1. Sign in to the AWS Management Console and open the Amazon SES console at [https://console.aws.amazon.com/ses/](https://console.aws.amazon.com/ses/).

1. In the navigation pane, choose **Account dashboard**. Your sending quotas are shown under **Sending Limits**. Total emails sent, remaining sends, and percentage of sending quota used is displayed under **Daily email usage**.   
![\[Account dashboard showing sending limits, daily email usage, and SMTP settings for Amazon SES.\]](http://docs.aws.amazon.com/ses/latest/dg/images/account_dashboard.png)

1. To update the display, select the refresh icon in the upper right-hand corner of the **Daily email usage** box.

## Monitoring your sending quotas using the Amazon SES API
<a name="manage-sending-quotas-monitor-api"></a>

The Amazon SES API provides the `GetSendQuota` action, which returns your sending quotas. When you call `GetSendQuota` action, you receive the following information:
+ Number of emails you have sent during the past 24 hours
+ Sending quota for the current 24-hour period
+ Maximum send rate

**Note**  
For a description of `GetSendQuota`, see [Amazon Simple Email Service API Reference](https://docs.aws.amazon.com/ses/latest/APIReference/).

# Errors related to the sending quotas for your Amazon SES account
<a name="manage-sending-quotas-errors"></a>

If you attempt to send an email after reaching your daily sending quota (the maximum amount of email you can send in a 24-hour period) or your maximum sending rate (the maximum number of messages you can send per second), Amazon SES drops the message and doesn't attempt to redeliver it. Amazon SES also provides an error message that explains the issue. The way that Amazon SES produces this error message depends on how you attempted to send the email. This topic includes information about the messages you receive through the Amazon SES API and through the SMTP interface. 

For a technique that you can use when you reach your maximum send rate, see [ How to handle a "Throttling – Maximum sending rate exceeded" error](https://aws.amazon.com//blogs/messaging-and-targeting/how-to-handle-a-throttling-maximum-sending-rate-exceeded-error/) on the AWS Messaging and Targeting Blog.

## Reaching sending limits with the Amazon SES API
<a name="manage-sending-quotas-errors-api"></a>

If you attempt to send an email by using the Amazon SES API (or an AWS SDK), but you've already exceeded your account's sending limits, the API produces a `ThrottlingException` error. The error message includes one of the following messages:
+ `Daily message quota exceeded`
+ `Maximum sending rate exceeded`

If you encounter a throttling error, you should program your application to wait for an interval of up to 10 minutes, and then retry the send request.

## Reaching sending limits with SMTP
<a name="manage-sending-quotas-errors-smtp"></a>

If you attempt to send an email by using the Amazon SES SMTP interface, but you've already exceeded your account's sending limits, your SMTP client might display one of the following errors:
+ `454 Throttling failure: Maximum sending rate exceeded`
+ `454 Throttling failure: Daily message quota exceeded`

Different SMTP clients handle these errors in different ways.