Amazon Pinpoint reaches end of support; AWS points email senders to SES

AWS ended support for Amazon Pinpoint on October 30, 2026. The service had already stopped accepting new customers on May 20, 2025. According to the AWS migration guide, the Pinpoint console and its engagement resources, meaning endpoints, segments, campaigns, journeys and analytics, can no longer be accessed after that date.

What stopped working

The guide lists the capabilities that are not supported after October 30:

• SendUsersMessages, and sending to a stored endpoint ID on any channel, because both rely on the retired endpoint registry
• the analytics and KPI APIs, such as the date-range KPI operations
• in-app messaging and recommenders

AWS told customers to export any historical KPI data before the cutoff.

What keeps running

Pinpoint was never only a campaign tool, and parts of it stay up. Email, SMS and voice sending through SendMessages continues, but only for accounts that signed up before May 20, 2025. Email, SMS and voice templates can still be created, updated and deleted. Event delivery to Kinesis and Data Firehose and metric delivery to CloudWatch continue for messages sent through the direct-send APIs. Push, OTP and phone-number validation remain available to all accounts through AWS End User Messaging.

Where AWS sends email users

The guide gives three paths:

• Email sending: migrate to Amazon Simple Email Service (SES). AWS calls SES and End User Messaging "the long-term homes" for these channels.
• Deliverability dashboard: AWS says that feature now lives in SES Virtual Deliverability Manager.
• Segments, campaigns and journeys: recreate them in Amazon Connect outbound campaigns, with Customer Profiles in place of Pinpoint endpoints.

AWS suggests Connect for agent-assisted or AI-driven engagement, and End User Messaging with SES for high-volume transactional mail.

What senders should check

This section is our analysis. If you sent mail through Pinpoint journeys or campaigns, they have stopped. Rebuilding them on another ESP or on SES is also a sending infrastructure change. Before you move volume, confirm SPF, DKIM and DMARC alignment on the new path, carry your suppression list over so past hard bounces and complaints are not mailed again, and ramp volume on any new dedicated IP. Our email authentication checker confirms the DNS side in one pass.