- Newest
- Most votes
- Most comments
AWS End User Messaging SMS includes an SMS simulator, which you can use to send text messages and receive realistic event records. The SMS simulator is a helpful way to view actual SMS event records. It's also useful for testing applications that use AWS End User Messaging SMS to send SMS messages. Messages sent to these destination phone numbers are designed to stay within AWS End User Messaging SMS, so they are not sent over the carrier network. These numbers are only for testing sms working internally without sending actual sms in the real world.
Hence we can’t use Simulator to verify new phone numbers. So in order to send messages and verify US number, you need origination identity. When you are trying to verify the US destination phone number, in order to verify them, please allow me to mention that, you should have a TFN or 10 DLC or a short code (any of them). Below is the doc which you can follow to see in order to send messages to US numbers we need origination identity [+].
[+] https://docs.aws.amazon.com/sms-voice/latest/userguide/phone-numbers-sms-by-country.html
Therefore please get any one of the origination identity and then please try again to verify the destination numbers.
It seems you're encountering an issue with verifying phone numbers in AWS End User Messaging, which is different from the previous SNS sandbox system you might be familiar with. Here are a few things to consider:
-
SMS Sandbox: When you start using AWS End User Messaging to send SMS messages, your AWS account is initially placed in the SMS sandbox. This is a safe environment for testing, but it restricts SMS sending to verified destination phone numbers only.
-
Verification Process: To verify a phone number, you need to add it to your account and then verify it with a one-time password (OTP). The system should send an OTP to the phone number you're trying to verify.
-
Phone Number Format: Ensure you're entering the phone number in the correct format, including the country code (e.g., +1 for the United States).
-
Check Spam/Blocked Messages: If you're not receiving the verification code, check your phone's spam or blocked messages folder.
-
AWS Account Region: Make sure you're in the correct AWS region when setting this up, as SMS capabilities can vary by region.
-
Service Limits: There might be service limits or restrictions on your account that are preventing the verification process.
-
Support: If you've tried multiple numbers and still can't receive verification codes, it might be worth contacting AWS Support for assistance.
-
Recent Changes: AWS has recently introduced new features for SMS protection, including phone number block/allow rules. While this shouldn't directly affect verification, it's worth being aware of recent changes to the service.
If you've double-checked all these points and are still unable to receive verification codes, it's recommended to reach out to AWS Support for further assistance, as there may be an account-specific issue or a temporary service problem.
Sources
VerifySMSSandboxPhoneNumber - Amazon Simple Notification Service
CreateSMSSandboxPhoneNumber - Amazon Simple Notification Service
AWS End User Messaging introduces phone number block/allow rules - AWS
answered 2 years ago
for a human looking at this, I checked #3 and #4, and the problem is with #2. The system should send OTP, but it doesn't
Relevant content
- AWS OFFICIALUpdated a year ago
Thank you, Makendran - you are an expert and AWS employee, so who am I to argue! But the experience on the page and in the documentation that I am following is inconsistent with your answer. It never says that I need to get TFN or 10DLC in order to verify the number. Not to mention that last time it took me over a month to get TFN (I don't think AWS issues 10DLC any more).
So, it looks like as an individual I cannot use SNS to send SMS to phone numbers. I assume it changed 2 years ago with additional vigilance to prevent SPAM. While the desire is admirable, the way AWS has implemented is just disastrous. There is no distinction between marketing messages and technical notifications about system status integrated with CloudWatch and other services. VERY disappointing. As certified AWS Instructor, I was trying to put it as part of my class - now I will have to explain to my students how limited is AWS service.
Dependent on the destination country, your SMS messages have different requirements that must be met to make sure they are delivered. Kindly refer the below Knowledge center article which explains the reason for it.
[+] https://repost.aws/knowledge-center/sns-resolve-origination-identity-error
AWS End User Messaging distinguishes between transactional and promotional messaging types. Transactional messages are used for time-sensitive information like password resets, one-time passwords, and system notifications .
However, even transactional messages still require compliance with opt-in requirements, particularly in countries with strict regulations like the United States .
For US-based messaging, AWS supports three types of origination identities: Toll-Free (TFN), 10DLC, and short codes . Toll-Free numbers are specifically designed for low-volume use cases with a maximum throughput of 3 Messages Per Second .
10DLC is intended for Application-to-Person (A2P) SMS in the United States and requires both company and campaign registration through The Campaign Registry (TCR).
[+] https://docs.aws.amazon.com/sms-voice/latest/userguide/registrations-tfn.html [+] https://docs.aws.amazon.com/sms-voice/latest/userguide/registrations-10dlc.html
Your phone number can't send messages until your registration has been approved.
[+] https://docs.aws.amazon.com/sms-voice/latest/userguide/phone-numbers-request.html