App-specific verification guide

AWS SNS SMS Sandbox Destination Verification

Use the sandbox only to verify destination phones whose recipients have authorized your AWS messaging test.

Authorized use onlyYou initiate your own verification request.
Live reference dataReview current inventory and rental terms.
Platform-controlledAWS controls delivery and acceptance.

How SMS reception for AWS works

An online SMS number is a phone number rented for the displayed period to receive a verification message for a request you initiate. After selecting AWS and a country with current inventory, ProSMS shows the assigned number and rental state. You enter that number in the official app or website, then return to the dashboard to monitor delivery. ProSMS does not create the account, submit the code for you, or decide whether the platform accepts a number.

SNS sandbox verification is an AWS developer workflow, not Amazon customer 2SV. OTP receipt verifies one regional destination and does not approve production sending. Because anti-abuse rules, carrier ranges, and account requirements change, a number receiving a message now does not predict the outcome of another request. Use this service only for an account, test project, or workflow you are legally authorized to manage.

Understand what the SNS sandbox verifies

New Amazon SNS SMS accounts begin in a sandbox where messages can be sent only to verified destination phone numbers. In a supported AWS Region, add the destination, choose its country and verification language, then enter the OTP received by that consenting recipient.

The verified destination is a testing resource, not proof of an Amazon shopping account or an AWS account owner’s identity. Verification is regional, so the same destination must be handled again in another Region where you intend to test.

Work within AWS delivery and retry controls

AWS says to use Resend verification if the OTP has not arrived within fifteen minutes, with up to five resends in twenty-four hours. Check country code, pending status, spending limits, recipient opt-in, carrier filtering, and network conditions before retrying.

A sent request can still encounter carrier delay, while an invalid destination or suspended AWS messaging capability stops delivery earlier. Track those states separately because console acceptance is not proof of carrier delivery.

Plan compliant production messaging

The sandbox supports testing with limits, including a maximum number of verified destinations and a waiting period before deletion. Production use requires the appropriate sandbox-exit process, origination identity, registrations, recipient consent, and country-specific obligations.

Do not use temporary recipients to manufacture testing scale or avoid sandbox restrictions. Keep test ownership documented, remove destinations according to AWS timing, and understand that a verified phone does not establish carrier acceptance of later production traffic.

Official guidance sources

Confirm the current flow against the platform documentation before requesting a code.

Steps to receive a AWS code

  1. Create or sign in to your ProSMS account, then confirm that your account has enough credits for the option currently displayed.
  2. Search for AWS, review countries with current inventory, and read the shown duration, message capability, and cancellation terms.
  3. Choose an option consistent with the account region and platform rules. Copy the complete number in international format.
  4. Open the official AWS application or website, start your own request, and enter the assigned number once.
  5. Keep the dashboard open while waiting. If a message arrives, keep the code private and enter it only in the official flow you just started.
  6. After completion, review the rental state. For an account you will keep, promptly replace temporary recovery details with a durable method you control.

Do not make repeated requests while the platform timer is running. Closely spaced attempts can invalidate an earlier code, trigger a waiting period, or change the delivery channel. Read the current on-screen prompt before trying again. If the platform offers an in-app confirmation, email, trusted-device prompt, or call, follow that official path instead of trying to force SMS delivery.

Choosing a country and rental type

The least expensive country is not automatically the best match. Prefer a country consistent with the profile, operating region, and terms for AWS. Check the calling code, local formatting, and message language. If a service expects a phone number from the same region as billing or residence information, a different country may be declined even when a message can technically reach the number.

A one-time rental fits a short request with a clear end and no expectation of future messages. A longer rental is more suitable when an authorized workflow needs multiple messages during the published period. Neither option replaces a stable personal or business number for an important account. Decide by considering later sign-ins, password resets, new-device confirmations, and access recovery.

What to check when the code does not arrive

First confirm that you selected the exact AWS service, copied the right country code, and entered the complete number without an extra local prefix. Check whether the platform sent the code to an existing session, email address, or trusted device. Also verify that the rental remains active and that a message has not appeared in another dashboard view.

If there is still no code, wait for the official timer before requesting another. Never share the number or code with someone claiming to be support. Do not let another person control your login session. Follow the cancellation or credit-return terms shown for the rental; the available action depends on its actual state and whether a valid message has already been received.

Protecting the account after verification

An SMS code is a short-lived credential. Enter it only in the official domain or application that you opened yourself. After access is established, review devices and sessions, remove unfamiliar access, use a unique password, and enable a durable authentication method supported by AWS. Store backup codes privately when the platform provides them.

If the rented number appears in recovery settings, replace it with a phone, email, or trusted device that you control before the rental ends. Temporary numbers can expire or return to inventory under the displayed terms. Leaving one as a recovery method can block a future challenge. For business accounts, document ownership, backup administrators, and a secure handover process.

AWS verification FAQ

Can an online number receive a AWS code?

An available number may receive SMS when AWS chooses that channel and accepts the range, but the platform controls delivery, eligibility, and any additional checks.

Can I use the number again later?

Rely only on the displayed rental duration and multiple-message capability. Do not treat a short rental as a permanent recovery number.

Are inventory and price fixed?

No. Availability and price may vary by country, inventory, rental mode, and demand. The nearby panel shows the latest reference data; the dashboard confirms the selectable option.

Is ProSMS part of AWS?

No. ProSMS is not affiliated with, endorsed by, or sponsored by AWS. The trademark is used only to describe the customer-selected service.