AWS End User Messaging

AWS End User Messaging — SMS as an AWS primitive: no vendor relationship, but registration is a support ticket. AWS End User Messaging (formerly Pinpoint SMS, and before that SNS SMS) is the roll-it-yourself baseline for this category. Credentials are instant given an existing AWS account, billing lands on an invoice from an Australian entity, and traffic runs in ap-southeast-2. The cost is friction of a different kind: Australian sender IDs require a support-ticket registration, there is no product surface beyond the API, and every feature other providers include — opt-out UI, campaign tooling, deliverability support — you build or go without. Built by Amazon Web Services. Founded 2016. We carry it as the do-it-yourself baseline, not as a vendor.

We track it in 1 comparison — AU SMS APIs — so every claim below is a cell in a table you can open and check rather than an impression. Across those rosters it sits against 12 other tools, and what follows is where it visibly separates from them.

Where it wins.

• Billing model — postpaid-self-serve, the best figure of the 13 here.
• SDK languages — node, python, php, ruby, java, dotnet, go, tied for best across 3 of 12 tools.

Each of those is ranked against the whole roster on its category page, not against a hand-picked subset, so a first place here means first of everything we list.

Where it gives ground.

• Carrier route — international-aggregator, 10th of 13. Telstra Messaging API records direct-carrier.
• MMS to AU — No. MessageMedia records Yes.
• RCS — No. Sinch records Yes.
• Operating since — 2016, the weakest of the 11 here. SMSGlobal records 1999.

None of these disqualify it on their own. They are the fields to check against your own requirements before you commit, because they are the ones where a competitor genuinely does better.

Provenance. 23 of 26 tracked fields carry a value for AWS End User Messaging, and 3 of those cite a document you can open. Last verified 2026-07-20. Every figure keeps its own provenance — measured by us, claimed by the vendor, inferred, or community-reported — and we would rather print a dash than a guess.

Its nearest neighbour in our data is Bird. AWS End User Messaging is ahead on Billing model (postpaid-self-serve against contract-required) and AU data residency (Yes against No). Bird takes MMS to AU (Yes against No) and RCS (Yes against No). That pattern repeats across the rest of the roster — see AWS End User Messaging alternatives for the other rivals, each compared the same way.

Company

Amazon Web Services

Founded

2016

Fields we track

23 of 26

Last verified

2026-07-20

The right reference point for whether a dedicated provider is worth its margin. On AWS already, the marginal cost of adding SMS is one IAM policy and a registration ticket — but there is no console, no deliverability support and nobody to escalate to when Australian delivery degrades.

Carrier route

international-aggregator10th of 13

Inferred

Billing model

postpaid-self-serve1st of 13

Inferred

MMS to AU

○No9th of 12

Inferred

SDK languages

nodepythonphpruby+31st of 12

Vendor-claimedverified 2026-07-20source

RCS

○No9th of 10

Inferred

Operating since

201611th of 11

Inferred

Price /SMS @ 10k

A$0.07 /SMS6th of 8

Inferred

Price /SMS @ 100k

A$0.07 /SMS6th of 8

Inferred

AWS End User Messaging is the right call in these situations, each one drawn from a field we actually record:

• Teams already running on AWS who want one invoice and one IAM model.
• Workloads where AU data residency in ap-southeast-2 is the deciding factor.
• Establishing a cost floor before negotiating with a dedicated provider.
• Billing model is your binding constraint. AWS End User Messaging records postpaid-self-serve, the best figure in the AU SMS APIs roster. We define that field as how you pay to get started.
• SDK languages is your binding constraint. AWS End User Messaging records node, python, php, ruby, java, dotnet, go, the best figure in the AU SMS APIs roster. We define that field as first-party, vendor-maintained SDKs.

Reach for something else when any of the following is a requirement rather than a nice-to-have:

• Carrier route. AWS End User Messaging records international-aggregator, 10th of 13 in the AU SMS APIs roster. Telstra Messaging API records direct-carrier on the same field. If that is a hard requirement rather than a preference, start elsewhere.
• MMS to AU. AWS End User Messaging records No on the AU SMS APIs table. MessageMedia records Yes on the same field. If that is a hard requirement rather than a preference, start elsewhere.
• RCS. AWS End User Messaging records No on the AU SMS APIs table. Sinch records Yes on the same field. If that is a hard requirement rather than a preference, start elsewhere.
• Operating since. AWS End User Messaging records 2016, the weakest of the 11 tools in the AU SMS APIs roster. SMSGlobal records 1999 on the same field. If that is a hard requirement rather than a preference, start elsewhere.
• Price /SMS @ 100k. AWS End User Messaging records A$0.07 /SMS, 6th of 8 in the AU SMS APIs roster. SMS Broadcast records A$0.024 /SMS on the same field. If that is a hard requirement rather than a preference, start elsewhere.

We publish this block because a comparison that only lists what a tool is good at is marketing. Every figure above sits on the same page as its source, and the field definitions are on the category tables if you want to check how we measured them.

What we don't know. 3 of the 26 fields we track for AWS End User Messaging are still blank: Dedicated number, Min top-up and ACMA Sender ID. Those render as dashes rather than as zeroes or assumptions, because an empty cell and a bad cell are not the same thing and only one of them is honest. If you know any of these figures and can point at a document, tell us.