Amplify's Analytics, Push Notifications and In-App Messaging categories were built on Amazon Pinpoint, which ended on October 30, 2026. Pinpoint endpoints, segments, campaigns, journeys and analytics are gone, and in-app messaging has no AWS replacement. What still works, what to move to (Kinesis, End User Messaging, Connect) and what to build.
Since October 30, 2026 the Pinpoint console and its resources (endpoints, segments, campaigns, journeys and analytics) are no longer accessible. Amplify apps that call Analytics.record, register devices for push through Pinpoint, or show Pinpoint in-app messages have stopped doing those things, often without an error the user sees.
Book a free 30-minute call. You'll leave knowing what we'd do first and roughly what it costs, whether or not you hire us.
Search client code for Analytics, Notifications and InAppMessaging imports from Amplify, and backend code for Pinpoint API calls.
Whatever was exported from Pinpoint before October 30 (endpoint lists, segments, campaign definitions, analytics) is the record now; keep it in S3. If nothing was exported, rebuild audiences from your own user table rather than hoping to recover them.
Move event recording to Kinesis or your own collector so you keep a continuous history.
Keep push working: tokens in your own store, sends through End User Messaging.
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.
Book a free 30-minute call about it. Bring your setup and your bill; you'll leave knowing what we'd do first and roughly what it costs, whether or not you hire us.
Or keep reading
Leaving AWS Amplify and AppSync: When It Is Time, and How to Do It Without a Rewrite
Amplify gets a startup to launch fast. The trouble starts later: list queries that scan, resolvers that can't throw or call out, a 30-second ceiling, and a data model that was never designed. The signs it is time to leave, what to move to, what to keep, and a cutover that doesn't log anyone out.
Read
Amplify Gen 1 Reaches End of Life on May 1, 2027: Migrating to Gen 2, Gap by Gap
Gen 1 backends have received only critical fixes since May 1, 2026, and reach end of life on May 1, 2027. Gen 2 covers most of Gen 1 and adds OIDC and SAML, SQL databases and TypeScript functions, but it drops DataStore, many-to-many relationships, @searchable, Studio's visual configuration and Pinpoint analytics. The parity table and a migration order.
Read
As of October 25, 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.