CloudConsole

AWS Lambda pricing explained

Updated 17 November 2026 · How we write and check guides

Short answer

Lambda charges $0.20 per million requests plus duration in GB-seconds (memory allocated × run time, billed per millisecond): $0.0000166667 per GB-second on x86 and $0.0000133334 on ARM in us-east-1 at the time of writing. The first 1 million requests and 400,000 GB-seconds each month are free, so many small functions cost nothing.

Line chart of AWS Lambda monthly cost against invocations per month (millions), 1 gb for 200 ms each: x86, 50M: $169.80…
Monthly cost from the unit prices in this page's table (us-east-1, prices checked 17 November 2026); the marked points are the worked examples.

Pricing dimensions

DimensionUnitus-east-1 price
Requestsper invocation$0.20 per million
Duration, x86GB-second$0.0000166667
Duration, ARM (Graviton)GB-second$0.0000133334
Provisioned concurrency (kept warm)GB-second$0.0000041667
Duration on provisioned concurrencyGB-second$0.0000097222
Ephemeral storage above 512 MBGB-second$0.0000000309

From the AWS Price List API at the time of writing. The x86 duration rate falls to $0.000015 per GB-second beyond 6 billion GB-seconds a month, which only very large accounts reach.

A GB-second is one second of run time at 1 GB of configured memory. A 256 MB function running for 400 ms uses 0.25 × 0.4 = 0.1 GB-seconds. Memory, not CPU, is the dial: CPU is allocated in proportion to memory.

Worked examples

1. A small API. 5 million invocations a month at 512 MB and 120 ms average:

  • Duration: 5,000,000 × 0.5 GB × 0.12 s = 300,000 GB-seconds, inside the 400,000 free
  • Requests: (5,000,000 − 1,000,000) × $0.20 per million = $0.80
  • Total: $0.80. Without the free tier it would be $5.00 + $1.00 = $6.00.

2. A busy event processor. 50 million invocations at 1,024 MB and 200 ms:

  • Duration: 50,000,000 × 1 × 0.2 = 10,000,000 GB-s; minus 400,000 free = 9,600,000 × $0.0000166667 = $160.00
  • Requests: 49,000,000 × $0.20 per million = $9.80
  • Total: $169.80; on ARM the duration is 9,600,000 × $0.0000133334 = $128.00, so $137.80.

3. Provisioned concurrency. Ten 1 GB environments kept warm all month: 10 × 1 × 730 × 3,600 = 26,280,000 GB-s × $0.0000041667 = $109.50 before a single request, plus duration at the lower provisioned rate when they run.

To try other memory sizes and durations, use the Lambda cost calculator.

What is free

The monthly free tier of 1,000,000 requests and 400,000 GB-seconds applies to every account, not just new ones, and is shared across x86 and ARM functions in all Regions. Invocations from most AWS event sources are billed as normal requests; there is no extra charge for the trigger itself, but the source service (SQS, API Gateway, EventBridge) bills its own requests.

Charges around Lambda

  • CloudWatch Logs: every function writes logs, and ingestion at $0.50 per GB often exceeds the Lambda bill for chatty functions; see CloudWatch Logs pricing.
  • Functions in a VPC that call the internet go through a NAT gateway and pay its per-GB charge.
  • Waiting is billed: time spent awaiting a slow downstream API counts as duration.
  • Recursive loops (a function writing to the bucket that triggers it) multiply both requests and duration until something stops them.
  • API Gateway in front adds its own per-request price; see API Gateway pricing.

Seeing Lambda cost

In Cost Explorer filter Service = Lambda and group by Usage type: in us-east-1 you will see Request, Lambda-GB-Second and Lambda-GB-Second-ARM. To find which function is expensive, compare each function's Duration and Invocations metrics in CloudWatch, multiplied by its memory size, or tag functions and activate the tags for cost allocation.

Cutting it: why a Lambda bill is high.

Questions

How much does Lambda cost per invocation?

The request charge is $0.20 per million, or $0.0000002 per invocation, plus duration. A 128 MB function running 100 ms adds 0.0125 GB-seconds, about $0.0000002 on x86.

Is Lambda free?

Up to 1 million requests and 400,000 GB-seconds per month, every month. Beyond that you pay per request and per GB-second.

Does more memory make Lambda more expensive?

Per millisecond, yes, linearly. But more memory also gives more CPU, so a function can finish faster and cost the same or less; measure before assuming.

Is Lambda cheaper than Fargate or EC2?

For spiky or low traffic, usually yes. For steady high throughput, a container or instance that is busy most of the time is typically cheaper per request.

When this happens away from your desk

A runaway Lambda loop can burn through money in an hour. CloudConsole is being built to put alarms and costs on your phone so you notice it outside working hours.

About the app → · Download on the App Store

Sources