Guides · messaging · Verification-gated

Amazon SNS SMS - leave the sandbox and raise the spend limit

New AWS accounts can only text up to 10 verified phone numbers and spend $1 a month on SMS. To text real users you verify and test a number, open a support case to exit the SMS sandbox, raise the monthly spend quota, and register an origination identity where the destination country requires it.

Researched · not yet run liveLast researched 25 October 2026 · Amazon Web Services · provider site

Researched, not yet run live. Built from the provider’s official pages (linked below). A person hasn’t walked this flow end to end yet, so check each step against the source.

Who owns what

SMS sandbox status and the monthly SMS spend quota are per AWS account and per Region. Origination identities (phone numbers, sender IDs) are bought and registered in AWS End User Messaging SMS.

Have ready

  • aws/account-and-iam: An activated AWS account and a user allowed to use SNS and open Support cases.
  • Carrier registration for the destination country where required (e.g. US 10DLC or toll-free): Done through AWS End User Messaging SMS; see the country table. Compare twilio/a2p-10dlc for what US registration involves.
  • A real mobile phone to add and verify as a sandbox destination number (receives a one-time code). [2]Needed for: Add and verify a sandbox destination number
  • The website or app name that will send the SMS. [2]Needed for: Open the Exit SMS sandbox support case, Request a higher monthly SMS spend quota
  • Message type (one-time password, transactional or promotional), destination countries, a description of how users opt in, and the exact message templates. · Support asks for all of these; fields marked optional are still required in practice. [3]Needed for: Open the Exit SMS sandbox support case, Request a higher monthly SMS spend quota

Steps

Steps marked “human step” are ones only you can do: verapli never signs in, submits, pays or accepts terms for you.

  1. Pick the Region you will send SMS from

    Sandbox status and spend quota are per Region; use the same Region in every step and in the support case.

    • Guided by hand
  2. Add and verify a sandbox destination number

    In SNS > Text messaging (SMS) > Sandbox destination phone numbers, add your phone and type in the code it receives.

    • verapli co-pilot
    • Human step: You enter a 2-step code
    • After: Pick the Region you will send SMS from
    If something goes wrong (1)
    • Cannot delete a test number you added by mistake.: Numbers can be deleted only 24 hours after verification or the last verification attempt; wait and retry. [1]

    Where: https://console.aws.amazon.com/sns/home

  3. Send a test SMS to the verified number

    Publish a test message and confirm it arrives - AWS asks you to do this before exiting the sandbox.

    • Official API
    • After: Add and verify a sandbox destination number
  4. Open the Exit SMS sandbox support case

    Choose Exit SMS sandbox; it opens a Service quota increase case for SNS Text Messaging. Fill in website/app, message type, Region, countries, opt-in process and templates; under Requests pick the Region, General Limits and Exit SMS Sandbox. You press Submit yourself.

    • verapli co-pilot
    • Human step: You press submit
    • After: Send a test SMS to the verified number
    The provider says
    Initial response within 24 hours; longer if Support needs more information. [2]
    If something goes wrong (1)
    • Request refused because the use case does not fit AWS policy.: Make opt-in explicit and documented, remove promotional content from transactional templates, and reply on the case with the details. [2]

    Where: https://support.console.aws.amazon.com/support/home#/case/create?issueType=service-limit-increase

  5. Request a higher monthly SMS spend quota

    New accounts can spend only $1.00 a month on SMS. Open a quota case (SNS Text Messaging, General Limits, Account Spend Threshold Increase) with the new USD limit and a use-case description; above $10,000 add per-country details.

    • verapli co-pilot
    • Human step: You press submit
    • After: Pick the Region you will send SMS from
    The provider says
    Initial response within 24 hours. [3]

    Where: https://support.console.aws.amazon.com/support/home#/case/create?issueType=service-limit-increase

  6. Set the new Account spend limit in SNS

    After approval, edit Text messaging preferences and enter the new Account spend limit - otherwise the increase does not take effect.

    • verapli co-pilot
    • Human step: You press submit
    • After: Request a higher monthly SMS spend quota
    If something goes wrong (1)
    • Invalid Parameter error when saving the new limit.: Check the value matches what AWS Support approved; if it still fails, open a case. [3]

    Where: https://console.aws.amazon.com/sns/home

  7. Register an origination identity where requiredoptional

    Some countries (for example the US) require registering your company and number or sender ID before sending. Check the AWS End User Messaging SMS country table and complete registration there.

    • Guided by hand
    • Human step: The provider reviews it
    • After: Pick the Region you will send SMS from

    Where: https://docs.aws.amazon.com/sms-voice/latest/userguide/phone-numbers-sms-by-country.html

Terms and gotchas

Plain-English summary, not legal advice. Each card links its source.

Can get you bannedThe rules say

Only text people who opted in; AWS may refuse sandbox exit when the use case does not align with its policies, and the AUP bans unsolicited mass messages. Plain-English summary, not legal advice. [2]

Can cost moneyThe rules say

Spend quota can overshoot

SNS stops sending within minutes of passing the spend quota, so you can be billed slightly above it. [3]

Worth knowingThe rules say

The default $1.00 per month SMS quota blocks almost any real launch; request the increase early. [3]

What you end up with

Env varSecretFormatWhat it is
SNS_SMS_REGIONnot secretus-east-1Region whose SNS account is out of the SMS sandbox.

For agents

The same entry as JSON: /api/v1/entries/aws/sns-sms-sandbox · requirements /api/v1/requirements/aws/sns-sms-sandbox · terms /api/v1/terms/aws/sns-sms-sandbox.

Remote MCP (read-only, no auth)
claude mcp add --transport http verapli https://verapli.com/mcp

> "What do I need for Amazon SNS SMS - leave the sandbox and raise the spend limit, and how long will it take?"
  → tools/call requirements { "provider_id": "aws/sns-sms-sandbox" }

Sources

  1. Using the Amazon SNS SMS sandbox New accounts start in the SMS sandbox; only verified destination numbers; up to 10 verified numbers; numbers can be deleted only 24 hours after verification; origination identities; some countries require company registration (see AWS End User Messaging SMS country list). · accessed 25 October 2026 · official
  2. Moving out of the Amazon SNS SMS sandbox Verify and test a number, then Exit SMS sandbox opens a Service quota increase case (SNS Text Messaging): website or app, message type (OTP/Promotional/Transactional), Region, countries, opt-in description, templates; Requests section Region + General Limits + Exit SMS Sandbox; initial response within 24 hours; may be refused if the use case does not fit policy. · accessed 25 October 2026 · official
  3. Requesting increases to your monthly Amazon SNS SMS spending quota Default spending quota $1.00 USD per month for new accounts; increase via quota case (Account Spend Threshold Increase) with website/app, service description and opt-in process; extra per-country details above $10,000; initial response within 24 hours; after approval you must also raise Account spend limit in SNS text messaging preferences; SNS may overshoot the quota by minutes. · accessed 25 October 2026 · official
  4. Supported countries and regions for SMS messaging with AWS End User Messaging SMS Which countries require registration of the company / origination identity before sending (linked from the SNS sandbox page; not fetched in full). · accessed 25 October 2026 · official
  5. AWS Acceptable Use Policy Bans unsolicited mass messages and promotions. · accessed 25 October 2026 · official

Provider rules change. This page is generated from verapli registry version 2026.1025.316; spotted something out of date? Tell us. Amazon Web Services is not affiliated with verapli.