Migration to AWS
Six-phase GCP or Heroku to AWS assessment that ends in Terraform, scripts and a costed plan.
Install
OfficialShips scriptsClaude Code: /plugin marketplace add anthropics/claude-plugins-official → /plugin install migration-to-aws@claude-plugins-official
GCP ya da Heroku'daki bir iş yükünün AWS'e taşınması planlanırken ve maliyeti çıkarılırken
- Author
- Amazon Web Services
- License
- Apache-2.0
The plugin reads whatever exists — Terraform files, application code, a billing export, or a consent-gated read-only Heroku session — then works through discovery, questions, architecture design, pricing and artifact generation. Two decisions come from measurement rather than a default: the database migration tool is picked from the actual size of the database, so a small one gets pg_dump and a zero-downtime case gets DMS, and cost is presented as three tiers compared against the current bill instead of one number. A security baseline is emitted on every run, and AI workloads are handled separately, mapping OpenAI or Gemini usage onto Bedrock options.

Comments(0)
Sign in to comment