FA Dev Tools

AWS Cost

What AWS will charge, and how to pay less for it: a Lambda cost calculator, and which Savings Plan or Reserved Instance to buy for EC2.

Estimate the monthly AWS Lambda bill for one function from how often it runs, how much memory it has and how long it takes — requests, compute (GB-seconds, tiered) and ephemeral storage, with or without the free tier.

Presets
Architecture

128–10,240 MB · 0.29 vCPU

Billed per 1 ms, rounded up — 100 ms each

512–10,240 MB; the first 512 MB is free

Free tier

1,000,000 requests + 400,000 GB-s a month, per account

Total per month
$0.00
$0.00 per year
$0.00 per 1M invocations
Requests
0 billable × $0.20 per 1M (1,000,000 free)
$0.00
Compute (duration)
0 billable GB-s of 50,000 (50,000 free)
$0.00
Ephemeral storage
Within the free 512 MB
$0.00
Instructions

Estimates the on-demand monthly cost of a single AWS Lambda function from its traffic, memory, duration and /tmp size. Everything is calculated in the browser; nothing is sent to AWS.

  1. Pick the Architecture — Arm (Graviton) is about 20% cheaper per GB-second.
  2. Enter how many Invocations the function gets and choose per month, day, hour or second.
  3. Set Memory and the Average duration from CloudWatch (the Duration metric, or the REPORT line in the logs).
  4. Raise Ephemeral storage only if you configured more than the default 512 MB of /tmp.
  5. Read the total and the breakdown underneath; it updates as you type.

Tips

  • Cost = requests × $0.20 per 1M + GB-seconds × the price per GB-second, where GB-seconds = invocations × duration (s) × memory (GB). Prices are the US East (N. Virginia) list prices from the AWS Lambda pricing page; most regions match, a few charge more.
  • Duration price tiers apply to the whole account's monthly GB-seconds per architecture and region, not per function — with other busy functions you may already be in a cheaper tier.
  • The free tier (1M requests + 400,000 GB-s a month) is shared by every function in the account, so untick it if other functions already use it up.
  • More memory also means more CPU (1,769 MB ≈ 1 vCPU), so a function often gets faster as memory goes up — the cheapest setting is not always the smallest.
  • Not included: provisioned concurrency, SnapStart, Lambda@Edge, data transfer, and the services around the function (API Gateway, CloudWatch Logs, SQS…).
  • A Compute Savings Plan takes about 12% (1 yr) to 17% (3 yr) off duration and provisioned concurrency, never off requests. It is the only plan that covers Lambda; see the Savings Plans tab.
  • Your inputs are kept in this browser and restored on reload.
  • Hit Example and click one of the highlighted Presets — API backend, Cron job, Image resize or Stream consumer (which is big enough to reach the cheaper tiers).