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.
The Amplify team announced that Gen 1 entered maintenance mode on May 1, 2026, with only critical bug fixes and security patches, and that it reaches end of life on May 1, 2027. The path is to migrate each backend environment to Gen 2, using the migration guide and the migration support added to the Gen 1 CLI.
CLI wizards and amplify push give way to TypeScript resource definitions and npx ampx pipeline-deploy.
Environments are Git branches, each deployed as its own backend, and every developer gets a cloud sandbox.
The backend is AWS CDK, so anything Gen 2 does not model directly is added as CDK in the same project.
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.
From the Amplify Gen 1 to Gen 2 feature matrix, October 2026.
Inventory each Gen 1 app: categories used, custom resources, overrides, and any DataStore, @searchable or many-to-many usage. Those three decide the effort.
Upgrade client libraries to the current major version first; it is required for Gen 2 and can ship on its own.
Migrate a non-production environment with the migration tooling and compare the generated resources.
Plan data carefully: Cognito user pools, DynamoDB tables and S3 buckets hold real data. Migrate in place where the tooling supports it rather than recreating resources.
Cut over production per app, then remove the Gen 1 environment.
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
AWS Amplify in 2026: Every Tool, What It Does, and What Is Being Retired
Amplify is not one product. It is Hosting, a TypeScript backend framework (Gen 2), client libraries, UI components and an AI kit, plus a Gen 1 CLI, Studio and DataStore that reach end of life on May 1, 2027, and Pinpoint-backed analytics and push that lost their backend on October 30, 2026. What each piece is, what it costs and whether to use it.
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.