Free calculator · Cloud

Estimate your AWS savings, lever by lever

Enter your monthly AWS bill and how it splits. The calculator applies five savings levers in order (rightsizing, Spot, Savings Plans, gp2 to gp3 and gateway endpoints) and shows the saving from each, a likely range and what it leaves out.

How this is calculated Related service: Cloud & DevOps

AWS cost savings calculator

Enter your monthly AWS bill, how it splits and where each lever stands today. The levers are applied in order, each to the spend the one before left, so no saving is counted twice.

Your bill

Currency

Changes the symbol only; nothing is converted.

Monthly cloud bill (USD)

How the bill splits

Percent of the monthly bill, by kind of spend.

Compute (%)

Database (%)

Storage (%)

Network (%)

Other (%)

Adds up to 100%.

01Rightsize idle compute

Spend on instances that sit idle or are bigger than their load. AWS Compute Optimizer reports both.

Idle or oversized (% of compute)

Share of that removed (%)

Saves $1,375 a month: 20% idle × 50% removed, on $13,750 of compute.

02Move interruptible work to Spot

Work that can be stopped and restarted, such as stateless web servers, containers, CI/CD and batch jobs (AWS Well-Architected).

Could run on Spot (% of compute)

Already on Spot (% of compute)

Saves $2,228 a month: 30% of the $12,375 of compute left after rightsizing moves to Spot, at 60% off.

03Raise Savings Plans coverage

Coverage is the share of eligible usage, at On-Demand prices, that Savings Plans pay for (how AWS measures it).

Coverage today (%)

Target coverage (%)

Saves $1,516 a month: coverage rises from 0% to 70% of the $8,663 still On-Demand, at 25% off.

04Move gp2 volumes to gp3

gp3 includes 3,000 IOPS and 125 MB/s at any size and costs up to 20% less per GB than gp2 (Amazon EBS).

Storage spend on gp2 volumes (%)

Saves $300 a month: the $1,500 of storage on gp2 costs 20% less on gp3.

05Use gateway endpoints for S3 and DynamoDB

Gateway endpoints have no hourly or data-processing charge (Amazon VPC pricing), but they only carry traffic to S3 and DynamoDB in the same Region (gateway endpoints).

NAT processing for S3 and DynamoDB (% of network)

Saves $500 a month: the $500 of NAT processing for that traffic stops being charged.

Adjust assumptions

Discount rates

Spot discount (%)

AWS quotes up to 90% off On-Demand (Spot pricing). In the Spot Instance Advisor data on 8 Oct 2026, the median for Linux instance types in US East (N. Virginia) was 63%.

Savings Plans discount (%)

AWS quotes up to 66% off On-Demand for Compute and 72% for EC2 Instance Savings Plans (plan types); the plan, term and payment option set your rate.

gp3 saving against gp2 (%)

AWS's pricing examples use $0.08 per GB-month for gp3 against $0.10 for gp2 (EBS pricing). Extra IOPS or throughput lowers the saving.

Low end of the range: share of each lever achieved

The high end removes all idle compute and does every other lever in full.

25%50%75%

Estimated savings

Savings per month

$5,918

23.7% of your $25,000 bill, or $71,021 a year.

Likely range: $3,235 to $6,878; From each lever 50% done to all idle compute removed.
Monthly bill after these savings: $19,082

Saving per lever, per month

Rightsizing idle compute$1,375
Spot for interruptible work$2,228
Savings Plans coverage$1,516
gp2 volumes to gp3$300
Gateway endpoints$500

Not in this estimate: database and other services ($6,750 a month), data transfer out, NAT hourly charges, extra gp3 IOPS, S3 classes and snapshots, out-of-hours scheduling, support plans and taxes, and engineering time.

How this is calculated

The calculator splits your monthly bill into compute, database, storage, network and other spend, then applies five AWS savings levers in a fixed order, each to the slice it affects and to what the lever before it left. Every rate is an input you can change; the defaults are examples set against AWS's published figures.

Step by step

Split the bill: each slice is its share of the monthly bill. If the shares don't add up to 100%, each is scaled so they do. Database and other services get no lever.
Rightsizing: compute spend × idle share × share of that idle spend removed.
Spot: compute left after rightsizing × (Spot-eligible share − share already on Spot, never below zero) × Spot discount.
Savings Plans: compute still On-Demand after Spot × (target coverage − coverage today, never below zero) × Savings Plans discount.
gp2 to gp3: storage spend × share on gp2 × gp3 saving.
Gateway endpoints: network spend × share that is NAT processing for S3 and DynamoDB in the same Region. Gateway endpoints have no hourly or data-processing charge, so all of that processing charge is saved.
Total: the five savings added together. The bill after savings is the bill minus the total.
Range: the low end re-runs every lever at the low-end share (half by default); the high end removes all idle compute and does every other lever in full. The estimate always sits inside the range.

Default assumptions

Assumptions marked adjustable can be changed in the calculator; the others are fixed parts of the model.

Default assumptions and their sources
Assumption	Default	Sources
Monthly cloud bill (example)adjustable	$25,000 a month	None
Compute share of the billadjustable	55%	None
Database share of the billadjustable	20%	None
Storage share of the billadjustable	10%	None
Network share of the billadjustable	8%	None
Other services' share of the billadjustable	7%	None
Idle or oversized share of compute spendadjustable	20%	[9]
Share of idle spend removedadjustable	50%	None
Share of compute that can run on Spotadjustable	30%	[10]
Share of compute already on Spotadjustable	0%	None
Spot discount below On-Demandadjustable	60%	[4] [3]
Savings Plans coverage todayadjustable	0%	[2]
Target Savings Plans coverageadjustable	70%	[2]
Savings Plans discount below On-Demandadjustable	25%	[1]
Share of storage spend on gp2 volumesadjustable	60%	None
gp3 saving against gp2adjustable	20%	[5] [6]
Share of network spend that is NAT processing for same-Region S3 and DynamoDBadjustable	25%	[7]
Low end of the range: share of each lever achievedadjustable	50%	None
NAT processing charge removed for traffic moved to gateway endpoints	100%	[7] [8]

What this doesn’t model

Database and other services get no lever: database rightsizing, Reserved Instances and Database Savings Plans aren't modelled.
Shares apply to today's spend rather than to On-Demand-equivalent usage, so results are approximate where part of the bill is already discounted.
The levers run in a fixed order (rightsizing, Spot, Savings Plans), so each acts on what the one before left; a different order would split the saving differently.
Discounts and prices vary by Region, instance type, term and payment option. The defaults are examples, not quotes.
The range is a planning band built from your inputs, not a statistical confidence interval.
Data transfer to the internet, between Regions and between Availability Zones.
NAT gateway hourly charges, and NAT traffic to anything other than S3 and DynamoDB in the same Region.
gp3 IOPS or throughput bought above the included 3,000 IOPS and 125 MB/s.
S3 storage classes and lifecycle rules, snapshots and unattached volumes.
Switching non-production instances off outside working hours.
Support plans, Marketplace charges, taxes, credits and privately negotiated pricing.
The engineering time the changes take, and the cost of a commitment your usage later falls below.

Sources

Amazon Web Services, Savings Plans types. Accessed 8 Oct 2026. Compute Savings Plans are up to 66% off On-Demand, EC2 Instance Savings Plans up to 72% and Database Savings Plans up to 35%.
Amazon Web Services, Understanding coverage metrics and calculations. Accessed 8 Oct 2026. Coverage is the On-Demand equivalent of usage covered by Savings Plans, divided by that plus eligible usage billed at On-Demand rates.
Amazon Web Services, Amazon EC2 Spot Instances pricing. Accessed 8 Oct 2026. Spot Instances are available at up to 90% off On-Demand prices, which adjust gradually with long-term supply and demand.
Amazon Web Services, Spot Instance Advisor. Accessed 8 Oct 2026. Savings over On-Demand and interruption frequency per instance type over the last 30 days. Its data on 8 Oct 2026 gave a median saving of 63% across Linux instance types in US East (N. Virginia).
Amazon Web Services, Amazon EBS General Purpose volumes. Accessed 8 Oct 2026. gp3 is up to 20% lower in price per GB than gp2, with a baseline of 3,000 IOPS and 125 MB/s at any volume size.
Amazon Web Services, Amazon EBS pricing. Accessed 8 Oct 2026. The pricing examples use $0.08 per GB-month for gp3 and $0.10 for gp2; gp3 IOPS and throughput above the included baseline cost extra.
Amazon Web Services, Amazon VPC pricing. Accessed 8 Oct 2026. NAT gateways are charged per hour and per GB processed ($0.045 each in the page's US East (Ohio) example); gateway VPC endpoints have no data-processing or hourly charge.
Amazon Web Services, Gateway endpoints. Accessed 8 Oct 2026. Gateway endpoints serve Amazon S3 and DynamoDB at no additional charge; traffic to those services in another Region does not use them.
Amazon Web Services, What is AWS Compute Optimizer?. Accessed 8 Oct 2026. Recommends rightsizing and identifies idle resources from 14 days of CloudWatch utilisation by default.
Amazon Web Services, COST07-BP01 Perform pricing model analysis (AWS Well-Architected Framework, Cost Optimization Pillar) (27 Jun 2024). Accessed 8 Oct 2026. Commitment discounts for long-running resources; Spot for interruptible work such as stateless web servers, containerised workloads, CI/CD and big-data jobs.

Last reviewed 8 Oct 2026 by the QuantmHill engineering team. Found an error?

Link to or cite this tool

Writing about this topic? Link to the calculator or cite it. Its method, defaults and sources are all on this page, so readers can check the numbers.

Page link

Citation

QuantmHill. (2026). AWS cost savings calculator [Online calculator]. Last reviewed 8 Oct 2026. https://quantmhill.com/tools/cloud-cost-and-aws-savings-calculator

Embed this calculator

You can put this calculator on your own site for free. Paste the code below where it should appear. It loads the same calculator in a frame, with a link back to this page for the full method and sources.

Embed code

<iframe src="https://quantmhill.com/embed/tools/cloud-cost-and-aws-savings-calculator" title="AWS cost savings calculator by QuantmHill" width="100%" height="900" loading="lazy" style="border:0;max-width:960px"></iframe>
<p>Calculator by <a href="https://quantmhill.com/tools/cloud-cost-and-aws-savings-calculator">QuantmHill</a></p>

The credit line links to this page with the anchor text “QuantmHill”. You may edit it, add rel="nofollow" or remove it — the calculator works the same either way. Add ?theme=light or ?theme=dark to the iframe address to fix its colour scheme; otherwise it follows the visitor's system setting.

Optional auto-height script

<script>
window.addEventListener("message", function (e) {
  if (e.origin !== "https://quantmhill.com") return;
  var d = e.data;
  if (!d || d.source !== "quantmhill-embed" || typeof d.height !== "number") return;
  var frames = document.querySelectorAll('iframe[src^="https://quantmhill.com/embed/"]');
  for (var i = 0; i < frames.length; i++) {
    if (frames[i].contentWindow === e.source) {
      frames[i].style.height = Math.min(4000, Math.max(200, Math.ceil(d.height))) + "px";
    }
  }
});
</script>

Add this once per page, after the iframe, if you want the frame to grow and shrink with the calculator instead of using the fixed height above. It accepts messages from quantmhill.com only and resizes only the frame that sent them.

Frequently asked questions

The monthly saving from five AWS levers: rightsizing idle compute, moving interruptible work to Spot, raising Savings Plans coverage, moving EBS volumes from gp2 to gp3, and sending same-Region S3 and DynamoDB traffic through gateway endpoints instead of a NAT gateway. It uses your bill, how it splits and the rates you enter, and shows each lever's saving, a likely range and what it leaves out.

So no saving is counted twice. Rightsizing shrinks the compute that Spot and Savings Plans then apply to, and compute moved to Spot leaves the On-Demand spend that Savings Plans cover. Applying each lever's headline rate to the whole bill would overstate the total.

They are examples set at or below AWS's published figures. AWS says Spot is up to 90% off On-Demand, Compute Savings Plans up to 66% and EC2 Instance Savings Plans up to 72%, and gp3 up to 20% cheaper per GB than gp2. The 60% Spot default sits just under the 63% median saving for Linux instance types in US East (N. Virginia) in AWS's Spot Instance Advisor data on 8 October 2026. Replace them with your own rates.

AWS Compute Optimizer gives rightsizing recommendations and flags idle resources, the Savings Plans coverage report shows your current coverage, the Spot Instance Advisor lists the saving for each instance type, and the EBS console shows which volumes are still gp2. Your bill broken down by service gives the split.

Partly. Rightsizing, interruptible capacity and commitment discounts exist on other clouds, so those levers carry over if you enter that provider's rates. The gp2-to-gp3 and gateway endpoint levers, and every default and source here, are specific to AWS; set them to zero for another cloud.

The low end re-runs the model with every lever only partly done: 50% by default, which you can change under Adjust assumptions. The high end removes all idle compute and does every other lever in full. It is a planning band built from your inputs, not a statistical confidence interval.

Want an engineer to check your numbers?

Send us your inputs and the decision you're weighing. We'll reply within one business day with an honest read on whether we can help.

Talk to an engineer

Estimated savings

How this is calculated

Step by step

Default assumptions

What this doesn’t model

Sources

Link to or cite this tool

Embed this calculator

Frequently asked questions

What does this calculator estimate?

Why are the levers applied in order instead of added up?

Where do the default rates come from?

How do I find my own numbers?

Does it work for Azure or Google Cloud?

What does the likely range mean?

Want an engineer to check your numbers?

Estimated savings