Updated October 25, 2026
· ~1 min read
All three let you define infrastructure in TypeScript next to your application. They sit at different heights. Amplify Gen 2 gives you five opinionated categories (auth, data, storage, functions, AI) and generates the rest. SST gives you components for common building blocks, including frontends, and a fast development loop. CDK gives you every AWS resource and leaves the opinions to you.
Question 1 of 2
Do Amplify's auth and data categories fit your app?
**Amplify Gen 2:** a product team that wants auth and a typed data layer working today, and is happy with AppSync and DynamoDB or an existing SQL database. **SST:** teams that want framework-level conveniences (Next.js and other frontends deployed to their own account, live Lambda development) without Amplify's data model, and are comfortable with a non-CloudFormation engine. **AWS CDK:** platform teams, multi-service systems, anything with real networking, and organizations standardizing on CloudFormation. The most control and the most to decide.
Infrastructure as Code Migration (CDK)
Migrate your hand-crafted AWS infrastructure to reproducible, type-safe CDK, and never click through the console again.
Amplify Gen 1 to Gen 2 Migration and Pinpoint Exit
Amplify Gen 1 reaches end of life on May 1, 2027 and the Pinpoint-backed Analytics, Push Notifications and In-App Messaging lost their backend on October 30, 2026. We move each app to Gen 2, replace DataStore and Pinpoint features, and keep users, data and sign-ins intact.
AWS Architecture Review
A focused, senior-level review of your current AWS architecture, with a prioritized list of what to fix and why.
We work with startups and growing companies on AWS architecture decisions. Tell us about your situation and we will recommend the right approach.
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.