Home/Blog/Risk of Over-Committing
Explainer · Commitment Management

The Risk of Over-Committing to Cloud Discounts

Cloud discounts feel like free money, so the instinct is to buy as much as possible. That instinct is the trap. Commit past your stable base and utilization collapses, turning a discount that was meant to save you money into a multi-year liability you cannot easily escape.

Updated May 20269 min readAWS · Azure · GCP · OCI

The risk of over-committing to cloud discounts is that a reservation, savings plan, or committed use discount is a contract: you agree to pay for a level of usage for one to three years whether or not you actually use it. Commit to more than your usage reliably sustains and the unused portion becomes pure waste, paid for and consumed by nothing. The discount that was supposed to cut your bill ends up adding a fixed cost you cannot turn off. This is the single most common way a well-intentioned commitment strategy backfires, and it is entirely avoidable.

This article is part of the complete guide to cloud commitment management. Across the 500-plus environments we have optimized since 2019, over-commitment is the failure mode we are most often called in to fix, and it almost always traces back to chasing coverage without watching utilization.

How over-commitment happens

It rarely looks reckless in the moment. The usual paths are:

  • Chasing 100 percent coverage. A team treats coverage as a score to maximize and commits to the peak of the usage curve, not the floor. When usage drops below the peak, the commitment keeps charging.
  • Committing before rightsizing. Reserving an oversized fleet locks the discount onto capacity that should have been cut, the mistake explained in why you should rightsize before you commit.
  • Forecasting growth that does not arrive. Buying three year commitments against an optimistic roadmap, then watching the workload shrink, migrate, or get re-architected.
  • Ignoring workload churn. Committing to specific instance families that the engineering team then moves off, stranding the reservation.

What it costs when utilization collapses

The damage shows up in the utilization metric, the second of the two numbers explained in coverage and utilization. Every percentage point of unused commitment is money spent on nothing. A savings plan at 80 percent utilization is wasting a fifth of what you committed; if that plan was meant to deliver a 30 percent discount, the waste can erase the saving entirely and leave you paying more than on-demand would have cost. Worse, unused commitment does not roll over, so an idle hour is gone for good, which is why this is one of the hidden costs of idle commitments.

When a discount becomes a loss

Commit to $10/hour at a 30% discount and you pay $7/hour. If usage only draws $6 of it, your real cost per used dollar is $7 divided by $6, about $1.17, which is 17% more than on-demand. The discount has flipped into a penalty.

Why it is hard to escape

The reason over-commitment is so dangerous is that the exits are limited. A standard AWS reserved instance can sometimes be sold on the Reserved Instance Marketplace, and convertible reservations can be exchanged, but savings plans and most committed use discounts cannot be cancelled or sold at all. The options and their limits are covered in selling and exchanging unused reservations. For everything that cannot be unwound, you are simply paying out the term. That asymmetry, easy to buy, hard to exit, is exactly why the buying discipline matters so much.

The guardrails that prevent it

Over-commitment is preventable with a few disciplines, all part of the buying sequence in how to build a commitment purchase strategy:

  • Commit to the floor, not the peak. Find the stable base with commitment forecasting and leave the variable top on-demand.
  • Rightsize first. Never commit to capacity you are about to cut.
  • Favor flexible instruments. Savings plans and convertible reservations follow your workloads, reducing the chance of stranding. See reserved instances vs savings plans vs CUDs.
  • Ladder the purchase. Staggered tranches limit how much can be wrong at once, the technique in how to ladder cloud commitments.
  • Set a utilization floor and monitor it. Treat anything under 95 percent utilization as an alert, not an annual surprise.

Worried you have already over-committed?

An audit measures your real utilization, identifies idle commitment, exchanges or sells what it can, and rebuilds the portfolio on the stable base. On the performance model, if we do not save you money, there is no fee.

Get a commitment audit →

The conservative bias is the right one

Because over-commitment is hard to escape and under-commitment only means leaving some savings on the table, the asymmetry argues for caution. It is almost always better to be slightly under-covered at near-perfect utilization than over-covered with leaking commitments. You can always buy more on the stable base next quarter; you cannot easily give back a three year commitment. Holding that conservative bias, and topping up gradually through a ladder, is how you capture most of the discount with very little of the risk. The ongoing measurement that keeps you honest is in how to track commitment ROI.

Where this fits

Avoiding over-commitment is the risk side of the commitment cluster. Read the complete guide to cloud commitment management for the full discipline, and download The Commitment Strategy Playbook: RIs, Savings Plans, CUDs for the risk worksheets. When you want the portfolio sized safely and managed for you, see our commitment management service.

The Cloud Cost Brief

Cloud pricing moves. We tell you when it matters.

New commitment instruments, FOCUS changes, hyperscaler pricing shifts, and the plays that actually move a bill. No schedule, no filler.

Subscribe · Work email only