ESTIMATE · published-list estimate · runs in your browser
AWS Cost Optimization Calculator
Model AWS Savings Plan, rightsizing, EBS, and egress savings on published list pricing. Published-list estimate only. The math runs in your browser — your numbers never leave this page.
source currentPublished-list scenario. Not your bill, not a quote, not financial advice.verified 2026-09-09 · valid before 2026-10-10view sources ↓
▮ Assumptions
🔒Computed on your device. No accounts, no bill upload, nothing sent to a server or any vendor.
▮ Scenario result
Worked example
Example inputs: a fixed AWS scenario, evaluated by the same engine used by this calculator.
The modeled baseline is $38,219.60/mo; the bounded scenario models $12,243.89/mo in savings and ends at $25,975.71/mo.
Cost classification: Modeled savings
Dominant cost driver: compute ($22,177.40/mo)
Decision rule: Commitment sized to post-rightsize compute. Committing to the original baseline would over-commit ~15% to capacity you're removing — binding for the term.
Scope / sensitivity: rightsize→storage→egress→commit so commitment is sized to real need. Commitments are binding; rates are representative scenarios, not quotes.
Signal
Result
Scenario monthly cost
$25,975.71/mo
Modeled monthly change
$12,243.89/mo savings
rightsize compute
$3,326.61/mo — compute -15% (applied first)
reduce iops
$30.00/mo — drop 6000 overprovisioned gp3 IOPS
reduce egress
$2,289.50/mo — egress -40% (tiered recompute)
commit:3yr all upfront
$6,597.78/mo — 70% of rightsized compute @ ~50% (scenario)
Example inputs only, not a quote or your bill. Static output is generated from the real calculator engine at build date 2026-09-14 and carries the same valid-before boundary 2026-10-10. If source evidence becomes stale or the example contains an unpriced resource, this block suppresses the computed total instead of publishing a confident number.
Decision guidance
AWS cost decisions this calculator can test
Use this page to model an AWS cost-optimization sequence against representative Linux on-demand prices in us-east-1. It separates EC2 compute, EBS storage and provisioned performance, internet egress, and a Savings Plans scenario so that one lever cannot claim the same saving twice.
Questions it answers
How much EC2 spend remains after rightsizing the current instance fleet before any commitment is applied?
Do gp3 IOPS, gp3 throughput, gp2-to-gp3 changes, or snapshot-class changes move a separately billed EBS meter?
How much does an egress reduction save after the free allowance and tiered data-transfer rates are recomputed?
When it returns zero or refuses a claim
An instance type or EBS product outside the verified table suppresses the total instead of substituting an approximate rate.
A storage migration is rejected when it moves more capacity than exists or when the target class is not cheaper.
Savings Plans coverage is applied to the post-rightsize compute baseline. The result warns when committing to the original fleet would lock in capacity that the scenario removes.
Verify against your invoice
Match EC2 instance families, counts, and monthly running hours to the Usage Report or Cost and Usage Report.
Match EBS gp2/gp3, provisioned IOPS, provisioned throughput, and snapshot storage to their separate invoice lines.
Compare internet data transfer out by tier, then size any Savings Plans coverage from the stable post-rightsize baseline rather than the historical peak.
The calculator remains a published-list scenario, not a quote or your actual bill. Use the source links and invoice lines below before acting.
Representative published-list prices, re-verified on a freshness schedule. When a rate goes stale or a resource is not in the verified table, the total is suppressed rather than guessed.