AWS Lambda Cost Calculator (invocations + GB-seconds)

Estimate Lambda-style serverless cost from request volume and GB-second compute. Compare baseline vs peak traffic with your region/runtime pricing.

Inputs

Invocations (per month)
Avg 19.04 req/sec.
Avg RPS
Use steady-state invocations/sec.
Est 52,531,200 invocations/month.
Avg duration (ms)
0.12 sec avg runtime.
Memory (MB)
0.5 GB billed memory.
Price ($ / 1M requests)
Price ($ / GB-second)
Deducts 1M requests + 400k GB-sec.
Scenario presets

Results

Estimated monthly total
$53.13
Compute cost (GB-seconds)
$43.33
Request cost
$9.80
GB-seconds (before free tier)
3,000,000
Billable invocations
49,000,000
Billable GB-seconds
2,600,000
Cost per 1M invocations
$1.08
GB-sec per invocation
0.06

How to get your inputs

  • Inputs: use billing exports, metrics, or logs to get real counts/GB where possible.
  • Units: convert throughput (Mbps) or rates (RPS) into monthly units when needed.
  • Scenarios: build a baseline and a high-usage scenario to avoid under-budgeting.

Result interpretation

  • GB-seconds per invocation is the main compute driver; reduce duration or memory to lower cost.
  • If request cost is small, focus on latency and memory tuning first.

Common mistakes

  • Using a single average and ignoring peak/incident scenarios.
  • Double-counting or missing adjacent line items (transfer, logs, retries).

Advanced inputs to capture

  • Use p50 and p95 duration for baseline and peak scenarios.
  • Memory size drives GB-seconds; model per-function differences.
  • Apply free tier or discounts as separate adjustments.
  • Include async retries or error bursts in invocation counts.

Scenario planning

Scenario Invocations Duration Memory
Baseline Expected p50 Configured
Peak High p95 Configured

Validate after changes

  • Compare your estimate to the first real bill and adjust assumptions.
  • Track the primary driver metric (requests/GB/count) over time.

Next steps

Guides All calculators Guide: Lambda pricing (what to include) Guide: Lambda cost optimization Guide: concurrency & cold starts Guide: Lambda vs Fargate cost
Advertisement

Example scenario

  • 50M invocations/month, 120ms avg duration, 512MB memory -> estimate requests + compute charges.
  • Peak 220% scenario shows bursty months or incident spikes.

Included

  • Request fees from invocations/month and $ per 1M requests.
  • Compute fees from GB-seconds (invocations x duration x memory GB) and $/GB-second.
  • Optional RPS to monthly invocations estimator.
  • Optional free tier deduction (toggle).
  • Baseline vs peak scenario table for invocation spikes.

Not included

  • Logging/metrics (for example, CloudWatch), data transfer, and downstream service costs.
  • Provisioned concurrency and other add-ons unless you model them separately.

How we calculate

  • GB-seconds = invocations x (duration_ms / 1000) x (memory_MB / 1024).
  • Request cost = billable_invocations / 1,000,000 x $ per 1M requests.
  • Compute cost = billable_GB_seconds x $ per GB-second.
  • Total = request cost + compute cost (excluding logs, transfer, etc).

FAQ

Why do I need to enter pricing?
Lambda pricing varies by region, architecture, and discounts. Use your effective rates for the best estimate.
Does this include CloudWatch logs and metrics?
No. Logging and metrics are usually separate line items. Add them using a logging calculator if relevant.
How do I estimate duration and memory?
Use p50/p95 duration from your monitoring and the configured memory size. Model a few scenarios if you're unsure.

Related tools

Guide: Lambda pricing (what to include) Guide: Lambda cost optimization Guide: concurrency & cold starts Guide: Lambda vs Fargate cost Lambda vs Fargate cost (compare) Guide: CloudWatch Logs pricing Log cost calculator Egress cost calculator

Related guides

S3 pricing: a practical model for storage, requests, egress, and replication
A practical S3 pricing guide: what to include (GB-month, requests, egress, replication) and how to estimate the key inputs without copying price tables.
CDN cost comparison: how to compare pricing across providers
A practical framework to compare CDN pricing across providers: normalize bandwidth, requests, regions, cache fill, and contract terms before choosing the lowest total cost.
Cloud cost estimation checklist: build a model Google (and finance) will trust
A practical checklist to estimate cloud cost without missing major line items: requests, compute, storage, logs/metrics, and network transfer. Includes a worksheet template, validation steps, and the most common double-counting traps.
Copy storage pricing: what you pay for when data moves
A practical guide to pricing storage copy operations (cross-region copy, replication, backups) across S3-like object storage: transfer, requests, and extra storage.
Google Kubernetes Engine (GKE) pricing: nodes, networking, storage, and observability
GKE cost is not just nodes: include node pools, autoscaling, requests/limits (bin packing), load balancing/egress, storage, and logs/metrics. Includes a worked estimate template, pitfalls, and validation steps to keep clusters right-sized.
S3 CRR vs SRR cost: what changes (transfer, storage, requests)
A practical cost comparison of S3 cross-region replication (CRR) vs same-region replication (SRR). Compare transfer/feature fees, extra replica storage, and request costs - with calculators.
Advertisement

Disclaimer

Educational use only. Not legal, financial, or professional advice. Results are estimates based on the inputs and assumptions shown on this page. Verify pricing and limits with your providers and documentation.

Last updated: 2026-02-23