# From AWS to Cloud Run

> Moving from AWS Lambda, App Runner, ECS on Fargate or a small AWS web app to Cloud Run: what each service becomes, the commands and both bills.

<https://exodus.elim.io/blog/topic/from-aws>

These guides move an app from AWS to Cloud Run: Lambda functions, App Runner services, ECS tasks on Fargate and a small web app with its database and its files. Each one maps the AWS service to its Google Cloud counterpart, shows where the billing models differ, gives the commands for the move and prices the same app on both clouds.

- [Moving from AWS Lambda or App Runner to Cloud Run](https://exodus.elim.io/blog/aws-lambda-to-cloud-run.md): Lambda bills each request; Cloud Run bills an instance that takes many at once, and App Runner closed to new customers in April 2026. What each piece becomes, with commands and both bills.
- [Moving from ECS on Fargate to Cloud Run](https://exodus.elim.io/blog/ecs-fargate-to-cloud-run.md): Fargate bills tasks every second behind an hourly load balancer; Cloud Run runs the same image and scales to zero. What each part of a task definition becomes, the commands, and both bills.
- [Moving a small web app from AWS to Cloud Run](https://exodus.elim.io/blog/from-aws-to-cloud-run.md): App Runner takes no new customers, Lambda needs an adapter and Fargate bills all month. What each AWS piece becomes on Google Cloud, a small app's cost on each side, and the move in six steps.