Behind a few TypeScript files, an Amplify Gen 2 backend is Cognito, AppSync, a DynamoDB table per model, Lambda functions, S3 and nested CloudFormation stacks. Two diagrams: what Amplify creates, and the same app built directly, with a table of each piece, what replaces it, and how hard the move is.
Amplify's pitch is that you never have to see the AWS underneath. That is also the problem when something breaks, a bill surprises you, or a requirement falls outside what Amplify generates. Underneath are Cognito, AppSync, DynamoDB, Lambda, S3 and CloudFormation.
Frontend
Auth
Every data and storage rule resolves to these.
API
Data
Other
Each sandbox and branch deploys its own copy.
A typical Amplify Gen 2 app: auth, data, storage and a function
Frontend
Auth
API
Data
Infrastructure
The same app built directly, the shape we usually move teams to
Send us your amplify/ folder (or describe it) and we'll tell you which pieces to keep, which to move, and in what order.
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
Amplify's Share of Backend SDK Downloads Fell From 21% to 3.5% in Two Years
Among the three backend-as-a-service SDKs (aws-amplify, firebase and supabase-js), Amplify went from 21.4% of monthly npm downloads in November 2024 to 3.5% in October 2026, while Supabase went from 15% to 75%. Inside Amplify, the Gen 1 CLI is still downloaded more than twice as often as the Gen 2 backend package. The data, and what it does and doesn't tell you.
Read
One Screen, 241 DynamoDB Requests: How Nested GraphQL Queries Fan Out on AppSync
A feed of 20 posts, each with its author and 10 comments with their authors, is one GraphQL query and 241 DynamoDB requests when each relationship resolver fetches per parent. The arithmetic by page size and nesting depth, what it costs per million screen views, and four ways to cut it, from batching to a single Postgres join.
Read
As of November 4, 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.