AWS Lambda cost calculator
Lambda cost calculator
Show the formula
GB-seconds = requests × duration (s) × memory (GB)
Cost = billable requests × $0.0000002 + billable GB-seconds × duration ratePrices checked 17 November 2026, us-east-1, on-demand, in US dollars. Other regions differ. A month is 730 hours, as in the AWS Pricing Calculator. Everything is calculated in your browser.
Lambda charges $0.20 per million requests plus duration in GB-seconds (memory in GB × seconds run): $0.0000166667 per GB-second on x86 and $0.0000133334 on Arm in us-east-1. The free tier covers 1 million requests and 400,000 GB-seconds a month. So 10 million 200 ms invocations at 1,024 MB cost about $28.47 a month on x86 after the free tier.
How AWS Lambda pricing works
A Lambda function’s bill has two main parts. Requests cost $0.20 per million, counted each time the function is invoked. Duration is billed in GB-seconds: the memory you configure, in GB, multiplied by how long each invocation runs, rounded up to the nearest millisecond. Initialisation code outside the handler counts, so cold starts add to duration.
GB-seconds = invocations × average duration (s) × memory (MB) / 1024
monthly cost = (invocations − free requests) × $0.0000002
+ (GB-seconds − free GB-seconds) × price per GB-second
+ ephemeral storage above 512 MB × duration × $0.0000000309 per GB-s
Memory can be set from 128 MB to 10,240 MB in 1 MB steps, and CPU scales with it: at 1,769 MB a function gets the equivalent of one vCPU. More memory costs more per millisecond but often finishes sooner, so the cheapest setting is found by measuring, not guessing.
Duration has volume tiers on x86 and Arm separately, counted across all functions on that architecture in the same region and account (or across an AWS Organization with consolidated billing). Few accounts reach them: the first discount starts after 6 billion GB-seconds a month on x86.
Lambda prices in us-east-1
Prices checked 17 November 2026 for US East (N. Virginia), on-demand, from the AWS Price List and the Lambda pricing page.
| Charge | x86 | Arm |
|---|---|---|
| Requests | $0.20 per million | $0.20 per million |
| Duration: First 6 billion GB-s (x86) / First 7.5 billion GB-s (Arm) | $0.0000166667 | $0.0000133334 |
| Duration: Next 9 billion GB-s (x86) / Next 11.25 billion GB-s (Arm) | $0.0000150000 | $0.0000120001 |
| Duration: Over 15 billion GB-s (x86) / Over 18.75 billion GB-s (Arm) | $0.0000133334 | $0.0000106667 |
| Provisioned Concurrency (per GB-s configured) | $0.0000041667 | $0.0000033334 |
| Duration with Provisioned Concurrency | $0.0000097222 | $0.0000077778 |
| Ephemeral storage above 512 MB | $0.0000000309 | $0.0000000309 |
Prices are per GB-second unless stated. Each architecture’s duration tiers are cumulative: on x86 the first 6 billion GB-seconds, the next 9 billion, then everything over 15 billion; on Arm the first 7.5 billion, the next 11.25 billion, then everything over 18.75 billion.
Price per millisecond by memory
| Memory | x86 per 1 ms | Arm per 1 ms |
|---|---|---|
| 128 MB | $0.0000000021 | $0.0000000017 |
| 256 MB | $0.0000000042 | $0.0000000033 |
| 512 MB | $0.0000000083 | $0.0000000067 |
| 1,024 MB | $0.0000000167 | $0.0000000133 |
| 1,769 MB | $0.0000000288 | $0.0000000230 |
| 2,048 MB | $0.0000000333 | $0.0000000267 |
| 3,008 MB | $0.0000000490 | $0.0000000392 |
| 4,096 MB | $0.0000000667 | $0.0000000533 |
| 8,192 MB | $0.0000001333 | $0.0000001067 |
| 10,240 MB | $0.0000001667 | $0.0000001333 |
The free tier, Arm and Provisioned Concurrency
- Free tier. 1 million requests and 400,000 GB-seconds a month, shared by every function in the account. Turn it off in the calculator if other functions already use it up.
- Arm (Graviton). Duration is 20% cheaper per GB-second than x86, with the same request price. Most interpreted runtimes move across easily; compiled dependencies and container images need an arm64 build.
- Provisioned Concurrency. Keeps a set number of execution environments initialised. You pay for the concurrency configured, for as long as it’s enabled (rounded up to five minutes), plus requests and a lower duration rate for the invocations it serves. Invocations beyond it run on demand at normal rates, and the free tier doesn’t apply to the function.
- Ephemeral storage. Every function gets 512 MB of
/tmpat no extra cost. Above that, up to 10,240 MB, you pay per GB-second for the extra storage while the function runs.
What else a Lambda workload costs
The calculator covers Lambda’s own charges. A real bill usually has more lines:
- CloudWatch Logs. Everything a function prints is ingested and stored. Busy functions that log every request can cost more in logs than in compute.
- The trigger. API Gateway, Application Load Balancer, SQS, EventBridge and Step Functions all bill separately.
- Data transfer and NAT. Traffic out to the internet, and a NAT gateway if functions in a VPC call the internet or AWS APIs without VPC endpoints.
- Features not modelled here. SnapStart, Lambda@Edge, Lambda Managed Instances, durable functions and tenant isolation have their own prices, and Compute Savings Plans also apply to Lambda.
To see what you actually spend, group Cost Explorer by service and then by usage type; the AWS cost breakdown guide shows how.
Running containers instead? The Fargate pricing calculator prices ECS tasks by vCPU, memory and hours.
Questions
How much does AWS Lambda cost per million requests?
$0.20 per million requests in us-east-1, on x86 and Arm alike, plus duration: $0.0000166667 per GB-second on x86 or $0.0000133334 on Arm. A million 100 ms invocations at 512 MB use 50,000 GB-seconds, about $0.83 on x86, so roughly $1.03 in total before the free tier.
Is AWS Lambda free?
Up to a point. The Lambda free tier includes 1 million requests and 400,000 GB-seconds of compute a month, shared by all functions in the account. That is 3.2 million seconds at 128 MB, or about 111 hours at 1 GB. Above that you pay the normal rates.
Do cold starts count towards Lambda duration?
Yes. AWS bills duration for the code in your handler and for initialisation code declared outside it, so a cold start’s init time adds to the bill. Duration is rounded up to the nearest millisecond.
Is Lambda cheaper on Arm (Graviton)?
Duration is 20% cheaper per GB-second on Arm ($0.0000133334 against $0.0000166667 in us-east-1) and requests cost the same. If your code and its dependencies run on Arm64, and it doesn’t run slower there, Arm costs less.
Does the free tier apply with Provisioned Concurrency?
No. AWS says the Lambda free tier doesn’t apply to functions with Provisioned Concurrency enabled. You pay for the concurrency you configure for as long as it’s enabled, plus requests and a lower duration rate for invocations it serves.
What does the Lambda cost calculator leave out?
Data transfer, CloudWatch Logs, the services that trigger the function (such as API Gateway or SQS), Savings Plans, SnapStart, Lambda@Edge, Lambda Managed Instances, durable functions and tenant isolation. Check those on the AWS pricing page if you use them.
CloudConsole shows your spend by service, with usage types and regions, plus each Lambda function’s metrics and logs, so a function that suddenly costs more stands out. On iPhone and Android.
About the app →