How is Lambda pricing calculated?

Lambda charges per request ($0.20 per million) and per GB-second of compute ($0.0000166667 for x86). A GB-second is the memory allocated (in GB) multiplied by execution duration (in seconds). The free tier includes 1 million requests and 400,000 GB-seconds per month.

Does increasing memory always increase cost?

Not necessarily. Lambda allocates vCPU proportional to memory, so doubling memory also doubles available CPU. For CPU-bound functions, doubling memory can cut execution time in half, resulting in similar total cost but faster performance. Profile your function to find the optimal memory setting.

What is provisioned concurrency?

Provisioned concurrency keeps a specified number of Lambda execution environments initialized and ready to respond immediately, eliminating cold starts. You pay for provisioned concurrency whether functions are executing or not, at approximately 60% of the on-demand compute rate, plus the standard per-request charge.

Lambda Cost Estimator

ServerlessAWS

Estimate monthly AWS Lambda costs including compute, requests, and free tier.

Lambda Configuration

Memory (MB)

Average Execution Time (ms)

Invocations per Month

Architecture

Ephemeral Storage (MB)

512 MB included free. Additional storage billed per GB-second.

Include AWS Free Tier (1M requests + 400,000 GB-seconds/month)

Raw Output

Output will appear here...

About This Tool

The Lambda Cost Estimator calculates monthly AWS Lambda costs including compute charges, request fees, and free tier deductions. It accounts for memory allocation (which determines proportional vCPU), execution duration, provisioned concurrency, and Graviton (ARM) pricing. The tool helps you optimize function configuration for the best balance of performance and cost.

When to Use This Tool

•Estimating monthly Lambda costs for a new serverless API based on projected request volume and average duration.
•Comparing x86 vs. Graviton (ARM) Lambda pricing to quantify savings from architecture migration.
•Calculating the cost of provisioned concurrency for latency-sensitive functions that cannot tolerate cold starts.
•Modeling how memory allocation changes affect both cost and execution duration due to proportional vCPU scaling.

Frequently Asked Questions

How is Lambda pricing calculated?: Lambda charges per request ($0.20 per million) and per GB-second of compute ($0.0000166667 for x86). A GB-second is the memory allocated (in GB) multiplied by execution duration (in seconds). The free tier includes 1 million requests and 400,000 GB-seconds per month.
Does increasing memory always increase cost?: Not necessarily. Lambda allocates vCPU proportional to memory, so doubling memory also doubles available CPU. For CPU-bound functions, doubling memory can cut execution time in half, resulting in similar total cost but faster performance. Profile your function to find the optimal memory setting.
What is provisioned concurrency?: Provisioned concurrency keeps a specified number of Lambda execution environments initialized and ready to respond immediately, eliminating cold starts. You pay for provisioned concurrency whether functions are executing or not, at approximately 60% of the on-demand compute rate, plus the standard per-request charge.

Related Learning Guides

Lambda Performance Tuning26 min read
Cost Optimization Strategies26 min read

Disclaimer: This tool runs entirely in your browser. No data is sent to our servers. Always verify outputs before using them in production. AWS, Azure, and GCP are trademarks of their respective owners.