Migration to AWS

Reads your existing GCP account and Terraform state, parses resource definitions, and pulls actual billing data. It maps GCP services (for example Compute Engine, GKE, Cloud SQL, Cloud Storage, IAM) to equivalent AWS resources (EC2/EKS, RDS, S3, IAM) and flags constructs that don’t have 1:1 matches. The tool checks Terraform modules, identifies hard-coded GCP providers, and generates a migration inventory with resource counts, inter-dependencies, and estimated data transfer paths.

Fetches current AWS on-demand and reserved pricing and applies region-specific rates to give a line-item cost comparison. It generates Terraform sketches or CloudFormation snippets for the mapped AWS resources, and annotates them with the changes you’ll need (machine types, networking, IAM roles). The planner validates basic constraints like subnet sizes, VPC peering, and service limits and reports likely blockers.

Produces a five-phase migration plan: discovery, design, proof-of-concept, data sync and cutover, and validation & rollback. Each phase includes concrete commands, Terraform workspaces to run, a recommended cutover window, and smoke-test steps. It also evaluates whether a lift-and-shift, re-platform, or stay-put option is cheaper and safer, and it records the confidence level of each recommendation.

Imagine migrating a multi-region web app with GKE, Cloud SQL, and BigQuery: the plugin reads your Terraform state, maps clusters to EKS, converts SQL to RDS, pulls AWS pricing, and spits out a step-by-step cutover plan. That saves hours of manual mapping, spreadsheet pricing, and console hopping, and avoids bouncing between cloud consoles and separate cost tools during planning.