AWS Lambda vs Google Cloud Functions: pricing
AWS Lambda is cheaper for this workload (about $3.05/mo vs $14/mo). AWS Lambda is faas (request + gb-second) ($0.20 / 1M) and Google Cloud Functions is faas (now on cloud run model) ($0.40 / 1M). For 5M requests/month at 256 MB, 150 ms each plus 25 GB egress, the rough monthly totals are $3.05 and $14 respectively. Snapshot June 2026 — verify on the vendor's pricing page.
Data as of June 2026.
AWS Lambda vs Google Cloud Functions side by side
| Cost factor | AWS Lambda | Google Cloud Functions |
|---|---|---|
| Vendor | Amazon Web Services | Google Cloud |
| Pricing model | FaaS (request + GB-second) | FaaS (now on Cloud Run model) |
| Per 1M requests | $0.20 / 1M | $0.40 / 1M |
| Per GB-second | $0.0000167 / GB-s | $0.0000025 / GB-s |
| Free tier | 1,000,000 requests/month + 400,000 GB-s/month, perpetual (does not expire after 12 months). | 2,000,000 invocations + 400,000 GB-s + 200,000 GHz-s + 5 GiB egress per month. Cloud Functions (2nd gen) was renamed Cloud Run functions in 2024 and now bills on the Cloud Run model. |
| Scale to zero | Yes | Yes |
| Egress | $0.09/GB | varies |
| Regions | 30+ AWS regions worldwide. | 40+ Google Cloud regions. |
Sources: Amazon Web Services pricing · Google Cloud pricing.
Sample monthly cost
A rough monthly total for a sample workload: 5,000,000 requests/month, each ~150 ms at 256 MB of memory, plus 25 GB of egress. Computed after each platform's free tier; excludes platform minimums and regional variation, so treat it as a starting point:
| Component | AWS Lambda | Google Cloud Functions |
|---|---|---|
| Compute (after free tier) | $0.80 | $14 |
| Egress (25 GB) | $2.25 | varies |
| Estimated total / month | $3.05 | $14 |
Verdict
On cost for this sample workload, AWS Lambda is cheaper for this workload (about $3.05/mo vs $14/mo). But price is not the only factor: AWS Lambda (mature, deepest aws ecosystem (api gateway, sqs, dynamodb, eventbridge)) versus Google Cloud Functions (generous free tier (2m invocations + 400k gb-s + 5 gib egress)). Read each platform's full breakdown — AWS Lambda and Google Cloud Functions — and model your own workload in the calculator.
Frequently asked questions
Is AWS Lambda or Google Cloud Functions cheaper?
For a sample workload of 5M requests/month at 256 MB, 150 ms each plus 25 GB egress, AWS Lambda is cheaper for this workload (about $3.05/mo vs $14/mo). This is illustrative and after each platform's free tier; your real cost depends on memory, duration, egress and region. snapshot captured June 2026.
How do AWS Lambda and Google Cloud Functions price requests?
AWS Lambda: $0.20 per 1M requests + $0.0000166667 per GB-second (x86). Arm/Graviton2 is ~20% cheaper. Billed per 1 ms. Memory is configurable 128 MB-10 GB and sets the GB-second rate. Google Cloud Functions: Cloud Functions (2nd gen) was renamed 'Cloud Run functions' in Aug 2024 and bills on Cloud Run rates ($0.000024/vCPU-s + $0.0000025/GiB-s + $0.40/1M requests). 1st-gen kept its own invocations + GB-s + GHz-s model with the free tier shown. Snapshot June 2026 — verify on the vendor's pricing page.
Do AWS Lambda and Google Cloud Functions scale to zero?
AWS Lambda: yes, no charge when idle. Google Cloud Functions: yes, no charge when idle. Scale-to-zero saves money for spiky traffic but adds cold-start latency on the first request.
Which has the better free tier, AWS Lambda or Google Cloud Functions?
AWS Lambda: 1,000,000 requests/month + 400,000 GB-s/month, perpetual (does not expire after 12 months). Google Cloud Functions: 2,000,000 invocations + 400,000 GB-s + 200,000 GHz-s + 5 GiB egress per month. Cloud Functions (2nd gen) was renamed Cloud Run functions in 2024 and now bills on the Cloud Run model.
More comparisons
Last updated: 2026-06-21