# Getting started with AWS End User Messaging SMS
This topic shows you how to use the AWS End User Messaging SMS console to manage phone numbers, sender IDs, pools, and configuration sets, and then send test SMS messages. We recommend you use simulator phone numbers to test both sending and receiving an SMS message. The [workshop](https://catalog.workshops.aws/build-sms-program/en-US) is targeted for developers and technical individuals who are comfortable using the AWS Command Line Interface (AWS CLI) to run API commands. For more information about SMS, MMS, or origination identity pricing, see [AWS End User Messaging Pricing](https://aws.amazon.com//end-user-messaging/pricing/).
**Note**
When you set up a new AWS End User Messaging SMS account, it is placed in a sandbox for SMS, MMS, and voice message channels until you request production access. In the sandbox, you can access all of features of AWS End User Messaging SMS, with restrictions on your SMS, MMS, and voice messages.
For information about the SMS/MMS sandbox restrictions, see [The AWS End User Messaging SMS SMS/MMS sandbox](sandbox.md#sandbox-sms).
For information about the voice sandbox restrictions, see [AWS End User Messaging SMS Voice sandbox](sandbox.md#sandbox-voice).
When you're ready to move from the sandbox to production, create an AWS Support case for a **Service limit increase** request for each channel that you want to move.
**Tip**
If you want to send OTP or verification messages without managing phone numbers, you can use Notify. Notify lets you send templated messages using AWS-managed origination identities. For more information, see [What is AWS End User Messaging Notify?](notify.md).
**Topics**
+ [First time user tutorial](getting-started-tutorial.md)
+ [Add a verified destination phone number](verify-destination-phone-number.md)
+ [SMS/MMS and Voice sandbox](sandbox.md)
+ [Message part preview](getting-started-mpp.md)
+ [Simulator phone numbers](test-phone-numbers.md)
+ [Set a spending limit](spend-limit.md)
# Tutorial for sending a message using AWS End User Messaging SMS
This section provides an overview of the tutorial designed to help you start using AWS End User Messaging SMS.
**Intended Audience**
This tutorial is designed for system administrators and developers responsible for setting up, testing, and deploying AWS End User Messaging SMS.
**Features Used**
This tutorial shows you how to use the AWS End User Messaging SMS console to:
+ Create and configure a phone pool.
+ Request an origination identity, which is either a phone number or sender ID.
+ Create and configure a protect configuration.
+ Send a test SMS message with the SMS simulator.
**Time Required**
It should take about 10–15 minutes to complete this tutorial.
**Regional Restrictions**
There are no country or regional restrictions associated with using this solution.
**Resource Usage Costs**
There's no charge for creating an AWS account. However, by implementing this solution, you might incur some or all of the costs that are listed in the following table.
[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/sms-voice/latest/userguide/getting-started-tutorial.html)
**AWS account permissions**
The account that you use to sign in to the AWS Management Console has to be able to perform the following tasks:
+ Create a pool
+ Create a configuration set
+ Create an event destination
+ Send SMS messages
For more information about account permissions, see [Identity and access management for AWS End User Messaging SMS](security-iam.md).
## Step 1: Create a pool
The procedures in this section show you how to create a pool and add either a phone number or sender ID to the pool.
**To create a pool**
1. Open the AWS End User Messaging SMS console at [https://console.aws.amazon.com/sms-voice/](https://console.aws.amazon.com/sms-voice/).
1. In the navigation pane, under **Overview**, in the **Quick start** section, choose **Create pool**.
1. Under the **Pool setup** section, enter a name for your pool in **Pool name**.
1. Choose one of the following options:
+ **Phone number** – If you choose this option, under **Phone numbers available for association**, choose either:
+ **Request simulator number**, and in the **Country** dropdown list, choose the destination country and then **Request number**.
**Note**
A simulated phone number doesn't require registration. It generates realistic events and is used for testing. Messages sent from a simulator number can only be sent to other simulator destination numbers and aren't sent over the carrier network.
+ Choose a phone number that you've previously purchased.
+ **Sender ID** – If you choose this option, choose a sender ID from **Sender IDs available for association**.
1. Choose **Create phone pool**.
## Step 2: Create a configuration set
The procedures in this section show you how to create a configuration set, add a CloudWatch Events, Amazon Data Firehose, or Amazon SNS destination and choose the event types.
1. Open the AWS End User Messaging SMS console at [https://console.aws.amazon.com/sms-voice/](https://console.aws.amazon.com/sms-voice/).
1. In the navigation pane, under **Overview**, in the **Quick start** section, choose **Create set**.
1. Under the **Configuration set details** section, enter a name in **Configuration set name**.
1. For **Event destination setup**, choose either:
+ **Set up CloudFormation** (Recommended) to have CloudFormation create and configure CloudWatch, Amazon Data Firehose and Amazon SNS to log all events.
+ For **Event destination name** enter a name for the event destination.
+ Choose **Launch stack**.
+ A new browser window will open. Review the **Quick create stack** form and check any acknowledgements. Choose **Create stack**.
**Note**
Creating the CloudFormation stack can take up to five minutes.
+ When the status indicator for the CloudFormation stack on the **Create configuration set** page is **Stack created**, choose **Create**.
+ **Setup event destination** to manually set up the configuration set and event destination.
+ For **Event destination name**, enter a name for the event destination.
+ For **Destination type**, choose either CloudWatch, Amazon Data Firehose or Amazon SNS. For more information on how to setup these event destinations see [Set up Amazon CloudWatch event destination](configuration-sets-cloud-watch.md), [Set up Amazon Data Firehose event destination](configuration-sets-kinesis.md) and [Set up an Amazon SNS event destination](configuration-sets-sns.md)
+ Under **Event types**, choose the appropriate option:
+ **All SMS events (Recommended)** – Send all SMS events listed in [Event types](configuration-sets-event-types.md) to the event destination.
+ **Custom SMS events** – Choose specific SMS events to send to the event destination. To edit the list of events choose **Edit SMS event selection**. In the **Edit SMS event selection** window choose only the events that you want to log. Choose **Save selection**.
+ **All MMS events (Recommended)** – Send all MMS events listed in [Event types](configuration-sets-event-types.md) to the event destination.
+ **Custom MMS events** – Choose specific MMS events to send to the event destination. To edit the list of events choose **Edit MMS event selection**. In the **Edit MMS event selection** window choose only the events that you want to log. Choose **Save selection**.
+ **All voice events (Recommended)** – Send all voice events listed in [Event types](configuration-sets-event-types.md) to the event destination.
+ **Custom voice events** – Choose specific voice events to send to the event destination. To edit the list of events, choose **Edit voice event selection**. In the **Edit voice event selection** window choose only the events the you want to log. Choose **Save selection**.
+ Choose **Create**.
1. Choose **Create configuration set**
## Step 3: Create a protect configuration
The procedures in this section show you how to create a protect configuration to specify which countries AWS End User Messaging SMS can send messages to.
1. Open the AWS End User Messaging SMS console at [https://console.aws.amazon.com/sms-voice/](https://console.aws.amazon.com/sms-voice/).
1. In the navigation pane, under **Overview**, in the **Quick start** section, choose **Create configuration**.
1. Under **Protect configuration details** enter a friendly name for your protect configuration in **Protect configuration name**.
1. Under Country rules, select the countries you want to set rules for. For each country, choose whether to block, filter, or allow message sending. We recommend:
+ Setting block rules for countries you don't do business in.
+ Using filter rules for countries with high per-message costs or where you have SMS pumping concerns.
+ Setting allow rules for countries where you do not wish to use filter.
**Note**
Do not block the country that you are going to send a test message to in the next step.
1. In **Protect configuration associates** under **Association type**, choose **Configuration set association**. Under **Configuration sets available for association**, choose the configuration set you created in step 2.
1. Choose **Create configuration**.
## Step 4: Send a test message with the SMS simulator
**Note**
To add a verified destination phone number you must have an originator that's status is *Active*, see [View a phone number status and capabilities in AWS End User Messaging SMS](phone-numbers-status.md). If you don't have an *Active* originator then use a simulator phone number and a simulator destination phone number to send and receive the test SMS message.
The procedures in this section show you how to send a test SMS message to verify your environment is correctly configured.
1. Open the AWS End User Messaging SMS console at [https://console.aws.amazon.com/sms-voice/](https://console.aws.amazon.com/sms-voice/).
1. In the navigation pane, under **Overview**, in the **Quick start** section, choose **Test SMS sending**.
1. For **Originator**, choose either **Phone pool**, **Phone number** or **Sender ID** as the type of originator to send the test message. You then need to select the originator identity from the dropdown list.
1. (Optional) If you need a simulator phone number then choose **Request simulator number**. In the **Request simulator number** window choose a **Country** from the dropdown list and then choose **Request number**.
**Important**
Simulator phone numbers can only send to other simulator destination phone numbers however they behave like actual phone numbers without sending over the carrier network. You can not use a simulator phone number to verify a destination phone number. For example, US simulator phone numbers can only send to US destination simulator phone numbers.
1. In the **Destination number** section, choose either **Simulator number** or **Verified number** and then select the number from the dropdown list.
To view your current list of verified destination numbers choose **Verified number** then expand **Manage verified destination number**. If you don't have any verified destination phone numbers, or need to add a new verified destination phone number, do the following:
1. To verify a new destination phone number, choose **Verify new number**.
1. In the **Add phone number** window for **Destination phone number**, enter the phone number of the device to receive the test message. The phone number must start with a '\$1' and can't contain any spaces, hyphens, or parentheses. For example, `+1 (206) 555-0142` is not in the correct format, but `+12065550142` is.
1. Choose **Send verification code**.
1. The destination device will receive a verification code that is valid for 15 minutes. Enter the code the device received into the **Verification code** field.
1. Choose **Verify number**.
1. For **Configuration set**, choose the event destination to receive the event data.
1. For **Message body**, enter a custom SMS message.
1. Choose **Send test message**.
1. For **Event logs: CloudWatch**, choose the refresh button to display the event log of the test message.
**Tip**
Wait at least at 10 seconds after sending the test SMS message before refreshing.
## Next steps: Move from sandbox to production
After fully testing your SMS environment in the SMS sandbox, you can request to move to production.
1. Create an AWS Support case at [https://support.console.aws.amazon.com/support/home\$1/case/create?issueType=service-limit-increase](https://console.aws.amazon.com/support/home#/case/create?issueType=service-limit-increase).
1. Choose the **Looking for service limit increases?** link, then complete the following:
+ For **Service**, choose **AWS End User Messaging SMS (Pinpoint)**.
+ 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.
+ For **What type of messages do you plan to send**, choose the type of message that you plan to send by using your origination identity:
+ **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.
+ For **Which AWS Region will you be sending messages from**, choose the AWS Region that you will be sending messages from.
+ For **Which countries do you plan to send messages to**, enter the country or region that you want to purchase short codes in.
+ For **How do your customers opt to receive messages from you**, provide details about your opt-in process.
+ For **Please provide the message template that you plan to use to send messages to your customers**, include the template that you will be using.
1. Under **Requests**, complete the following sections:
+ For the **Region**, choose the AWS Region from which you will be sending messages.
**Note**
The Region is required in the **Requests** section. Even if you provided this information in the **Case details** section, you must also include it here.
+ For **Resource Type**, choose** General Limits**.
+ For the **Quota**, choose **SMS Production Access**.
+ For **New quota value**, enter 1.
1. Under **Case description**, for **Use case description**, enter any relevant details about this request.
1. (Optional) If you want to submit any further requests, choose **Add another request**.
1. Under **Contact options**, for **Preferred contact language**, choose whether you want to receive communications for this case in **English** or **Japanese**.
1. When you finish, choose **Submit**.
# Add a destination phone number while in the AWS End User Messaging SMS sandbox
**Note**
Verified destination phone numbers are only required for testing while your account is in the sandbox. If your account is in production, you don't need to add verified destination phone numbers.
When your account is in the SMS/MMS or voice sandbox you can only send messages to verified destination phone numbers. You can add up to 10 verified destination phone numbers to your account. Adding a verified destination phone number requires you to send a text or voice message to the destination phone number and then entering the code the device received.
Before you begin you need an origination identity in your account that is active and has text or voice message capabilities. If you don't have an origination identity available you can use **Origination simulator phone numbers** and **Destination simulator phone numbers ** to test sending and receiving messages. For more information about simulated phone numbers, see [Simulator phone numbers](test-phone-numbers.md). The origination identity can only send messages within its country or region. For example, an origination identity for the United States can only send verification messages to destination phone numbers in the United States.
**Important**
Simulator phone numbers can only send to other simulator destination phone numbers however they behave like actual phone numbers without sending over the carrier network. You can not use a simulator phone number to verify a destination phone number. For example, US simulator phone numbers can only send to US destination simulator phone numbers.
For more information about installing and configuring the AWS CLI, see the [AWS Command Line Interface User Guide](https://docs.aws.amazon.com/cli/latest/userguide/).
1. Add the phone number to your account by using the [create-verified-destination-number](https://docs.aws.amazon.com/cli/latest/reference/pinpoint-sms-voice-v2/create-verified-destination-number.html) CLI command.
At the command line, enter the following command:
```
aws pinpoint-sms-voice-v2 create-verified-destination-number --destination-phone-number PhoneNumber
```
In the preceding command, make the following changes:
+ Replace *PhoneNumber* with the E.164 formatted phone number to send the message to. For example, `+1 (206) 555-0142` is not in the correct format, but `+12065550142` is.
On completion the command will return the verified phone numbers `VerifiedDestinationNumberId` which is needed in the next steps.
1. Use the [send-destination-number-verification-code](https://docs.aws.amazon.com/cli/latest/reference/pinpoint-sms-voice-v2/send-destination-number-verification-code.html) CLI command to send a verification message to the device. Only the first verification code is free.
At the command line, enter the following command:
```
aws pinpoint-sms-voice-v2 send-destination-number-verification-code --verified-destination-number-id PhoneNumberID --verification-channel Channel
```
In the preceding command, make the following changes:
+ Replace *PhoneNumberID* with the `VerifiedDestinationNumberId` you received in the previous step.
+ Replace *Channel* with the channel to use to send the message. You need to have an origination identity that supports the channel you use. This can be `TEXT` or `VOICE` and is case sensitive.
The device should receive a message with a randomly generated code. You will need this code in the next step.
1. Use the [verify-destination-number](https://docs.aws.amazon.com/cli/latest/reference/pinpoint-sms-voice-v2/verify-destination-number.html) CLI command to send a verification message.
At the command line, enter the following command:
```
aws pinpoint-sms-voice-v2 verify-destination-number --verified-destination-number-id PhoneNumberID --verification-code Code
```
In the preceding command, make the following changes:
+ Replace *PhoneNumberID* with the `VerifiedDestinationNumberId` you received in the previous step.
+ Replace *Code* with the verification code the destination device received.
Upon successful completion the status of the verified destination phone number is `VERIFIED`. You can now send messages to the verified destination phone number while you are in the sandbox.
# SMS/MMS and Voice sandbox in AWS End User Messaging SMS
New AWS End User Messaging SMS accounts are placed into an SMS/MMS or voice sandbox. The sandbox protects both AWS customers and recipients from fraud and abuse. It creates a safe environment for test and development.
**Topics**
+ [SMS/MMS sandbox](#sandbox-sms)
+ [Moving from the SMS/MMS sandbox](#sandbox-sms-move-to-production)
+ [Voice sandbox](#sandbox-voice)
## The AWS End User Messaging SMS SMS/MMS sandbox
While your account is in the sandbox, you can use all of the SMS sending methods in the AWS End User Messaging SMS console or the `SendTextMessages` API. To send an MMS message you must use the `SendMediaMessage` API. However, the following restrictions are in place while your account is in the sandbox:
+ You have a monthly SMS spending limit of \$11.00 (USD).
+ You have a monthly MMS spending limit of \$11.00 (USD).
+ You can send SMS and MMS messages only to verified destination phone numbers. You can add up to 10 verified numbers.
+ The rules and restrictions for sending SMS and MMS messages to each destination country apply. For example, to send a message to a recipient in the United States, you must first request and register a US number.
+ To verify that you own a phone number, we send a verification code to that number. While the standard fees for each SMS message typically apply, we waive the fee for the first verification code for each phone number. For more information about SMS pricing, see the [AWS End User Messaging Pricing](https://aws.amazon.com//end-user-messaging/pricing/) page.
**Note**
Message and data rates apply for messages that you receive. We send one message per verification request.
+ You can delete a destination phone number. However, you must wait 24 hours after adding a phone number before you can delete it.
+ You can send SMS and MMS messages only to verified destination numbers. For more information about how to add a verified destination phone number, see [Add a verified destination phone number](verify-destination-phone-number.md).
You can remove these restrictions by requesting production access. For more information, see [Moving from the AWS End User Messaging SMS MMS and Voice sandbox to production](#sandbox-sms-move-to-production).
**Note**
If your account is observed to be sending suspicious SMS/MMS traffic, your account's ability to send messages may be paused. If this occurs, please follow the steps in [Moving from the AWS End User Messaging SMS MMS and Voice sandbox to production](#sandbox-sms-move-to-production) to gain production access.
## Moving from the AWS End User Messaging SMS MMS and Voice sandbox to production
After fully testing your SMS/MMS environment in the SMS/MMS sandbox, you can request to move to production. Moving from the SMS sandbox to production also applies to MMS capability.
**Note**
If your account is in multiple AWS Regions, you must submit a support request for each Region.
Complete all fields in the support case, even if they are labeled as optional.
**To move to production from the SMS sandbox**
1. Create an AWS Support case at [https://support.console.aws.amazon.com/support/home\$1/case/create?issueType=service-limit-increase](https://console.aws.amazon.com/support/home#/case/create?issueType=service-limit-increase).
1. On the **Create Case** page, complete the following:
+ Select **Account and Billing**.
+ For **Service**, choose **Service Quotas**.
+ For **Category** choose either **AWS End User Messaging SMS (Pinpoint)** or **AWS End User Messaging Voice (Pinpoint)**, depending on your request.
+ For **Severity**, choose **General Limits**.
1. Under **Requests**, complete the following sections:
+ For the **Region**, choose the AWS Regions from which you will be sending messages.
**Note**
The AWS Regions is required in the **Requests** section. Even if you provided this information in the **Case details** section, you must also include it here.
+ For **Resource Type**, choose** General Limits**.
+ For the **Quota**, choose **SMS Production Access**.
+ For **New quota value**, enter 1.
1. Under **Description**, for **Use case description**, enter any relevant details about this request. Include answers to the following:
+ 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/MMS messages.
+ For **What type of messages do you plan to send**, choose the type of message that you plan to send by 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.
+ For **Which countries do you plan to send messages to**, enter the country or region that you want to purchase short codes in.
+ In the **How do your customers opt to receive messages from you**, provide details about your opt-in process.
+ 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.
1. (Optional) If you want to submit any further requests, choose **Add another request**.
1. Choose **Next Step: Solve now or Contact us**. For **Preferred contact language**, choose whether you want to receive communications for this case in **English** or **Japanese**.
1. When you finish, choose **Submit**.
After we receive your request, we provide an initial response within 24 hours. We might contact you to request additional information.
## AWS End User Messaging SMS Voice sandbox
To help protect our customers from fraud and abuse, we place your account in a sandbox environment when you first create it. The sandbox environment also helps you test the channel to help establish your reputation. While your account is in the sandbox, you have full access to AWS End User Messaging SMS voice messaging, with the following restrictions:
+ You have a daily limit of 20 messages.
+ You can send a maximum of five voice messages to a single recipient during a 24-hour period.
+ You can send a maximum of five calls per minute.
+ The maximum voice message length is 30 seconds.
+ You can send voice messages only to specific countries. For more information, see [Voice quotas](quotas.md#quotas-voice).
+ For more information on how to add a verified destination phone number, see [Add a verified destination phone number](verify-destination-phone-number.md).
When you're ready to move your account out of the voice sandbox, create an AWS Support case for a **Service limit increase** request. For more information, see [SMS/MMS and Voice sandbox in AWS End User Messaging SMS](#sandbox).
**Note**
Before you request production access, you must send at least one voice message from your AWS End User Messaging SMS account. You can send a voice message by using the [SendVoiceMessage](https://docs.aws.amazon.com/pinpoint/latest/apireference_smsvoicev2/API_SendVoiceMessage.html) API.
# Message part preview
A single SMS message can contain up to 140 bytes of information. When a message contains more than the maximum number of characters, the message is split into multiple parts. Depending on the recipient's mobile carrier and device, multiple messages might be displayed as a single message, or as a sequence of separate messages.
If your message uses only characters in the GSM 03.38 character set, also known as the GSM 7-bit alphabet, it can contain up to 160 characters. If your message contains any characters that are outside the GSM 03.38 character set, it can have up to 70 characters. When you send an SMS message, AWS End User Messaging SMS automatically determines the most efficient encoding to use.
You are billed for each message part that is sent. Phone numbers have a limit on the number of message parts they can send each second. If your message is split into two message parts, you are billed for each message part. Use the message part preview before you send your SMS message to see how many message parts it is. For more information about supported character sets, see [SMS character limits](sms-limitations-character.md). For more information about message size and throughput, see [What are the Message Parts per Second (MPS) limits](sms-limitations-mps.md).
**Using the message part preview**
1. Open the AWS End User Messaging SMS console at [https://console.aws.amazon.com/sms-voice/](https://console.aws.amazon.com/sms-voice/).
1. In the navigation pane, under **Shortcuts**, choose **Message part preview**.
1. In the **SMS message** section, enter your SMS message. As you enter the message, the **Part preview** displays the encoding, number of characters, and SMS message parts.
# Simulator phone numbers in AWS End User Messaging SMS
You can use the SMS simulator that is included with AWS End User Messaging SMS to send text messages and receive realistic event records. The SMS simulator is also useful for:
+ Viewing actual SMS event records.
+ Testing applications that use AWS End User Messaging SMS to send SMS messages.
When using the SMS simulator, messages originate from a origination simulator phone number, and messages are sent to destination simulator phone numbers that you request. The simulator phone numbers are designed to stay within AWS End User Messaging SMS, so that messages are not sent over the carrier network. Origination and destination simulator phone numbers work with SMS and MMS.
**Topics**
+ [Origination simulator phone numbers](#test-phone-numbers-origination)
+ [Destination simulator phone numbers](#test-phone-numbers-destination)
## Origination simulator phone numbers
You can request a simulator phone number to use as your origination identity to send test SMS and MMS messages. The simulator phone number will have a country code from the country that you choose. When you use a simulator phone number as the origination identity you can only send messages to the destination simulator phone number from the same country. If you try to send to a different country the message will fail. For example, if you use a simulator phone number from the United States and try to send a message to United Kingdoms success simulator phone number an error is returned.
**Note**
AWS End User Messaging SMS currently supports origination simulator phone numbers in the United States.
You can request an origination simulator phone number through the SMS simulator in the AWS End User Messaging SMS console or with the AWS CLI. To request an origination simulator phone number in the AWS CLI follow the directions in [Request a phone number (AWS CLI)](phone-numbers-request.md#request-cli) tab and use `SIMULATOR` for the number type.
**Request an origination simulator phone number**
1. Open the AWS End User Messaging SMS console at [https://console.aws.amazon.com/sms-voice/](https://console.aws.amazon.com/sms-voice/).
1. Choose **Shortcuts** and then **Test SMS sending with SMS simulator**.
1. Under **Originator** choose **Phone number** and then choose the **request a simulator number** link.
1. In the **Request simulator number** window, for **Country** choose a country from the drop down list. Choose **Request number**.
## Destination simulator phone numbers
Destination simulator phone numbers are available in several countries and regions. For each country and region, there are phone numbers that generate message success events, and numbers that generate message failure events. The following table contains SMS/MMS simulator phone numbers for all of the countries and regions in which the simulator is available.
****
| Country | Event type | Phone number |
| --- | --- | --- |
| Australia | Success | \$161455944038 |
| Australia | Failure | \$161455944039 |
| Austria | Success | \$143676800442031 |
| Austria | Failure | \$143676800442032 |
| Belgium | Success | \$132460213922 |
| Belgium | Failure | \$132460213923 |
| Chile | Success | \$156229140630 |
| Chile | Failure | \$156229140631 |
| Czech Republic | Success | \$1420790542286 |
| Czech Republic | Failure | \$1420790542287 |
| Denmark | Success | \$14525919410 |
| Denmark | Failure | \$14525919215 |
| Estonia | Success | \$137282720792 |
| Estonia | Failure | \$137282720793 |
| Finland | Success | \$13584573979110 |
| Finland | Failure | \$13584573979111 |
| France | Success | \$133755512501 |
| France | Failure | \$133755512502 |
| Hong Kong | Success | \$185257048426 |
| Hong Kong | Failure | \$185257048854 |
| Hungary | Success | \$136707178770 |
| Hungary | Failure | \$136707178772 |
| Italy | Success | \$1394390009172 |
| Italy | Failure | \$1394390009174 |
| Jersey | Success | \$1447937404990 |
| Jersey | Failure | \$1447937404992 |
| Luxembourg | Success | \$1352691385880 |
| Luxembourg | Failure | \$1352691385882 |
| Netherlands | Success | \$13197008100148 |
| Netherlands | Failure | \$13197008100150 |
| Norway | Success | \$14759449384 |
| Norway | Failure | \$14759449387 |
| Poland | Success | \$148732141440 |
| Poland | Failure | \$148732141442 |
| Portugal | Success | \$1351927946948 |
| Portugal | Failure | \$1351927946950 |
| Romania | Success | \$140783900330 |
| Romania | Failure | \$140783900332 |
| Spain | Success | \$134683783440 |
| Spain | Failure | \$134683783442 |
| Sweden | Success | \$146790645100 |
| Sweden | Failure | \$146790645102 |
| Switzerland | Success | \$141798075872 |
| Switzerland | Failure | \$141798075874 |
| Taiwan | Success | \$1886903444630 |
| Taiwan | Failure | \$1886903444632 |
| United Kingdom | Success | \$1447860019066 |
| United Kingdom | Failure | \$1447860019067 |
| United States | Success | \$114254147755 |
| United States | Failure | \$114254147167 |
# Set an SMS, MMS or voice spending limit in AWS End User Messaging SMS
In AWS End User Messaging SMS there are spending limits for each messaging channel.
The *account limit* is the maximum amount, in US dollars, that you can spend each month sending messages through a channel. When you reach your account limit, AWS End User Messaging SMS stops sending your messages and, to send more messages that month, you need to request a spending limit increase. When you request a spending limit change to either your SMS or MMS *account limit* both your SMS and MMS *account limit* are set to the new requested limit. MMS and SMS have separate *enforced limit*. For example you could set you MMS *enforced limit* to \$110 and SMS *enforced limit* to \$15. To change your *account limit*, see [Requesting a spending quota change](awssupport-spend-threshold.md).
The *enforced limit* is an optional spending limit, in US dollars, between \$11 and the account limit. If you don't specify an enforced limit, you can spend up to your account limit. When you reach your enforced limit, AWS End User Messaging SMS stops sending your messages. To resume sending messages, you can adjust your enforced limit through the console or AWS CLI. For example, if you set your SMS account limit to \$1100 and your enforced limit to \$150, then once you've spent \$150, AWS End User Messaging SMS stops sending your messages until you raise your enforced limit.
The *remaining limit* is how much you have spent for the current month sending messages.
You can adjust your enforced limit to increase or decrease your spending without having to contact Support.
To set up billing alarms for your spending, see [Monitoring spending](monitor-spending.md). For more information about configuring the AWS CLI, see [Configure the AWS CLI](https://docs.aws.amazon.com/cli/latest/userguide/cli-chap-configure.html) in the [AWS Command Line Interface User Guide](https://docs.aws.amazon.com/cli/latest/userguide/). For more information about SMS, MMS, or origination identity pricing, see [AWS End User Messaging Pricing](https://aws.amazon.com//end-user-messaging/pricing/).
------
#### [ View your spending limits (console) ]
**View all of your spending limits**
1. Open the AWS End User Messaging SMS console at [https://console.aws.amazon.com/sms-voice/](https://console.aws.amazon.com/sms-voice/).
1. On the **Overview** page, navigate to **SMS Spending status**.
1. In the **SMS Spending status** pane, you can view your **Account limit**, **Enforced limit**, and **Remaining limit**.
If your **Enforced limit** displays a `–`, it means the limit is not set.
------
#### [ View your enforced spending limit (AWS CLI) ]
You can use the `[describe-spend-limits](https://docs.aws.amazon.com/cli/latest/reference/pinpoint-sms-voice-v2/describe-spend-limits.html)` command to view all of your channel spending limits.
```
aws pinpoint-sms-voice-v2 describe-spend-limits
```
When the command completes, it returns the **Account limit** and **Enforced limit** for each channel.
------
#### [ Change your enforced spending limit (Console) ]
**Change a spending limit**
1. Open the AWS End User Messaging SMS console at [https://console.aws.amazon.com/sms-voice/](https://console.aws.amazon.com/sms-voice/).
1. On the **Overview** page, navigate to **SMS Spending status**.
1. In the **SMS Spending status** pane, choose **Edit** for the channel for which you want to change the **Enforced limit**.
1. In the **Edit spending limits** window, choose:
+ **Update enforced spend limit** – Enter a new **Enforced limit** between one and your account limit.
+ **Default to the max send limit** – Choose this option to adjust your enforced limit to your account limit.
1. Choose **Save changes**.
------
#### [ Set enforced spending limit (AWS CLI) ]
You can use the `[set-text-message-spend-limit-override](https://docs.aws.amazon.com/cli/latest/reference/pinpoint-sms-voice-v2/set-text-message-spend-limit-override.html)` command to set the enforced limit for the SMS channel. For the voice channel, use the `[set-voice-message-spend-limit-override](https://docs.aws.amazon.com/cli/latest/reference/pinpoint-sms-voice-v2/set-voice-message-spend-limit-override.html)` command.
The following command shows how to increase the enforced limit for the SMS channel.
```
aws pinpoint-sms-voice-v2 set-text-message-spend-limit-override --monthly-limit NewEnforcedLimit
```
Replace *NewEnforcedLimit* with a value between one and the account limit of the SMS channel.
When the command completes, it returns the value of your new set limit.
------
#### [ Remove an enforced spending limit (AWS CLI) ]
You can use the `[delete-text-message-spend-limit-override](https://docs.aws.amazon.com/cli/latest/reference/pinpoint-sms-voice-v2/delete-text-message-spend-limit-override.html)` command to set your enforced limit to the account limit for the SMS channel. For the voice channel, use the `[delete-voice-message-spend-limit-override](https://docs.aws.amazon.com/cli/latest/reference/pinpoint-sms-voice-v2/delete-voice-message-spend-limit-override.html)` command.
The following command shows how to remove the enforced limit for the SMS channel.
```
aws pinpoint-sms-voice-v2 delete-text-message-spend-limit-override
```
When the command completes, it returns the value of your enforced limit.
------
**Note**
Notify has a separate spend limit that is independent of your SMS, MMS, and voice spend limits. For information about managing Notify spend limits, see [Notify spend limits](notify-spend-limits.md).