Migrate from AWS to Google Cloud
with the official service map.
Google publishes both a service-by-service mapping from AWS and a series of migration guides. Here's the mapping in one table, the order to move things, and the AWS egress waiver that can cover the data transfer.
Facts checked against each provider's own pages
The short answer
Map each AWS service to its Google equivalent using Google's comparison table[1], move object storage with Storage Transfer Service (which accepts Amazon S3 as a source)[2], follow Google's per-service guides for EC2, EKS, RDS and Lambda[3], and ask AWS Support about free data transfer out for the migration[4]. Shift traffic gradually before decommissioning AWS.
What maps to what
| On AWS | On Google Cloud | Notes |
|---|---|---|
| Amazon EC2 | Compute Engine | [1] |
| AWS Lambda | Cloud Run functions | [1] |
| App Runner, Fargate, Lambda (apps) | Cloud Run | Google maps all three to Cloud Run[1]. Amazon ECS isn't named in Google's table. |
| Amazon EKS / Fargate with EKS | GKE / GKE Autopilot | [1] |
| AWS Elastic Beanstalk | App Engine | [1] |
| Amazon S3 | Cloud Storage | Storage Transfer Service supports S3 as a source[2]. |
| Amazon RDS / Aurora | Cloud SQL (Aurora also → AlloyDB) | [1] |
| Amazon DynamoDB | Firestore or Bigtable | [1] |
| Amazon ElastiCache | Memorystore | [1] |
| CloudFront / Route 53 | Cloud CDN / Cloud DNS | [1] |
| IAM / Secrets Manager | IAM / Secret Manager | [1] |
| ECR / ELB / CloudWatch | Artifact Registry / Cloud Load Balancing / Cloud Monitoring | [1] |
The migration, step by step
- 01
Map services and pick targets
Use Google's comparison table for each AWS service you run. For containers on ECS, which the table doesn't name, the closest listed targets are Cloud Run (for Fargate-style workloads) and GKE (for Kubernetes)[1].
- 02
Request the AWS egress waiver
Contact AWS Support to ask for free data transfer out under AWS's program for customers moving all their data off AWS, or off one AWS service. Approved customers receive credits; customers outside the EU have 180 days to complete the move[4].
- 03
Move object storage
Create Storage Transfer Service jobs from S3 buckets to Cloud Storage; the service is optimized for transfers over 1 TiB[2].
- 04
Move databases
Follow Google's guides for RDS and Aurora MySQL to Cloud SQL, RDS and Aurora PostgreSQL to Cloud SQL or AlloyDB, and RDS SQL Server to Cloud SQL[3].
- 05
Move compute
Google's series covers EC2 to Compute Engine, EKS to GKE and Lambda to Cloud Run[3]. Deploy the same release to both clouds so traffic can move gradually.
- 06
Cut over and close out
Shift traffic (below), move DNS from Route 53 to Cloud DNS or keep your current DNS provider, and decommission AWS resources once rollback is no longer needed.
Things the docs warn about
- AWS's waiver requires moving all data off AWS, or off a particular service, across eligible accounts, and is requested through AWS Support; it isn't automatic[4].
- Google prices network egress per GiB, not GB[5]; budget comparisons should convert units.
- Compute Engine bills a 1-minute minimum then per second[6]; EC2 bills per second with a 60-second minimum[7].
- Google has no built-in per-PR preview deployments; Cloud Run revision tags give a revision its own URL without serving traffic[8].
- If you later leave Google Cloud, its exit program requires an Exit Notice and terminating use of the service you leave[9].
Run both during cutover, then switch
AW3 Host connects both your AWS and Google Cloud accounts, so the old and new deployments run side by side from one dashboard and API instead of a big-bang switch.
Weighted routing sends a small share of traffic to Google Cloud first (for example 5%, then 25%, 50% and 100%) while AWS serves the rest. Health checks every 60 seconds watch both; if the Google Cloud side fails, failover moves traffic back automatically, and rollback to the previous release is one step. Daily cost sync shows what each provider costs during the overlap, and budget policies alert you if the double-running period gets expensive. Secrets for both are stored encrypted per environment. Geo routing also lets you move one region's users at a time.
When Google Cloud has carried all traffic cleanly for long enough that you no longer need the fallback, point DNS at it for good and decommission AWS.
AWS vs Google Cloud at a glance
| AWS | Google Cloud | |
|---|---|---|
| Category | Hyperscaler | Hyperscaler |
| Pricing model | Pay as you go per service; no long-term contract required[10] | Pay as you go per resource; no up-front fees or termination charges[16] |
| Compute billing granularity | EC2: per second with a 60-second minimum (Linux, Windows, RHEL, Ubuntu Pro); SLES by the full hour[7] | Compute Engine: 1-minute minimum, then per second; Cloud Run rounded up to 100 ms[6] |
| Internet egress (first paid tier) | $0.09/GB for the first 10 TB/month from US East (N. Virginia), then $0.085, $0.07, $0.05[11] | Premium Tier to North America: $0.12/GiB up to 1,024 GiB; Standard Tier $0.085/GiB after 200 GiB free[5] |
| Regions / locations | 39 regions, 124 Availability Zones[12] | 43 regions, 130 zones[17] |
| Deploy model | VMs (EC2), containers (ECS, EKS, Fargate), functions (Lambda), git-connected hosting (Amplify)[13] | VMs (Compute Engine), Kubernetes (GKE), containers, source or functions on Cloud Run[18] |
| Persistent volumes | Yes: Amazon EBS block volumes for EC2[14] | Yes: Persistent Disk and Hyperdisk for VMs; Cloud Run can mount Cloud Storage as a volume[19] |
| Config file | amplify.yml for Amplify Hosting; otherwise infrastructure as code (CloudFormation, CDK, SAM)[15] | Cloud Run service YAML (Knative Service spec); no mandated filename[20] |
Frequently asked questions
- What is the Google Cloud equivalent of AWS Lambda?
- Google's comparison table maps AWS Lambda to Cloud Run functions, and maps App Runner, Fargate and Lambda-based apps to Cloud Run.
- Does AWS charge egress when migrating to Google Cloud?
- AWS offers free data transfer out to the internet for eligible customers moving all their data off AWS or off a particular service. You request it through AWS Support and receive credits for the migrated data.
- How do I move S3 data to Google Cloud Storage?
- Use Storage Transfer Service, which supports Amazon S3 and S3-compatible sources and is optimized for transfers of more than 1 TiB.
Sources
- Google Cloud: Compare AWS and Azure services to Google Cloud. https://cloud.google.com/docs/get-started/aws-azure-gcp-service-comparison (checked 2026-11-16)
- Google Cloud Docs: Storage Transfer Service overview. https://cloud.google.com/storage-transfer/docs/overview (checked 2026-11-16)
- Google Cloud: Migrate from AWS to Google Cloud, get started. https://cloud.google.com/architecture/migration-from-aws-get-started (checked 2026-11-16)
- AWS News Blog: Free data transfer out to internet when moving out of AWS. https://aws.amazon.com/blogs/aws/free-data-transfer-out-to-internet-when-moving-out-of-aws/ (checked 2026-11-16)
- Google Cloud: Network pricing. https://cloud.google.com/vpc/network-pricing (checked 2026-11-16)
- Google Cloud: VM instance pricing. https://cloud.google.com/compute/vm-instance-pricing (checked 2026-11-16)
- AWS: EC2 On-Demand pricing. https://aws.amazon.com/ec2/pricing/on-demand/ (checked 2026-11-16)
- Google Cloud Docs: Rollouts, rollbacks and traffic migration. https://cloud.google.com/run/docs/rollouts-rollbacks-traffic-migration (checked 2026-11-16)
- Google Cloud: Exit free data transfer. https://cloud.google.com/exit-cloud (checked 2026-11-16)
- AWS: Pricing. https://aws.amazon.com/pricing/ (checked 2026-11-16)
- AWS Price List: AWSDataTransfer offer file, us-east-1. https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSDataTransfer/current/us-east-1/index.json (checked 2026-11-16)
- AWS: Global infrastructure. https://aws.amazon.com/about-aws/global-infrastructure/ (checked 2026-11-16)
- AWS Docs: What is Amazon ECS?. https://docs.aws.amazon.com/AmazonECS/latest/developerguide/Welcome.html (checked 2026-11-16)
- AWS: Amazon EBS. https://aws.amazon.com/ebs/ (checked 2026-11-16)
- AWS Docs: Amplify build settings. https://docs.aws.amazon.com/amplify/latest/userguide/build-settings.html (checked 2026-11-16)
- Google Cloud: Pricing. https://cloud.google.com/pricing (checked 2026-11-16)
- Google Cloud: Locations. https://cloud.google.com/about/locations (checked 2026-11-16)
- Google Cloud Docs: Deploy from source code (Cloud Run). https://cloud.google.com/run/docs/deploying-source-code (checked 2026-11-16)
- Google Cloud Docs: Disks. https://cloud.google.com/compute/docs/disks (checked 2026-11-16)
- Google Cloud Docs: Cloud Run YAML reference. https://cloud.google.com/run/docs/reference/yaml/v1 (checked 2026-11-16)
Your next deploy
goes everywhere.
Connect a provider, point a service at it, and ship. Add the second provider when you're ready.
No card needed · Free tier · Pay as you go after that