What is AWS End User Messaging?
AWS End User Messaging connects your applications directly to your end users across SMS, MMS, RCS, WhatsApp, push notifications, and voice. The service is designed for application-to-person (A2P) messaging: one-time passwords, status updates, appointment reminders, or marketing messages.
According to the documentation, the SMS, MMS, and voice (text to speech) features of Amazon Pinpoint are now called AWS End User Messaging. The dedicated interface is the AWS End User Messaging SMS and Voice v2 API, which still uses the pinpoint-sms-voice-v2 API namespace.
Core Features
- Multiple channels: SMS, MMS, RCS, WhatsApp, push notifications, and voice on one platform
- Originator identities: Request phone numbers and sender IDs, group them into phone pools, and manage registrations and their status
- RCS with SMS fallback: Verified, branded messages with delivery receipts that fall back to SMS automatically when RCS is unavailable
- Notify: Managed OTP and verification messaging using AWS-managed origination identities
- SMS Protect: Detection of anomalous traffic to help prevent fraud and unexpected cost
- Protect configurations: Country rules that allow or block messages per destination country
- Configuration sets and event destinations: Rules applied when sending, plus capture of delivery and failure events
- Two-way messaging: Inbound messages via Amazon SNS, Amazon EventBridge, or Amazon Kinesis, and per the product page in combination with AWS Lambda and Amazon Bedrock
- SMS simulator: Test your messaging environment without sending real traffic
Typical Use Cases
Authentication: Deliver one-time passwords for login and verification — with Notify even without your own phone numbers.
Transactional notifications: Deliver order, delivery, and appointment status to customers promptly.
Marketing messages: Run campaigns with text and media content over SMS, MMS, RCS, or WhatsApp.
Multi-tenant platforms: Per the documentation, the v2 API suits multi-tenant architectures such as independent software vendors, because event data, origination phone numbers, and opt-out lists can be separated per tenant.
Benefits
- One service for several messaging channels instead of separate providers per channel
- Phone numbers, sender IDs, and country-specific registrations managed in the same service
- Automatic SMS fallback for RCS
- Protection features against anomalous traffic and unwanted destination countries
- Event data can be integrated into existing analytics through configuration sets
- Available in several EU regions
Integration with innFactory
As an AWS Reseller, innFactory supports you with AWS End User Messaging: selecting suitable channels, requesting and registering phone numbers and sender IDs, migrating existing Amazon Pinpoint sending paths, setting up configuration sets and event destinations for measurable delivery events, and hardening traffic with protect configurations.
Typical Use Cases
Technical Specifications
Frequently Asked Questions
What is AWS End User Messaging?
AWS End User Messaging is an application-to-person (A2P) messaging service. Through a single API you send SMS, MMS, RCS, and WhatsApp messages as well as push notifications and voice messages from web, mobile, or business applications.
How does AWS End User Messaging relate to Amazon Pinpoint?
According to the documentation, the SMS, MMS, and voice (text to speech) features of Amazon Pinpoint are now called AWS End User Messaging. The corresponding interface is the AWS End User Messaging SMS and Voice v2 API, which still uses the pinpoint-sms-voice-v2 API namespace. If you already use Amazon Pinpoint to send SMS, MMS, or voice messages, the documentation notes your account is already configured to use this API.
How does the v2 API differ from the Amazon Pinpoint API?
The Amazon Pinpoint API focuses on projects, segments, campaigns, journeys, and analytics. The AWS End User Messaging SMS and Voice v2 API focuses on sending directly to individual recipients and provides phone pools, phone numbers, sender IDs, configuration sets, opt-out lists, registrations, MMS, protect configurations, RCS, and notify configurations. Per the documentation, the v2 API is available in 32 AWS Regions and the Amazon Pinpoint API in 13.
What do RCS and Notify provide?
RCS (Rich Communication Services) sends verified, branded text messages with delivery receipts and automatic SMS fallback using phone pools; you create an AWS RCS Agent to represent your brand. Notify is a managed solution for templated OTP and verification messages using AWS-managed origination identities, with no need to provision your own phone numbers.
How are inbound messages handled?
Per the product page, inbound messages are routed through Amazon SNS, Amazon EventBridge, or Amazon Kinesis. For outbound traffic the documentation recommends setting up configuration sets with event destinations, because the v2 API does not automatically emit event data.
What does AWS End User Messaging cost?
Billing is usage-based and channel-specific. The channel used and the destination country determine the rate; refer to the provider's official pricing information for binding rates.
Note: All product information on this page has been compiled with care, but is provided without guarantee and may be outdated or incomplete. Cloud services evolve rapidly — features, pricing, SLAs, and availability change frequently. Authoritative and up-to-date information can only be found on the official product page of AWS (official documentation). This page does not represent an offer by AWS.