When to buy reserved instances: timing the commitment right

Quick answer

Buy reserved instances (or savings plans) when a workload's usage is steady, predictable, and expected to persist for the commitment term, and after you have right-sized it so you reserve the capacity you will actually run. Reserve only the baseline you are confident will stay, leaving variable or uncertain usage on-demand or spot. The wrong times to buy are before right-sizing (you lock in over-provisioning), for volatile or short-lived workloads (the commitment may strand), or speculatively. In short: right-size first, then reserve the durable baseline you are sure of.

Reserved instances are a powerful discount, but they are a commitment, and a commitment made at the wrong time or for the wrong capacity turns savings into waste. The question is not whether to use reservations, for steady workloads you should, but when a given workload is actually ready to be reserved. Timing and sizing the commitment right is what separates real savings from stranded commitments.

The conditions for reserving

Condition	Why it matters
Steady usage	The capacity runs consistently
Predictable and durable	Will persist through the term
Right-sized first	You reserve the size you will run
Baseline, not peak	Reserve the always-on portion

A workload is ready to reserve when its usage is steady and predictable, expected to persist for the commitment term (one or three years), and already right-sized. Reserve the baseline capacity that runs consistently, not the variable peaks, so the reservation always has matching usage to apply the discount. These conditions ensure high utilization, which is what makes a reservation pay off.

Right-size before you reserve

The most important rule is to right-size first. If you reserve an oversized instance and then right-size it, the reservation is stranded on capacity you no longer use, and the discount is wasted. Running the right-sizing pass before committing ensures you reserve the size you will actually run. Reserving before right-sizing locks in over-provisioning, the exact opposite of the intended saving.

When not to buy

Do not reserve volatile, uncertain, or short-lived workloads, the commitment may strand if the workload changes or ends. Do not reserve speculatively for growth you are not sure of. Do not reserve capacity you might migrate to a different instance family soon. For these, on-demand or spot keeps flexibility, and a flexible savings plan can cover steady spend without locking to a specific configuration, reducing stranding risk.

A practical reservation strategy

Analyze usage to find the steady baseline that has run consistently for months and is expected to continue, right-size it, then reserve that baseline (preferring flexible savings plans for changing infrastructure), and leave everything variable on-demand or spot. Review utilization over time and factor expiring reservations into future purchases. Buying at the right time, after right-sizing, for durable baseline usage, is what makes commitments deliver. Price your baseline against the resource catalog so you commit to capacity you are sure of.

FAQ

When should I buy reserved instances?

When a workload's usage is steady, predictable, and expected to persist for the commitment term, and after you have right-sized it so you reserve the capacity you will actually run. Reserve only the baseline you are confident will stay, leaving variable or uncertain usage on-demand or spot. These conditions ensure the reservation stays highly utilized, which is what makes the discount pay off.

Should I right-size before buying reserved instances?

Yes, always. If you reserve an oversized instance and then right-size it, the reservation is stranded on capacity you no longer use and the discount is wasted. Running the right-sizing pass before committing ensures you reserve the size you will actually run. Reserving before right-sizing locks in over-provisioning, the opposite of the intended saving, so right-size first, then reserve.

When should I not buy reserved instances?

Do not reserve volatile, uncertain, or short-lived workloads, since the commitment may strand if the workload changes or ends. Do not reserve speculatively for growth you are unsure of, or capacity you might migrate to a different instance family soon. For these, keep on-demand or spot flexibility, or use a flexible savings plan that covers steady spend without locking to a specific configuration.

How much capacity should I reserve?

Reserve the steady baseline that runs consistently and is expected to persist through the commitment term, not the variable peaks. Reserving the always-on portion ensures the reservation always has matching usage to apply the discount, keeping utilization high. Leave variable and uncertain usage on-demand or spot. Over-committing beyond your durable baseline risks stranding reservations on capacity you do not always use.

Should I buy reserved instances or a savings plan?

For workloads whose infrastructure may change, a flexible Compute Savings Plan is often safer because it applies across instance families, sizes, and regions, reducing the risk of stranding the commitment. Reserved instances suit stable, unchanging workloads or when you need a capacity reservation. Either way, right-size first and commit only to the durable baseline you are confident will persist through the term.

How does C3X help decide when to reserve?

C3X prices your infrastructure before you deploy, helping you right-size resources so you commit to the capacity you will actually run, and understand your steady baseline. Knowing the real, durable usage at design time helps you time and size a reservation or savings plan correctly, reserving the baseline you are sure of and keeping utilization high, rather than committing to capacity a workload later moves away from.

What to do next

Reserve the right baseline by pricing it first. C3X reads your Terraform and prices your resources against a live catalog. Start with the quickstart.