Migration Guide
Migrate from ECS to Cloud Run
Migrate AWS ECS/Fargate services to Google Cloud Run. Translate task definitions to Cloud Run services, remap IAM and networking.
What you get
Risk assessment
Blockers, warnings, and unknowns ranked by severity
Effort estimate
Hours, t-shirt size, and role breakdown
Cost estimate
Labor, infrastructure, and tooling cost range
Migration steps
Ordered execution plan with durations
Open questions
What still needs to be answered before you start
Draft config or code
Starter configs when the migration path supports it
Why teams migrate from ECS to Cloud Run
Good fit when
- +Teams migrating containerized workloads to GCP alongside other service migrations.
- +Services that can run as request-driven containers without persistent connections.
- +Teams wanting simpler container deployment without managing cluster infrastructure.
Strengths
- Cloud Run eliminates cluster management entirely for stateless containers.
- Scale-to-zero capability reduces costs for bursty or low-traffic services.
- Native integration with Cloud Build, Artifact Registry, and GCP networking.
Tradeoffs
- ECS task definitions with sidecar patterns need adaptation for Cloud Run's multi-container support.
- ECS service discovery and App Mesh have different Cloud Run networking equivalents.
- Persistent storage patterns (EFS mounts) differ from Cloud Run's approach.
Migration notes
- Translate ECS task definitions to Cloud Run service configurations.
- Remap ECS IAM task roles to GCP service accounts.
- Replace ALB/NLB targets with Cloud Run's built-in load balancing.
- Migrate container images to Artifact Registry and update CI/CD pipelines.
How it works
Describe your migration
Select ECS as source and Cloud Run as target. Add context about your setup — configs, docs, architecture notes.
Keshro runs the analysis
Keshro researches the path, finds similar past migrations, and generates a structured assessment with risks, effort, cost, and steps.
Get your plan
Review the migration plan, refine it with your team, and use it as a living document during execution.
Related migrations
Ready to plan your ECS to Cloud Run migration?
Get a risk assessment, effort estimate, and step-by-step plan in minutes.
Start Migration Analysis