Calculator Inputs
Use the form below to estimate request, compute, storage, streaming, provisioned concurrency, and other monthly cost components.
Example Data Table
These examples show how the calculator can be used for quick scenario comparison.
| Scenario | Requests | Duration | Memory | Architecture | Free Tier | Estimated Total |
|---|---|---|---|---|---|---|
| Small API backend | 3,000,000 | 120 ms | 1,536 MB | x86 | On | $2.73 |
| Fleet telemetry enrichment | 7,440,000 | 2,000 ms | 1,024 MB | x86 | Off | $249.49 |
| Arm optimization trial | 5,000,000 | 250 ms | 1,024 MB | Arm | On | Varies with selected extras |
Formula Used
1) Billable requests
Billable Requests = max(0, Monthly Requests - Free Requests)
2) Total compute seconds
Total Compute Seconds = (Monthly Requests × Avg Duration ms ÷ 1000) + (Cold Starts × Init Duration ms ÷ 1000)
3) Monthly compute in GB-seconds
Monthly Compute GB-s = Total Compute Seconds × (Memory MB ÷ 1024)
4) Billable compute
Billable Compute GB-s = max(0, Monthly Compute GB-s - Free Compute GB-s)
5) Request cost
Request Cost = (Billable Requests ÷ 1,000,000) × Request Price Per Million
6) Compute cost
Raw Compute Cost = Billable Compute GB-s × Compute Rate
7) Ephemeral storage cost
Ephemeral GB-s = Total Compute Seconds × max(0, (Ephemeral Storage MB - 512) ÷ 1024)
Ephemeral Cost = Ephemeral GB-s × Ephemeral Storage Rate
8) Provisioned concurrency cost
Provisioned Cost = GB-hours × GB-hour Rate
9) Savings adjustment
Discounted Compute + Provisioned = (Raw Compute + Raw Provisioned) × (1 - Savings Discount %)
10) Final monthly total
Total = Request Cost + Discounted Compute Cost + Discounted Provisioned Cost + Ephemeral Cost + Streaming Cost + Other Monthly Cost
How to Use This Calculator
- Enter your expected monthly request count.
- Provide average billed duration in milliseconds.
- Set memory size and select the processor architecture.
- Review the default request and compute rates, then overwrite them if your region or contract differs.
- Choose whether free tier benefits should be applied.
- Add optional cold-start, streaming, ephemeral storage, and provisioned concurrency inputs when those costs matter.
- Add any other fixed monthly overhead for a fuller estimate.
- Press Calculate Pricing to see the result above the form, detailed metrics, and the Plotly chart. Export CSV or PDF when needed.
FAQs
1) What does this calculator estimate?
It estimates monthly and annual lambda spending from requests, execution time, memory allocation, optional storage, optional streaming, provisioned concurrency, discounts, and extra overhead.
2) Why does memory change price?
Compute usage is measured with memory included. When memory increases, each billed second converts into more GB-seconds, which raises compute cost unless execution time drops enough to offset it.
3) Why compare x86 and Arm?
Different architectures can use different pricing and performance profiles. This form lets you compare them quickly while keeping the rest of the workload assumptions identical.
4) Do cold starts affect spending?
They can. If initialization time is billed for your workload, extra startup milliseconds add compute seconds. The cold-start fields let you model that added runtime separately.
5) When should I disable free tier?
Disable it when modeling mature production accounts, consolidated billing scenarios, exhausted allowances, or cases where you want a conservative full-cost estimate.
6) Can I use custom regional or negotiated rates?
Yes. The request, compute, storage, streaming, and provisioned concurrency rate fields are editable, so you can match your own pricing assumptions.
7) What is provisioned concurrency in this form?
It is treated as an optional fixed usage block entered in GB-hours. If you know your provisioned concurrency usage and rate, this field folds it into the monthly estimate.
8) Why export CSV or PDF?
CSV helps with spreadsheets, audits, and scenario comparison. PDF is useful for sharing a clean snapshot with managers, clients, reviewers, or procurement teams.