# AWS End User Messaging endpoints and quotas
<a name="end-user-messaging"></a>

To connect programmatically to an AWS service, you use an endpoint. AWS services offer the following endpoint types in some or all of the AWS Regions that the service supports: IPv4 endpoints, dual-stack endpoints, and FIPS endpoints. Some services provide global endpoints. For more information, see [AWS service endpoints](rande.md).

Service quotas, also referred to as limits, are the maximum number of service resources or operations for your AWS account. For more information, see [AWS service quotas](aws_service_limits.md).

The following are the service endpoints and service quotas for this service.

AWS End User Messaging includes the AWS End User Messaging SMS and Voice V2 API and AWS End User Messaging Social API.

## Service endpoints
<a name="end-user-messaging_region"></a>

### AWS End User Messaging SMS and Voice V2 API
<a name="end-user-messaging-sms-voice-v2"></a>

[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/general/latest/gr/end-user-messaging.html)

### AWS End User Messaging Social API
<a name="end-user-messaging-social"></a>


**Region availability**  

| Region name | Region | Endpoint | WhatsApp API version | 
| --- | --- | --- | --- | 
| US East (N. Virginia) | us-east-1 |  social-messaging.us-east-1.amazonaws.com social-messaging.us-east-1.api.aws social-messaging-fips.us-east-1.amazonaws.com social-messaging-fips.us-east-1.api.aws  | Version 20 and later | 
| US East (Ohio) | us-east-2 |  social-messaging.us-east-2.amazonaws.com social-messaging.us-east-2.api.aws social-messaging-fips.us-east-2.amazonaws.com social-messaging-fips.us-east-2.api.aws  | Version 20 and later | 
| US West (N. California) | us-west-1 |  social-messaging.us-west-1.amazonaws.com social-messaging.us-west-1.api.aws social-messaging-fips.us-west-1.amazonaws.com social-messaging-fips.us-west-1.api.aws  | Version 20 and later | 
| US West (Oregon) | us-west-2 |  social-messaging.us-west-2.amazonaws.com social-messaging.us-west-2.api.aws social-messaging-fips.us-west-2.amazonaws.com social-messaging-fips.us-west-2.api.aws  | Version 20 and later | 
| Africa (Cape Town) | af-south-1 |  social-messaging.af-south-1.amazonaws.com social-messaging.af-south-1.api.aws  | Version 20 and later | 
| Asia Pacific (Hong Kong) | ap-east-1 |  social-messaging.ap-east-1.amazonaws.com social-messaging.ap-east-1.api.aws  | Version 20 and later | 
| Asia Pacific (Taipei) | ap-east-2 |  social-messaging.ap-east-2.amazonaws.com social-messaging.ap-east-2.api.aws  | Version 20 and later | 
| Asia Pacific (Mumbai) | ap-south-1 |  social-messaging.ap-south-1.amazonaws.com social-messaging.ap-south-1.api.aws  | Version 20 and later | 
| Asia Pacific (Hyderabad) | ap-south-2 |  social-messaging.ap-south-2.amazonaws.com social-messaging.ap-south-2.api.aws  | Version 20 and later | 
| Asia Pacific (Tokyo) | ap-northeast-1 |  social-messaging.ap-northeast-1.amazonaws.com social-messaging.ap-northeast-1.api.aws  | Version 20 and later | 
| Asia Pacific (Seoul) | ap-northeast-2 |  social-messaging.ap-northeast-2.amazonaws.com social-messaging.ap-northeast-2.api.aws  | Version 20 and later | 
| Asia Pacific (Osaka) | ap-northeast-3 |  social-messaging.ap-northeast-3.amazonaws.com social-messaging.ap-northeast-3.api.aws  | Version 20 and later | 
| Asia Pacific (Singapore) | ap-southeast-1 |  social-messaging.ap-southeast-1.amazonaws.com social-messaging.ap-southeast-1.api.aws  | Version 20 and later | 
| Asia Pacific (Sydney) | ap-southeast-2 |  social-messaging.ap-southeast-2.amazonaws.com social-messaging.ap-southeast-2.api.aws  | Version 20 and later | 
| Asia Pacific (Jakarta) | ap-southeast-3 |  social-messaging.ap-southeast-3.amazonaws.com social-messaging.ap-southeast-3.api.aws  | Version 20 and later | 
| Asia Pacific (Melbourne) | ap-southeast-4 |  social-messaging.ap-southeast-4.amazonaws.com social-messaging.ap-southeast-4.api.aws  | Version 20 and later | 
| Asia Pacific (Malaysia) | ap-southeast-5 |  social-messaging.ap-southeast-5.amazonaws.com social-messaging.ap-southeast-5.api.aws  | Version 20 and later | 
| Asia Pacific (New Zealand) | ap-southeast-6 |  social-messaging.ap-southeast-6.amazonaws.com social-messaging.ap-southeast-6.api.aws  | Version 20 and later | 
| Asia Pacific (Thailand) | ap-southeast-7 |  social-messaging.ap-southeast-7.amazonaws.com social-messaging.ap-southeast-7.api.aws  | Version 20 and later | 
| Canada (Central) | ca-central-1 |  social-messaging.ca-central-1.amazonaws.com social-messaging.ca-central-1.api.aws social-messaging-fips.ca-central-1.amazonaws.com social-messaging-fips.ca-central-1.api.aws  | Version 20 and later | 
| Canada West (Calgary) | ca-west-1 |  social-messaging.ca-west-1.amazonaws.com social-messaging.ca-west-1.api.aws social-messaging-fips.ca-west-1.amazonaws.com social-messaging-fips.ca-west-1.api.aws  | Version 20 and later | 
| Europe (Frankfurt) | eu-central-1 |  social-messaging.eu-central-1.amazonaws.com social-messaging.eu-central-1.api.aws  | Version 20 and later | 
| Europe (Zurich) | eu-central-2 |  social-messaging.eu-central-2.amazonaws.com social-messaging.eu-central-2.api.aws  | Version 20 and later | 
| Europe (Stockholm) | eu-north-1 |  social-messaging.eu-north-1.amazonaws.com social-messaging.eu-north-1.api.aws  | Version 20 and later | 
| Europe (Milan) | eu-south-1 |  social-messaging.eu-south-1.amazonaws.com social-messaging.eu-south-1.api.aws  | Version 20 and later | 
| Europe (Spain) | eu-south-2 |  social-messaging.eu-south-2.amazonaws.com social-messaging.eu-south-2.api.aws  | Version 20 and later | 
| Europe (Ireland) | eu-west-1 |  social-messaging.eu-west-1.amazonaws.com social-messaging.eu-west-1.api.aws  | Version 20 and later | 
| Europe (London) | eu-west-2 |  social-messaging.eu-west-2.amazonaws.com social-messaging.eu-west-2.api.aws  | Version 20 and later | 
| Europe (Paris) | eu-west-3 |  social-messaging.eu-west-3.amazonaws.com social-messaging.eu-west-3.api.aws  | Version 20 and later | 
| Israel (Tel Aviv) | il-central-1 |  social-messaging.il-central-1.amazonaws.com social-messaging.il-central-1.api.aws  | Version 20 and later | 
| Middle East (Bahrain) | me-south-1 |  social-messaging.me-south-1.amazonaws.com social-messaging.me-south-1.api.aws  | Version 20 and later | 
| Middle East (UAE) | me-central-1 |  social-messaging.me-central-1.amazonaws.com social-messaging.me-central-1.api.aws  | Version 20 and later | 
| Mexico (Central) | mx-central-1 |  social-messaging.mx-central-1.amazonaws.com social-messaging.mx-central-1.api.aws  | Version 20 and later | 
| South America (São Paulo) | sa-east-1 |  social-messaging.sa-east-1.amazonaws.com social-messaging.sa-east-1.api.aws  | Version 20 and later | 

## Service quotas
<a name="limits_eum"></a>

### AWS End User Messaging SMS and Voice Service Quotas
<a name="limits_eum_sms"></a>

The following quotas apply to the SMS and MMS channel.


| Resource | Default quota | Eligible for increase | 
| --- | --- | --- | 
|  Spending threshold  |  USD \$11.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.  |  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 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.   | 
| 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 | No | 
| 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 | 

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.


| Resource | Default quota | Eligible for increase | 
| --- | --- | --- | 
|  Max 10DLC companies per AWS account  | 25 |  Yes  | 
|  Max 10DLC campaigns per 10DLC brand  | 10 |  Yes  | 
| Max 10DLC numbers per 10DLC campaign | 49 | No | 

The following quotas apply to protect configurations.


****  

| Resource | Default quota | Eligible for increase | 
| --- | --- | --- | 
| Number of protect configurations | 25 | No | 

The following quotas apply to the voice channel.


| 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 minuteIf 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 secondsIf 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: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/general/latest/gr/end-user-messaging.html) If your account is out of the sandbox, you can send messages to recipients in any country.  International 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 | 

For more information, see [Quotas for AWS End User Messaging SMS](https://docs.aws.amazon.com/sms-voice/latest/userguide/quotas.html) in the *AWS End User Messaging SMS User Guide*.

### AWS End User Messaging Social Service Quotas
<a name="limits_eum_social"></a>

The following quotas apply to the Social messaging channel.


| Resource | Default | 
| --- | --- | 
| WhatsApp Business Account (WABA) | 25 per region | 

For more information, see [Quotas for AWS End User Messaging Social](https://docs.aws.amazon.com/social-messaging/latest/userguide/load-balancer-limits.html) in the *AWS End User Messaging Social User Guide*.