Amazon Pinpoint
Amazon Pinpoint reaches end of support on 30 October 2026. After that date the console and the engagement resources — endpoints, segments, campaigns, journeys and analytics — are no longer accessible. The service stopped accepting new customers on 20 May 2025, so an account created since then cannot use it at all.
This page exists because Pinpoint appears throughout older documentation and architecture diagrams, and because the split in what happens to it is easy to get wrong: the engagement half is being withdrawn, while the messaging channel half continues under a different name.
What Pinpoint was
Section titled “What Pinpoint was”Pinpoint combined two distinct products under one console.
The engagement side modelled an audience and orchestrated communications to it: endpoints (one addressable destination for one person), segments (groups defined by attributes or behaviour), campaigns (a message to a segment, scheduled or triggered), journeys (multi-step, event-driven flows), message templates and the analytics over all of it.
The channel side was the delivery machinery: SMS, MMS, push notifications, WhatsApp, voice, one-time passcodes and phone number validation.
Where each part goes
Section titled “Where each part goes”Channels continue, renamed. The SMS, MMS, push, WhatsApp and text-to-voice capabilities were renamed AWS End User Messaging in 2024 and are unaffected by the end of support. The SMS, voice, mobile push, OTP and phone-number-validate APIs keep working; only the branding changed.
Email moves to SES. Anything sending email through Pinpoint should move to Amazon SES, and the deliverability dashboard has an equivalent in SES Virtual Deliverability Manager.
Engagement moves to Amazon Connect. AWS directs customers using segments, campaigns, journeys and analytics to Amazon Connect outbound campaigns and Customer Profiles, where an endpoint becomes a customer profile and a campaign or journey is recreated in Connect. Not everything transfers: in-app messaging has no equivalent, and push notifications are supported in journeys through a Lambda action rather than natively in campaigns.
Event collection moves to Kinesis. Applications that used Pinpoint only to stream analytics events should send those events to Kinesis instead.
If you are designing now
Section titled “If you are designing now”Do not build on Pinpoint. Choose the destination service directly: End User Messaging for SMS and push, SES for email, Amazon Connect for outbound campaign orchestration, and Kinesis for event collection. For an existing Pinpoint estate, the migration is a data export — segments, campaigns, journeys and templates can each be retrieved through the API — followed by recreating them in the destination service before the October 2026 date.