Quotas for Amazon Pinpoint SMS
Your AWS account has default quotas, formerly referred to as limits, for each AWS service. Unless otherwise noted, each quota is Region-specific. You can request increases for some quotas, and other quotas cannot be increased.
To request a quota increase, see Requesting a quota increase.
Your AWS account has the following quotas related to Amazon Pinpoint SMS.
The following table lists the Requests Per Second (RPS) quota for each resource of the Amazon Pinpoint SMS and Voice v2 API. All Resources are eligible for a rate increase by following the directions by following the directions in Requesting a quota increase.
| Resource | Default quota rate (requests per second) |
|---|---|
| AssociateOriginationIdentity | 1 |
| AssociateProtectConfiguration | 1 |
| CreateConfigurationSet | 1 |
| CreateEventDestination | 1 |
| CreateOptOutList | 1 |
| CreatePool | 1 |
| CreateProtectConfiguration | 1 |
| CreateRegistration | 1 |
| CreateRegistrationAssociation | 1 |
| CreateRegistrationAttachment | 1 |
| CreateRegistrationVersion | 1 |
| CreateVerifiedDestinationNumber | 1 |
| DeleteAccountDefaultProtectConfiguration | 1 |
| DeleteConfigurationSet | 1 |
| DeleteDefaultMessageType | 1 |
| DeleteDefaultSenderId | 1 |
| DeleteEventDestination | 1 |
| DeleteKeyword | 1 |
| DeleteMediaMessageSpendLimitOverride | 1 |
| DeleteOptedOutNumber | 10 |
| DeleteOptOutList | 1 |
| DeletePool | 1 |
| DeleteProtectConfiguration | 1 |
| DeleteRegistration | 1 |
| DeleteRegistrationAttachment | 1 |
| DeleteRegistrationFieldValue | 1 |
| DeleteTextMessageSpendLimitOverride | 1 |
| DeleteVerifiedDestinationNumber | 1 |
| DeleteVoiceMessageSpendLimitOverride | 1 |
| DescribeAccountAttributes | 1 |
| DescribeAccountLimits | 1 |
| DescribeConfigurationSets | 1 |
| DescribeKeywords | 1 |
| DescribeOptedOutNumbers | 1 |
| DescribeOptOutLists | 1 |
| DescribePhoneNumbers | 1 |
| DescribePools | 1 |
| DescribeProtectConfiguration | 1 |
| DescribeRegistrationAttachments | 1 |
| DescribeRegistrationFieldDefinitions | 1 |
| DescribeRegistrationFieldValues | 1 |
| DescribeRegistrations | 1 |
| DescribeRegistrationSectionDefinitions | 1 |
| DescribeRegistrationTypeDefinitions | 1 |
| DescribeRegistrationVersions | 1 |
| DescribeSenderIds | 1 |
| DescribeSpendLimits | 1 |
| DescribeVerifiedDestinationNumbers | 1 |
| DisassociateOriginationIdentity | 1 |
| DisassociateProtectConfiguration | 1 |
| DiscardRegistrationVersion | 1 |
| GetProtectConfigurationCountryRuleSet | 1 |
| ListPoolOriginationIdentities | 1 |
| ListRegistrationAssociations | 1 |
| ListTagsForResource | 10 |
| ProtectConfiguration | 1 |
| PutKeyword | 1 |
| PutOptedOutNumber | 10 |
| PutRegistrationFieldValue | 1 |
| ReleasePhoneNumber | 1 |
| ReleaseSenderId | 1 |
| RequestPhoneNumber | 1 |
| RequestSenderId | 1 |
| SendDestinationNumberVerificationCode | 1 |
| SendMediaMessage | 1 |
| SendTextMessage | 1 |
| SendVoiceMessage | 1 |
| SetAccountDefaultProtectConfiguration | 1 |
| SetDefaultMessageType | 1 |
| SetDefaultSenderId | 1 |
| SetMediaMessageSpendLimitOverride | 1 |
| SetTextMessageSpendLimitOverride | 1 |
| SetVoiceMessageSpendLimitOverride | 1 |
| SubmitRegistrationVersion | 1 |
| TagResource | 1 |
| UntagResource | 1 |
| UpdateEventDestination | 1 |
| UpdatePhoneNumber | 1 |
| UpdateProtectConfiguration | 1 |
| UpdateProtectConfigurationCountryRuleSet | 1 |
| UpdatePool | 1 |
| UpdateSenderId | 1 |
| VerifyDestinationNumber | 1 |
SMS and MMS quotas
The following quotas apply to the SMS and MMS channel.
| Resource | Default quota | Eligible for increase |
|---|---|---|
|
Spending threshold |
USD $1.00 per account |
Yes, but spending limits vary by region. You must specify the region(s) in which you require an increase. |
|
Number of SMS messages that can be sent each second (sending rate) |
Varies depending on destination country and originating phone number. For more information, see Message parts per second limits in the Amazon Pinpoint User Guide. |
Yes, however, you might need to obtain a phone number that supports higher throughput. If you're unsure of which number type to use, contact AWS Support or your AWS Account Manager for more information If you use an alphanumeric Sender ID to send messages, you might be able to increase your throughput rate. To find out if a throughput increase is available for your Sender ID, Open an Amazon Pinpoint SMS support case to request a sender ID in the Support Center Console. In your request, include your existing Sender ID, the country in which you use that Sender ID, and the throughput rate you want to request. |
| Number of SMS and MMS messages that can be sent to a single recipient each second | 1 message per second | No |
| Number of Amazon SNS topics for two-way SMS | 100,000 per account | Yes |
| Number of Keywords for two-way SMS | 30 Keywords per number | Yes |
| Number of SMS, MMS, and Voice numbers | 25 per account | Yes |
| Number of dedicated phone numbers | 25 per account | Yes |
|
Number of opt-out lists Note: The required Default opt-out list counts against this quota. |
25 per account | Yes |
| Number of configuration sets | 25 per account | Yes |
| Number of event destinations | 5 per configuration set | No |
| Number of verified destination phone numbers while in SMS sandbox | 10 per account | Yes |
| Number of phone number pools | 25 per account | Yes |
| Number of origination identities that can be associated with a phone number pool | 100 per phone number pool | Yes |
10DLC quotas
The following quotas apply to SMS messages sent using 10DLC phone numbers. 10DLC numbers can only be used to send messages to recipients in the United States.
Protect configuration quotas
The following quotas apply to protect configurations.
| Resource | Default quota | Eligible for increase |
|---|---|---|
| Number of protect configurations | 25 | No |
Voice quotas
The following quotas apply to the voice channel.
Note
When your account is removed from the sandbox, you automatically qualify for the maximum quotas shown in the following table.
| Resource | Default quota | Eligible for increase |
|---|---|---|
| Number of voice messages that can be sent during a 24-hour period | If your account is in the sandbox: 20 messages | No |
| Number of voice messages that can be sent to a single recipient during a 24-hour period | 5 messages | No |
| Number of voice messages that can be sent per minute | If your account is in the sandbox: 5 calls per minute If your account is out of the sandbox: 20 calls per minute |
No |
| Number of voice messages that can be sent from a single originating phone number per second | 1 message per second | No |
| Voice message length | If your account is in the sandbox: 30 seconds If your account is out of the sandbox: 5 minutes |
No |
| Ability to send voice messages to international phone numbers |
If your account is in the sandbox, you can send messages to recipients in only the following countries:
If your account is out of the sandbox, you can send messages to recipients in any country. NoteInternational calls are subject to additional fees, which vary by destination country or region. |
No |
| Number of characters in a voice message | 3,000 billable characters, in words that are spoken 6,000 characters total, including billable characters and SSML tags |
No |
| Number of configuration sets |
10,000 voice configuration sets |
No |
Requesting a quota increase
If the value in the Eligible for Increase column in any of the preceding tables is Yes, you can request an increase for that quota.
To request a quota increase
-
Open the Support Center Console at https://console.aws.amazon.com/support/home
. -
In the left hand navigation choose Your support cases.
Choose Create case.
Choose the Looking for service quota increases? link.
In the Looking for service quota increases? window choose Create a case instead.
-
Under Service quota increase, do the following:
For Service, choose Pinpoint SMS.
-
(Optional) For Provide a link to the site or app which will be sending SMS messages, provide information about the website, application, or service that will send SMS messages.
-
(Optional) For What type of messages do you plan to send, choose the type of message that you plan to send using your long code:
-
One Time Password – Messages that provide passwords that your customers use to authenticate with your website or application.
-
Promotional – Noncritical messages that promote your business or service, such as special offers or announcements.
-
Transactional – Important informational messages that support customer transactions, such as order confirmations or account alerts. Transactional messages must not contain promotional or marketing content.
-
-
(Optional) For Which AWS Region will you be sending messages from, choose the AWS Region that you will be sending messages from.
-
(Optional) For Which countries do you plan to send messages to, enter the country or region that you want to purchase short codes in.
-
(Optional) In the How do your customers opt to receive messages from you, provide details about your opt-in process.
-
(Optional) In the Please provide the message template that you plan to use to send messages to your customers field, include the template that you will be using.
-
Under Requests, do one of the following:
For Region, choose your AWS Region.
-
For Resource Type, choose General Limits.
For Quota, choose the quota to change.
For New quota value enter a new value for the quota.
-
To request an increase to the same quota in an additional AWS Region, choose Add another request, and then choose the additional AWS Region and fill out the new request.
-
Under Case description, for Use case description, explain why you're requesting the quota increase.
-
Under Contact options, for Preferred contact language, choose the language that you prefer to use when communicating with the AWS Support team.
-
For Contact method, choose your preferred method of communicating with the AWS Support team.
-
Choose Submit.
The AWS Support team provides an initial response to your request within 24 hours.
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 this 24-hour period. However, if we need to obtain additional information from you, it might take longer to resolve your request.
We might not be able to grant your request if your use case doesn’t align with our policies.
