- Newest
- Most votes
- Most comments
Based on the information provided, it appears that you have not set up verified phone numbers in Amazon SNS, which is a prerequisite for sending SMS messages from AWS Lambda while your account is in the SMS sandbox.
According to the AWS documentation, when your AWS account is in the SMS sandbox, there are certain restrictions in place for sending SMS messages using Amazon SNS. Specifically, the documentation states:
"While your account is in the SMS sandbox, you can use all of the features of Amazon SNS, with the following restrictions:
1. You can send SMS messages only to verified destination phone numbers.
2. You can have up to 10 verified destination phone numbers.
3. You can delete destination phone numbers only after 24 or more hours have passed since verification or the last verification attempt."
[+] https://docs.aws.amazon.com/sns/latest/dg/sns-sms-sandbox-verifying-phone-numbers.html
To resolve the issue and start receiving SMS messages on your phone, you need to follow these steps:
- Create an origination identity in Amazon SNS.
- Add the destination phone number (your phone number) to the list of verified phone numbers.
- Verify the phone number by following the instructions provided by Amazon SNS.
Once you have verified your phone number, you should be able to receive SMS messages sent from your Lambda function using Amazon SNS.
If you want to move your account out of the SMS sandbox and remove the restrictions, you can create a case with AWS Support. The documentation provides guidance on this process:
"When your account is moved out of the sandbox, these restrictions are removed, and you can send SMS messages to any recipient."
[+] https://docs.aws.amazon.com/sns/latest/dg/sns-sms-sandbox-moving-to-production.html
Please let me know if you have any further questions or need additional assistance.
You're on the right track with your understanding of the origination identity requirements for sending SMS messages from AWS to US phone numbers.
Customers sending to the US and the US territories of Puerto Rico (PR), Guam (GU), Virgin Islands (VI), American Samoa (AS), will not be able to send messages over unregistered long codes or shared routes due to regulatory requirements implemented by US telecom providers [1] [1A].
In order to successfully send messages to US territory recipients (Puerto Rico (PR), Guam (GU), Virgin Islands (VI), American Samoa (AS)), you need to register a 10DLC [2] or a toll-free number (TFN) [3]. To send messages to US based recipients, you need to register a 10DLC or toll-free number, or a US short code [4]. TFNs currently have the shortest turn around time, thus I would suggest you to acquire [5] and register a TFN. 10DLCs have the possibility of higher throughput limits but have a turn around time of several weeks at this time.
[1] https://docs.aws.amazon.com/sns/latest/dg/channels-sms-originating-identities-long-codes.html [1A] https://docs.aws.amazon.com/sns/latest/dg/channels-sms-originating-identities-origination-numbers.html#sns-10dlc-product-comparison [2] https://docs.aws.amazon.com/sns/latest/dg/channels-sms-originating-identities-10dlc.html [3] https://docs.aws.amazon.com/sns/latest/dg/channels-sms-originating-identities-tfn.html [4] https://docs.aws.amazon.com/sns/latest/dg/channels-sms-originating-identities-short-codes.html [5] https://docs.aws.amazon.com/pinpoint/latest/userguide/settings-sms-request-number.html
Below is the AWS documentation which explains the comparison for US phone number types:
You can use the Amazon Pinpoint console to request your 10DLC. Follow these steps to set up 10DLC for use with your 10DLC campaigns:
- Register your company.
- (Optional, but recommended) Apply for vetting
- Register your campaign.
- Request your 10DLC number.
There are registration and monthly fees associated with using 10DLC, such as registering your company and 10DLC campaign. These are separate from any other monthly fees charged by AWS.
Relevant content
- asked 6 years ago
- asked 2 months ago
- asked 6 months ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
This was very helpful. Thank you.
I had begun this process, but got a little confused in the origination identity process. It looks to me like the origination identity for US phone numbers must be a short code or through a 10DLC campaign registration. It looks like the 10DLC route is cheapest (since I'm just in a learning mode, I'm not ready to spend the money for a dedicated short code).
Am I on the right track?
Thanks again, in advance, for any help anyone can offer.