migration-to-aws
PluginPlan a migration from Google Cloud Platform (and OpenAI/Gemini AI workloads) to AWS. Analyzes your Infrastructure-as-Code files, app code, and GCP billing data to discover resources, design an AWS architecture, estimate costs, and generate migration artifacts — including AI-provider mapping to Amazo
Install
claude plugin install migration-to-aws@claude-plugins-officialWhat is migration-to-aws?
Plan a migration from Google Cloud Platform (and OpenAI/Gemini AI workloads) to AWS. Analyzes your Infrastructure-as-Code files, app code, and GCP billing data to discover resources, design an AWS architecture, estimate costs, and generate migration artifacts — including AI-provider mapping to Amazon Bedrock. Processing is local; your data stays in your environment.
What's inside
11 bundled components — installing the plugin installs all of them.
Skills (5)
agent-advisor
Unified entry point for AI-agent work on AWS: evaluate and pick a runtime, generate a full migration plan (for existing workloads), and build an executable POC — all in one flow. Triggers on: which runtime for my agent, AgentCore vs ECS vs EKS vs Lambda, AgentCore vs Lambda MicroVMs, deploy an AI ag
gcp-to-aws
Migrate workloads from Google Cloud Platform to AWS — including AI and agentic workloads regardless of cloud provider. Triggers on: migrate from GCP, GCP to AWS, move off Google Cloud, migrate Terraform to AWS, migrate Cloud SQL to RDS, migrate GKE to EKS, migrate Cloud Run to Fargate, Google Cloud
heroku-to-aws
Migrate workloads from Heroku to AWS. Triggers on: migrate from Heroku, Heroku to AWS, move off Heroku, migrate Heroku app, migrate Heroku Postgres to RDS, migrate Heroku Redis to ElastiCache, migrate Heroku Kafka to MSK, migrate dynos to Elastic Beanstalk, migrate dynos to Fargate, Heroku migration
llm-to-bedrock
Use when the user wants to migrate code that calls OpenAI, Gemini/Google AI, or the Anthropic API to Amazon Bedrock — a pure model/SDK rewrite. End-to-end: assesses the codebase, then rewrites SDK calls, evaluates output quality against Bedrock, and delivers a ready-to-merge git branch. Not for: age
tf-best-practices
Best-practice authoring guidance AND a read-only policy gate for AWS Terraform generated by a migration skill. Load during any phase that writes a terraform/ directory — first as the "what to emit" posture rules + security-baseline spec, then after writing as the deterministic policy verdict. Read-o
Subagents (6)
generic-phase-worker-rw
writes filesGeneric, phase-AGNOSTIC worker that runs ONE migration phase's work (its fragments + assembler) in an isolated context and writes the phase's artifact(s) to disk. It is NOT tied to any phase — the phase to run is passed in the context block at dispatch time (the `Phase file` line). Capability tier:
llm2bedrock-code-analyzer
Analyze the local source repo, detect the AI framework and LLM SDK usage, map all call sites, identify prompts, and enumerate user-visible behavior-deltas for the Bedrock migration. Returns a structured analysis object.
llm2bedrock-code-rewriter
Rewrite LLM SDK calls to Amazon Bedrock on a dedicated git branch, swap dependencies, generate tests, and apply the user-confirmed behavior-delta decisions. Returns a structured rewrite object.
llm2bedrock-log-ingestor
Parse LLM API logs from the local repo, extract prompt/response pairs, and build a golden dataset (prompts.jsonl) for evaluation. Returns a structured ingestion object.
llm2bedrock-prompt-evaluator
Run each golden prompt against the target Bedrock model via the pinned uv harness, score with LLM-as-judge, and report a pass rate. Handles throttling with backoff; returns a structured eval object, or a partial/blocked control state.
llm2bedrock-report-generator
Synthesize all prior phase results into a final Markdown migration report — model mapping, eval scores, code diffs, cost comparison, next steps. Writes MIGRATION_REPORT_<date>.md and returns a structured report object.
What this can do
Capabilities declared by the plugin's own components — read straight from their frontmatter, not inferred.
Create and modify files
1 component declare Write or Edit
Inherit all session tools
10 components declare no tool restrictions
~1,691 tokens of context used while enabled, before you invoke anything
All declared tools (5)
EditGlobGrepReadWriteTrust
83/100 · Excellent2 factors scored below maximum
Documentation
README · ~2 min readAWS Startups
AI agent plugins, tools, and resources for startup builders on AWS.
Plugins
| Plugin | Description | Status |
|---|---|---|
| migration-to-aws | Assess, plan & execute: migrate GCP/Heroku infrastructure and AI workloads to AWS (discovery, architecture mapping, cost analysis, Terraform), rewrite LLM SDK calls to Amazon Bedrock, and select an AWS runtime + build a POC for AI agents. Bundles the gcp-to-aws, heroku-to-aws, llm-to-bedrock, and agent-advisor skills | Available |
| aws-dev-toolkit | AWS development toolkit — 35 skills, 11 agents, and 3 MCP servers for building, migrating, and architecture reviews on AWS | Available |
Installation
Claude Code
Reviews
Log in to leave a review.
No reviews yet — be the first.
Explore related
Other things in this space — across every part of the ecosystem, not just plugins.
Pluginssimilar to this one
All plugins →mcp-tunnels
Connect Claude to a private MCP server through an Anthropic MCP tunnel. The /create-docker-mcp-tunnel command drives the Docker Compose quickstart end to end: certificates, proxy config, cloudflared, and a verifiable sample server.
32.9K stars
mcp-server-dev
Skills for designing and building MCP servers that work seamlessly with Claude. Guides you through deployment models (remote HTTP, MCPB, local), tool design patterns, auth, and interactive MCP apps.
32.9K stars
feature-dev
Comprehensive feature development workflow with specialized agents for codebase exploration, architecture design, and quality review
32.9K stars
MCP Servers
All mcp servers →Commands
All commands →feature-dev
Guided feature development with codebase understanding and architecture focus
32.8K stars
modernize-transform
Transform one legacy module to the target stack — idiomatic rewrite with behavior-equivalence tests
32.8K stars
modernize-extract-rules
Mine business logic from legacy code into testable, human-readable rule specifications
32.8K stars
Subagents
All subagents →architecture-critic
Reviews proposed target architectures and transformed code against modern best practice. Adversarial — looks for over-engineering, missed requirements, and simpler alternatives.
32.8K stars
code-architect
Designs feature architectures by analyzing existing codebase patterns and conventions, then providing comprehensive implementation blueprints with specific files to create/modify, component designs, data flows, and build sequences
32.8K stars
legacy-analyst
Deep-reads legacy codebases (COBOL, Java, .NET, Node, anything) to build structural and behavioral understanding. Use for discovery, dependency mapping, dead-code detection, and "what does this system actually do" questions.
32.8K stars
Skills
All skills →plugin-structure
This skill should be used when the user asks to "create a plugin", "scaffold a plugin", "understand plugin structure", "organize plugin components", "set up plugin.json", "use ${CLAUDE_PLUGIN_ROOT}", "add commands/agents/skills/hooks", "configure auto-discovery", or needs guidance on plugin director
32.8K stars
build-mcp-server
This skill should be used when the user asks to "build an MCP server", "create an MCP", "make an MCP integration", "wrap an API for Claude", "expose tools to Claude", "make an MCP app", or discusses building something with the Model Context Protocol. It is the entry point for MCP server development
32.8K stars
build-mcp-app
This skill should be used when the user wants to build an "MCP app", add "interactive UI" or "widgets" to an MCP server, "render components in chat", build "MCP UI resources", make a tool that shows a "form", "picker", "dashboard" or "confirmation dialog" inline in the conversation, or mentions "app
32.8K stars