All posts
AWS News

Amazon Pinpoint Stopped Working After October 30, 2026: What Broke and What to Do Today

By

November 7, 2026

6 min read

Pinpoint's engagement features (campaigns, journeys, segments and the analytics behind them) reached end of support on October 30, 2026. If messages stopped going out, a dashboard went flat or your app's analytics calls started failing, this is the triage: how to find every place you used Pinpoint, what still works under AWS End User Messaging, and what to put in place today, this week and this month.

Pinpoint Alternatives
Amazon Pinpoint
AWS End User Messaging
Amazon SES
Deadlines

AWS ended support for Amazon Pinpoint's engagement features on October 30, 2026. Teams that missed the notices tend to find out from a symptom rather than an email: a campaign that didn't send, a journey that stopped, an analytics chart that went flat, or errors from code that has run untouched for years.

What stopped, and what didn't

Pinpoint feature

After October 30, 2026

Replacement

Campaigns and journeys

Ended

Amazon Connect outbound campaigns, a marketing platform, or your own scheduler

Segments and endpoint analytics

Ended

Amazon Connect Customer Profiles, or your own tables

Event analytics (including Amplify Analytics record calls)

Ended

Your own event pipeline (Firehose to S3 and Athena), or a product analytics tool

SMS and voice sending

Continues as AWS End User Messaging

Keep it; update code and IAM to the End User Messaging APIs where AWS says so

Mobile push sending

Continues as AWS End User Messaging

Keep it; check your SDK version

Email

Use SES directly

Amazon SES, which Pinpoint email used underneath

From AWS's Pinpoint end-of-support announcement. Check AWS's current guidance for the exact API changes that apply to your code.

Find every place you used it (one hour)

  1. CloudTrail: filter event source pinpoint.amazonaws.com for the last 90 days. Every caller, every API, every role.

  2. Your code: search for "pinpoint", "@aws-amplify/analytics", "Analytics.record" and "PinpointClient".

  3. Your infrastructure code: search for Pinpoint apps, Amplify analytics categories and IAM policies that allow mobiletargeting actions.

  4. Your bill: Cost Explorer for Pinpoint and End User Messaging, to see what was actually being used.

  5. Your scheduled jobs: anything that created campaigns or exported segments on a timer.

Today, this week, this month

When

Do this

Today

Stop analytics calls from failing loudly in your app: make them no-ops or catch their errors, so a dead endpoint doesn't break sign-in or checkout. Move any transactional email straight to SES.

This week

Send events to a pipeline you own (a single endpoint into Firehose and S3 takes a day) so you stop losing data. Re-create the one or two campaigns that matter as scheduled sends.

This month

Choose the long-term home for segmentation and journeys: Amazon Connect, a marketing platform, or your own on AWS. Add holdout groups so you can finally tell whether the messages work.

Moving off Pinpoint?

We'll review your CloudTrail with you, restore the messages that matter first, and plan the rest. 30 minutes, free.

hoolco Monthly Review

Once a month: what changed in tech that month and what it means for you, from cloud and AI to security and the tools you build with. Every item links to its source. No sales pitch, unsubscribe in one click.

As of November 7, 2026. Provided as is, for general information, and accurate to the best of our knowledge on the date shown. Not legal, compliance, tax, financial or other professional advice. Prices, limits and vendor services change; check current vendor documentation before relying on anything here. Terms of use.