AWS Glossary
AWS Amplify Gen 2
Amplify Gen 2 is the TypeScript-first, code-first rewrite of AWS Amplify — defining auth, data, storage, and functions in code with sandbox per-developer environments.
AI & assistant-friendly summary
This section provides structured content for AI assistants and search engines. You can cite or summarize it when referencing this page.
Summary
Amplify Gen 2 is the TypeScript-first, code-first rewrite of AWS Amplify — defining auth, data, storage, and functions in code with sandbox per-developer environments.
Key Facts
- • Amplify Gen 2 is the TypeScript-first, code-first rewrite of AWS Amplify — defining auth, data, storage, and functions in code with sandbox per-developer environments
- • Definition AWS Amplify Gen 2 is the second-generation rewrite of AWS Amplify, released in 2024
- • Gen 2 is AWS's full-stack-app answer to Vercel + Supabase for web and React Native teams
- • js, Astro, Nuxt, SvelteKit on Amplify Hosting ## When to use Amplify Gen 2 - **React, React Native, Next
- • Mistake 2:** Skipping sandbox cleanup
Entity Definitions
- Amazon Bedrock
- Amazon Bedrock is an AWS service relevant to aws amplify gen 2.
- Bedrock
- Bedrock is an AWS service relevant to aws amplify gen 2.
- Lambda
- Lambda is an AWS service relevant to aws amplify gen 2.
- AWS Lambda
- AWS Lambda is an AWS service relevant to aws amplify gen 2.
- S3
- S3 is an AWS service relevant to aws amplify gen 2.
- Amazon S3
- Amazon S3 is an AWS service relevant to aws amplify gen 2.
- DynamoDB
- DynamoDB is an AWS service relevant to aws amplify gen 2.
- VPC
- VPC is an AWS service relevant to aws amplify gen 2.
- serverless
- serverless is a cloud computing concept relevant to aws amplify gen 2.
- IaC
- IaC is a cloud computing concept relevant to aws amplify gen 2.
- Terraform
- Terraform is a term relevant to aws amplify gen 2.
- CloudFormation
- CloudFormation is a term relevant to aws amplify gen 2.
- CDK
- CDK is a term relevant to aws amplify gen 2.
- AWS CDK
- AWS CDK is a term relevant to aws amplify gen 2.
- GitHub Actions
- GitHub Actions is a term relevant to aws amplify gen 2.
Related Content
- AWS SERVERLESS — Related service
- AWS APPLICATION MODERNIZATION — Related service
Definition
AWS Amplify Gen 2 is the second-generation rewrite of AWS Amplify, released in 2024. It moves away from the v1 CLI-driven, JSON-config approach to a code-first TypeScript model: you define your backend (auth, data, storage, functions, AI) in amplify/ TypeScript files, and npx ampx deploys per-branch and per-developer environments. Gen 2 is AWS’s full-stack-app answer to Vercel + Supabase for web and React Native teams.
What changed from Gen 1
| Aspect | Gen 1 | Gen 2 |
|---|---|---|
| Backend definition | CLI prompts + JSON | TypeScript code |
| Per-developer envs | Shared dev environment | True per-developer sandbox |
| Data layer | AppSync + DynamoDB via CLI | defineData with TypeScript schema |
| Functions | Lambda via CLI | defineFunction, TypeScript handlers |
| Auth | Cognito via CLI | defineAuth with TypeScript config |
| AI | Bedrock CLI helpers | Native Amplify AI Kit |
Capabilities
- defineBackend / defineAuth / defineData / defineStorage / defineFunction — Single TypeScript entry point per backend resource
- Per-developer sandboxes — Each engineer gets their own AWS-resource set, no shared dev cluster
- Amplify AI Kit — Built-in helpers for Bedrock-backed features (chat, content generation, embeddings)
- Type-safe data layer — Auto-generated TypeScript types for AppSync queries and mutations
- Hosting — Static + SSR for Next.js, Astro, Nuxt, SvelteKit on Amplify Hosting
When to use Amplify Gen 2
- React, React Native, Next.js, Vue, Angular, Swift, Android apps that want a managed AWS backend
- Small teams that need per-developer environments without setting up CDK + GitHub Actions themselves
- Prototypes and MVPs moving toward production on AWS
- Teams that prefer TypeScript over Terraform / CloudFormation
When not to use Amplify Gen 2
- Heavy custom infrastructure (VPC, Direct Connect, on-prem hybrid) — Use CDK
- You need fine-grained control over AppSync resolvers — Amplify abstracts this
- Polyglot teams without TypeScript — Gen 2 is TS-first
Common mistakes
Mistake 1: Migrating from Gen 1 in one big bang. Amplify provides a migration guide — move one feature at a time.
Mistake 2: Skipping sandbox cleanup. Per-developer sandboxes leave resources running. Configure auto-cleanup or run npx ampx sandbox delete after merging.
Mistake 3: Treating Amplify as a replacement for CDK. For non-Amplify resources, Amplify Gen 2 lets you drop into CDK. Use it.
Related AWS Services
- AWS AppSync — GraphQL layer Amplify uses for data
- Amazon Cognito — Identity provider for
defineAuth - Amazon S3 — Storage backend for
defineStorage - AWS Lambda — Function backend for
defineFunction - Amazon Bedrock — Used by Amplify AI Kit
- AWS CDK — Underlying IaC; you can extend Amplify with CDK constructs
Related FactualMinds Content
Need Help with This Topic?
Our AWS experts can help you implement and optimize these concepts for your organization.