GCP to AWS Migration Assessment

Migration Decision Summary ↑ contents

Go, with conditions

Execution shape: Phased migration · Complexity: Moderate

Balanced estimateEst. $155/moPrimary AWS comparison scenario

Shape if you executePhasedLong pole: database migration (medium-complexity drivers)

Decision statusConditional goConfirm availability before cutover

💡 AWS Activate Founders: up to $5,000 in credits — Apply for AWS Activate credits before incurring eligible charges.

Confidence: Medium — full basis in What This Assessment Rests On.

Recommendation: Proceed with a phased migration on the Balanced cost scenario once the availability assumption is confirmed.

Migrate if

You want managed compute without Kubernetes operations
Consolidating AI usage onto Bedrock matters this year

Stay entirely if

Your GCP committed-use discounts run through 2027

Current Stack ↑ contents

Primary GCP services detected
Service	Type
Cloud Run	compute
Cloud SQL (PostgreSQL 15)	database
Cloud Storage	storage

Cost Comparison ↑ contents

Estimated monthly costs
Tier	Est. Monthly AWS
Premium	Est. $212/mo
Balanced (compare GCP to this row first)	Est. $155/mo
Optimized	Est. $118/mo

⚠ not comparable Your GCP baseline: estimated from resource configs (±20–30%, standing charges only). Your stated spend band ($1K–$5K/mo) measures your whole bill and is not directly comparable to the AWS figure above.

Cost Optimization ↑ contents

Savings Plans and Reserved Instances are incremental to the Balanced on-demand baseline (Est. $155/mo). Do not add those savings on top of Optimized (Est. $118/mo) — that tier already embeds reservation assumptions.

Post-migration commitment options vs Balanced on-demand.
Optimization	Target	Est. savings	Commitment	Effort
Compute Savings Plans	Fargate	20–40%	1-year no-upfront	Low
Database Savings Plans	RDS	~20%	1-year no-upfront	Low

Timeline ↑ contents

Phased in dependency order if you execute — long pole: database migration, then cutover in a maintenance window (medium-complexity drivers; the plugin quotes no week estimates — uncalibrated).

Top Risks ↑ contents

Highest-severity migration risks
Risk	Impact	Likelihood	Mitigation
Availability posture assumed single-AZ	High	Medium	Confirm the availability requirement before cutover sizing
BigQuery excluded from combined totals	High	Low	Deferred to specialist engagement; plan the analytics track in parallel

What This Assessment Rests On ↑ contents

Region, database size, and model detection extracted from your Terraform and code; availability defaulted to single-AZ per dev-tier signals. Cached pricing dated 2026-07 (±5–10% infra).

Ready to execute? ↑ contents

Say "generate the Terraform and migration scripts" and I'll produce the full execution pack (Terraform, migration scripts, rollback runbook, fill-in checklist) from this same analysis.

This decision report was generated without execution artifacts; the full migration report replaces it if you proceed.