launch-with-aws
Migrates vibe-coded web applications to AWS. Handles the full workflow from analysis through migration to deployment, producing deployable AWS Blocks infrastructure code. Supports full-stack apps built with vibe-coding platforms (Lovable, Bolt.new, Replit) and frontend web applications and websites: React, Vue, Angular, Next.js, Nuxt, Astro, SvelteKit, Gatsby, Vite, Svelte, Solid, Docusaurus, and others (static sites, SPAs, and SSR frameworks with static export). Triggers on: launch with AWS, la
Security Assessment
About launch-with-aws
Launch with AWS is an AWS-authored skill that migrates vibe-coded and frontend web applications to AWS end-to-end, from analysis through migration to deployment, producing deployable AWS Blocks infrastructure code. It addresses the gap between prototype apps built on platforms like Lovable, Bolt.new, and Replit (or standard frontend frameworks such as React, Vue, Angular, Next.js, Nuxt, Astro, SvelteKit, and Vite) and a production AWS setup. It drives the migration through bundled CLI scripts and works standalone in any agent environment; the AWS MCP server is recommended but not required.
The skill runs via a Python entry script (launch_with_aws.py) that emits JSON on success and a JSON error on non-zero exit, requiring Python 3.10+ and boto3. Its documented flow starts with browser-based authentication: auth-start returns a sign-in URL that the user opens, auth-wait blocks until sign-in completes, and session-status and sign-out manage the cached session stored in ~/.launch-with-aws/session.json, with sessions capped at 90 days. It then creates a launch, generates a migration plan with a cost estimate, and delivers infrastructure code. The documentation is explicit about what moves versus what stays: for Supabase-backed apps, frontend, edge functions, and AI calls migrate to S3/CloudFront/Lambda and Bedrock while the database and auth remain on Supabase; for Replit apps, server logic, schema, auth code, realtime, and storage migrate to AWS-native services, but existing data, user accounts, and files must be migrated separately by the customer.
It is aimed at developers wanting to move a prototype or frontend app onto AWS with a guided, script-driven plan. The bundled script bodies were not included in the provided content, so the review is based on the documented behavior.
FAQ
Which apps and frameworks does it support?
Full-stack apps from Lovable, Bolt.new, and Replit, plus frontend frameworks including React, Vue, Angular, Next.js, Nuxt, Astro, SvelteKit, Gatsby, Vite, Svelte, Solid, and Docusaurus (static sites, SPAs, and SSR frameworks with static export).
How does authentication work?
It uses a browser sign-in flow: auth-start returns a sign-in URL, and auth-wait blocks until you complete sign-in. The session is cached locally at ~/.launch-with-aws/session.json, capped at 90 days, and sign-out best-effort revokes the token and deletes the local session.
Is my existing data migrated automatically?
Not always. For Supabase-backed apps the database, auth, storage, and realtime stay on Supabase. For Replit apps the code and schema migrate to AWS, but existing data, user accounts, and files must be exported and re-imported by the customer.
What are the prerequisites?
Python 3.10+ and boto3, which the script checks on startup. The AWS MCP server is recommended but optional; the skill works standalone via its CLI scripts.
Does it show cost before deploying?
Yes. The flow analyzes the app and generates a migration plan with a cost estimate, and for local directories it presents a confirmation step before proceeding.
Install launch-with-aws
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
aws/agent-toolkit-for-aws