launch-with-aws
An agent skill by aws, from aws/agent-toolkit-for-aws. Tags: aws, deployment, migration, react, web.
What it does
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, launch on AWS, deploy to AWS, migrate to AWS, host my app on AWS, move my app to AWS, transfer my app to AWS. Activates when the user wants to migrate a vibe-coded app or frontend web app to AWS, even if they don't say 'migrate' explicitly.
Install
With the skills CLI, which installs into Claude Code, Codex, Cursor and other agents:
npx skills add aws/agent-toolkit-for-aws --skill launch-with-aws
Or copy the skill folder into Claude Code's skills directory by hand (~/.claude/skills for every project, or .claude/skills inside one):
git clone --depth 1 https://github.com/aws/agent-toolkit-for-aws
cp -r agent-toolkit-for-aws/plugins/aws-core/skills/launch-with-aws ~/.claude/skills/launch-with-aws
Safety box score
Grade D, elevated risk: 51 of 100 risk points, rated 2026-10-20. The grade rates what the skill and its scripts can reach on the machine of whoever installs it, across eight categories from shell execution to secrets access. How the score works.
This skill is an end-to-end AWS migration workflow: it uploads a local app, analyzes it remotely, generates deployment code, and can start execution in an AWS-managed environment. The main risks are broad source-code egress to AWS, local token storage under the home directory, and automated file overwrites when applying the migrated output.
| Category | Level | Why |
|---|---|---|
| Code & shell execution | 2 (moderate) | It runs local Python scripts, spawns subprocesses (`git` and an OAuth callback server), and the docs also instruct shell-based deployment commands like `npm install && npx cdk bootstrap`. |
| Network access | 3 (high) | The core workflow uploads the user’s source code to the Launch with AWS service and can also download GitHub zipballs and a migrated snapshot from remote URLs. |
| Filesystem reach | 2 (moderate) | It reads the project tree recursively, writes `~/.launch-with-aws/session.json`, can delete that file on sign-out, and the post-migration steps overlay files into the working tree with `rsync -a /tmp/migration-output/ .`. |
| Secrets & credentials | 2 (moderate) | It caches access/refresh tokens in `~/.launch-with-aws/session.json` and reads AWS profile data from `~/.aws/config`, so it touches authentication material even though it does not read raw keychains or password stores. |
| Privilege & persistence | 0 (none) | There is no sudo, service registration, shell/profile editing, or other local privilege change; the skill stays within the user context. |
| Instruction hijack surface | 1 (low) | The service model says optional context inputs can be answered without prompting the user, which nudges the agent to auto-fill some prompts, though the main confirmation gates are still explicit. |
| Irreversible actions | 3 (high) | The skill is designed to drive migration and execution end-to-end, including creating a launch, starting deployment, and deleting launches; those are inherently high-autonomy actions even though some are gated by confirmation. |
| Transparency | 0 (none) | The shipped files are plain text Python/JSON/Markdown; there are no binaries, obfuscated blobs, or hidden runtime downloads in the skill itself. |
Before installing
- Read `SKILL.md`’s upload and execution gates; confirm you are comfortable sending the source tree to AWS.
- Inspect `scripts/auth.py` and `launch_config.py` for the `~/.launch-with-aws/session.json` token cache and `~/.aws/config` access.
- Review `scripts/archive.py` to see exactly which files are zipped, skipped, and downloaded from GitHub.
- If you plan to apply the migrated snapshot locally, test the `rsync -a /tmp/migration-output/ .` step in a scratch clone first.
Rated 2026-10-20 by an automated review of 8 files from the skill's repository.
Source
- Repository
- aws/agent-toolkit-for-aws (all skills from this repository)
- Path
- plugins/aws-core/skills/launch-with-aws/SKILL.md
- Branch
- main
- Collection
- aws-core
- Updated
- 2026-09-19
Related skills
- aws-amplify — Build and deploy full-stack web and mobile apps with AWS Amplify Gen2 (TypeScript code-first).
- expo-dom — Framework (OSS). Use Expo DOM components to run web code in a webview on native and as-is on web. Migrate web code to native incrementally.
- expo-web-to-native — Framework (OSS). Migrate an existing web React app to a native iOS/Android app with Expo.
- aws-serverless — Builds, deploys, manages, debugs, configures, and optimizes serverless applications on AWS using Lambda, API Gateway, Step Functions, EventBridge, and SAM/CDK.
- app-platform-migration — Migrate applications from Heroku, AWS, Render, Railway, Fly.io, or Docker Compose to DigitalOcean App Platform. Use when converting existing apps.
- eas-hosting — EAS service (paid). Deploy Expo websites and Expo Router API routes to EAS Hosting - export the web bundle, run eas deploy for production and PR preview URLs.