Free 2025 Pricing No Signup

AWS Lambda Cost Calculator

Enter your Lambda function config and get the exact monthly cost. Compare x86 vs ARM, track free tier usage, and find savings.

Quick Presets

Monthly Invocations

1,000,000

First 1,000,000 requests free every month

1K10K100K1M10M100M1B

Avg Execution Duration

200 ms

Lambda max timeout: 15 minutes (900,000 ms)

1ms100ms1s30s5min15min

Memory Allocation

512 MB

Range: 128 MB to 10,240 MB

128M256M512M1G2G4G6G10G

Architecture

x86_64

$0.0000166667

per GB-second

ARM Graviton2

$0.0000133334

20% cheaper

Provisioned Concurrency

Optional

Enable Provisioned Concurrency

Keeps functions warm to eliminate cold starts

No data stored. Runs entirely in your browser.

Cost Summary

Within Free Tier

Per Request

$0.00000000

Monthly

$0.00

Yearly

$0.00

Free Tier Used

Request charges $0.0000

Compute charges (GB-seconds) $0.0000

Total GB-seconds

Billable GB-seconds

Billable requests

Architecture

x86_64

x86 vs ARM Graviton2 — Same Workload

x86_64

$0.00

per month

$0.0000166667/GB-s

ARM Graviton2

-20%

$0.00

per month

$0.0000133334/GB-s Save $0.00

ARM Graviton2 costs 20% less than x86. Supported by Node.js, Python, Java, Go, Ruby, and .NET with no code changes required.

AWS Free Tier Usage

Resets monthly — never expires

Requests (1,000,000 free/month) 0 / 1,000,000

Compute (400,000 GB-seconds free/month) 0 / 400,000

Memory Optimization — Cost Comparison

Reducing memory reduces cost proportionally. Use AWS Lambda Power Tuning to find the optimal memory setting for your workload.

Cost Optimization Tips

Switch to ARM Graviton2 Save 20%

Change runtime architecture to arm64. No code changes needed for most runtimes. Takes 30 seconds in Lambda console.

aws lambda update-function-configuration --architectures arm64

Right-size memory allocation Save 30-70%

Most functions use far less memory than allocated. Use AWS Lambda Power Tuning to find the optimal memory vs cost tradeoff for your specific function.

Reduce execution duration Save 20-50%

Duration is billed in 1ms increments. Cache DB connections outside handler, use async operations efficiently, minimize cold start overhead.

Avoid unnecessary Provisioned Concurrency Common mistake

Provisioned Concurrency charges even when idle. Only use it when cold start latency directly impacts user experience — not for background jobs or infrequent functions.

Share this tool

Help other developers avoid surprise AWS Lambda bills

Share on X Share on LinkedIn

AWS Lambda Pricing Reference (2025)

Official AWS Pricing

Charge Type	x86_64	ARM Graviton2	Free Tier
Requests	$0.20 per 1M	$0.20 per 1M	1M / month
Compute (GB-seconds)	$0.0000166667	$0.0000133334	400K GB-s / month
Provisioned Concurrency	$0.0000041667/GB-s	$0.0000033334/GB-s	None

Prices for us-east-1. Other regions vary slightly. Duration billed in 1ms increments.

Frequently Asked Questions

AWS Lambda free tier includes 1,000,000 free requests per month and 400,000 GB-seconds of compute time per month. This free tier does not expire after 12 months — it applies permanently to every AWS account. A 128MB function running for 1 second uses 0.125 GB-seconds, meaning 400,000 GB-seconds gives roughly 3.2 million seconds of execution time per month at that configuration.

A GB-second equals 1 GB of memory allocated for 1 second. Formula: Memory (GB) x Duration (seconds) = GB-seconds. Example: 512MB function running for 200ms = 0.5 GB x 0.2 seconds = 0.1 GB-seconds. AWS bills in 1ms increments so you pay for exactly what you use.

ARM Graviton2 costs 20% less than x86 and often performs 10-20% faster. Node.js, Python, Java, Go, Ruby, and .NET all support arm64 without code changes. Only keep x86 if you have native compiled dependencies not available for ARM. For new functions, always start with ARM.

Provisioned Concurrency makes sense when cold start latency directly affects users — typically for user-facing APIs where cold starts add 500ms or more. It charges continuously whether invocations happen or not, so avoid it for background jobs, scheduled tasks, or low-traffic APIs.

This calculator uses AWS official pricing for us-east-1. Estimates are accurate when you enter your actual invocation count, duration, and memory values. Actual costs may vary due to regional pricing differences and other charges. Always verify in AWS Cost Explorer for exact billing.

More Developer Cost Calculators

GitHub Actions

CI/CD cost calculator

Rate limit calculator