Serverless functions · AWS vs Google Cloud
Lambda function URLs vs Cloud Run functions (formerly Cloud Functions)
Lambda function URLs map to the built-in HTTPS URL of a Cloud Run function.
Side-by-side comparison
| Aspect | Amazon Web Services | Google Cloud |
|---|---|---|
| Service | Lambda function URLs | Cloud Run functions (formerly Cloud Functions) |
| Lifecycle | Generally available | Generally available |
| What it is | A dedicated HTTPS endpoint for a function, with IAM (AWS_IAM) or public (NONE) auth, CORS, and response streaming. | Event-driven and HTTP functions deployed from source on Cloud Run, using the Functions Framework and Eventarc triggers. |
| Pricing model | No extra charge beyond Lambda requests and duration. | Request-based billing (default) charges vCPU-seconds and GiB-seconds while instances handle requests, plus a per-request fee; instance-based billing charges for the whole instance lifetime. A monthly free tier applies. |
| Docs | Lambda function URLs docs | Cloud Run functions (formerly Cloud Functions) docs |
| Pricing page | Lambda function URLs pricing | Cloud Run functions (formerly Cloud Functions) pricing |
Key differences
- Every Cloud Run service and function gets an HTTPS endpoint by default; access is controlled with IAM (Cloud Run Invoker) or public access.
Pricing summary
Pricing models only. No prices are quoted because they change by region and over time.
- AWS
- No extra charge beyond Lambda requests and duration. Lambda function URLs pricing →
- GCP
- Request-based billing (default) charges vCPU-seconds and GiB-seconds while instances handle requests, plus a per-request fee; instance-based billing charges for the whole instance lifetime. A monthly free tier applies. Cloud Run functions (formerly Cloud Functions) pricing →
And on Azure?
Direct match Azure's equivalent is Azure Functions. AWS vs Azure comparison →
FAQ
What is the Google Cloud equivalent of Lambda function URLs?
Lambda function URLs map to the built-in HTTPS URL of a Cloud Run function.
How does pricing compare between Lambda function URLs and Cloud Run functions (formerly Cloud Functions)?
AWS: No extra charge beyond Lambda requests and duration. Google Cloud: Request-based billing (default) charges vCPU-seconds and GiB-seconds while instances handle requests, plus a per-request fee; instance-based billing charges for the whole instance lifetime. A monthly free tier applies. Check the official pricing pages for current rates.
What is the Azure equivalent?
Azure Functions (direct match). Lambda function URLs map to the HTTP trigger in Azure Functions.