AWS End User Messaging (SNS)

AWS End User Messaging is Amazon's rebranded, consolidated home for direct customer messaging, absorbing the SMS/voice capabilities that previously lived under Amazon Pinpoint and the Pinpoint SMS and Voice v2 API. In practice, the most common entry point developers know is Amazon SNS: when you call SNS's Publish to a phone number, the message is now actually delivered through the AWS End User Messaging SMS backend, inheriting its features (phone pools, configuration sets, two-way messaging, opt-out lists, country block rules, and origination-identity management). The service spans SMS, MMS, voice (text-to-speech), RCS, WhatsApp, and push, with a dedicated SMS and Voice v2 API for transactional, one-to-one sends and SNS/Pinpoint for fan-out and campaign-style delivery. It is squarely aimed at teams already inside AWS who want OTPs, alerts, shipping updates, and 2FA delivered without bolting on a third-party CPaaS.

Where it wins is integration and economics inside the AWS ecosystem: IAM-scoped permissions, native event routing of inbound messages and delivery receipts into SNS, EventBridge, Kinesis, and Lambda, and pay-as-you-go pricing with no platform fee and no markup on carrier pass-through fees. US SMS lands around $0.00645 per message part plus carrier fees, which is competitive with or cheaper than Twilio for high volume, and there is no monthly minimum. The newer "Notify" path even lets you send OTPs without registering your own phone number first, lowering the cold-start barrier that has historically plagued AWS messaging.

Where it loses is developer experience and onboarding friction. The product surface is genuinely confusing, SNS vs. Pinpoint vs. End User Messaging SMS vs. the v2 API, and AWS's own rebrandings and the Pinpoint deprecation roadmap have added churn. US 10DLC and toll-free registration is slow and opaque (campaign vetting can take weeks and is run by third-party downstream reviewers), and developers report TEXT_BLOCKED / carrier-filtering deliverability surprises even after correct registration. Documentation is thorough but sprawling, and there is no Twilio-style polished messaging console, friendly error messages, or batteries-included SDK helpers. It is the right call for AWS-native engineering teams optimizing cost and infra cohesion, and the wrong call for teams that want fast onboarding, hand-holding, and a messaging-first developer product.