Language:JapaneseEnglish

migration-to-aws Claude Code Plugin

Author
Amazon Web Services
Category
Development
Topics
Migration & Modernization · Cloud, Deployment & CI/CD · AI Agents & AI App Development
First cataloged
2026-07-09 (UTC)
Explanation last updated
2026-09-22 (UTC)
Source (GitHub) last updated
2026-10-01 (UTC) (14 days ago)

The explanation below is AI-generated. Please verify it against the sources.

This plugin is a collection of agent skills for Claude Code, Codex, and Cursor that plans a migration of workloads from Google Cloud Platform or Heroku to AWS. According to the README, it reads infrastructure-as-code files, application source code, and billing data to inventory existing resources, then maps them to AWS equivalents, estimates costs, and produces migration artifacts such as Terraform code and scripts. For AI and agentic workloads built on OpenAI or Gemini, it also proposes a migration path to Amazon Bedrock or other AWS agent runtimes. Processing takes place locally, and any live inspection of a GCP project or Heroku account is read-only and requires the user's consent.

About the service

The migration target is Amazon Web Services (AWS), a cloud platform offering compute, storage, database, and AI services among others. Per the README, the plugin reads source-side information from Google Cloud Platform and Heroku through their respective command-line tools, and it also calls AWS pricing and documentation lookups through MCP servers, plus an optional Temporal-related documentation MCP server that is operated by a third party (kapa.ai).

What you can do with migration-to-aws

  • Inventory resources from Terraform files, application code, billing exports, or a read-only live scan via the gcloud or heroku CLI
  • Map discovered resources to AWS equivalents (e.g., Cloud Run to Fargate, Heroku Postgres to RDS/Aurora)
  • Generate Terraform configuration including baseline security controls
  • Select a database migration tool (pg_dump, pgcopydb, or AWS DMS) based on database size
  • Estimate monthly AWS costs across multiple pricing tiers and compare them to current spend
  • Detect AI models, agentic frameworks, and tools in use, and recommend a migration approach to Amazon Bedrock or AWS agent runtimes
  • Produce migration scripts, provider adapters, and a browsable HTML migration report
  • Run a read-only Terraform security policy check
  • Get guidance on runtime selection for running AI agents on AWS

Sources

Back to list