Overview
The Commitment Manager is where you manage your AWS Reserved Instances and Savings Plans. Beyond listing what you own, it answers the two questions a commitment strategy actually turns on: how much your commitments are earning you, and how much of your eligible usage is still uncovered.
Health of your Savings Rate and Savings
The panel at the top of the page summarises the financial health of your commitment portfolio.
Effective savings rate
Your savings over the last 30 days, divided by what that same usage would have cost at on-demand rates — not by what you paid. The badge beside it shows the change in percentage points against the previous 30 days. A badge reading -0.3 pts means the rate slipped from roughly 21.3% to 21.0%; it does not mean your savings fell by 0.3%.
Total Savings
What your commitments actually earned: the on-demand cost of the usage they covered, minus what you paid, with any upfront amount spread across its term and unused commitment subtracted. Reserved Instances and Savings Plans are both included.
Switch between 12 mo and All Time. All Time shows the first month measured underneath, so you can tell how much history the figure rests on.
Reading the chart
The chart plots one point per hour. The bars stack into three bands, and two lines cross them:
On-demand — the top band: eligible usage that no commitment covered. This is the room you still have to commit.
The middle band — your saving for that hour: the on-demand value of the covered usage, minus what the commitments cost.
The base band — what your commitments cost you for that hour.
Covered On-demand (dashed line) — the on-demand value of everything your commitments covered, which is the top of the base and middle bands together.
Committed cost (solid line) — what you paid, spread evenly across the commitment's term.
Two readings matter most. A consistently thick top band is unused opportunity: more commitment would pay. And when the solid line climbs above the dashed one, the middle band disappears — you are paying more for a commitment than the usage it covered was worth, which is over-commitment.
Commitments tab
Lists every commitment across your linked accounts. The chips above the table break the list down by family — RDS Reserved Instances, EC2 Reserved Instances, OpenSearch Reserved Instances, ElastiCache Reserved Instances and Savings Plans — each with a count. A family you own none of still appears, with a count of zero.
Columns include Type, Account, Start Date, End Date, Days Remaining, Commitment, Region and Payment Option. Some sit further right than the initial view, so scroll horizontally to reach them.
Days Remaining counts down to expiry. A commitment still running today reads 1 day rather than zero, an expired one reads 0 days, and a dash means no expiry date is known — which is not the same fact as expired.
Search, filter, choose columns and export to CSV or Excel from the controls above the table. You can also hide expired commitments to focus on what is still live.
Recommendations tab
Where the Commitment Manager proposes commitments worth buying. Each row gives the service, the recommendation, the potential savings per year, the current annual cost of the usage concerned, and how many resources are affected.
These figures are derived from your commitment settings, so changing the term, the payment option or the lookback window changes what this tab recommends.
Commitment settings
Commitment settings record the assumptions Stable should use when recommending a commitment, so that recommendations reflect how your organization actually buys. Open them with the Settings button next to the page title.
Terms: Whether you commit for 1 year or 3 years.
Payment options: All upfront, partial upfront, or no upfront.
Based on the past: The window of usage history a recommendation is computed from — 7, 30, or 60 days.
Target coverage: The share of your eligible usage you want covered by a commitment, as a whole percentage.
These are defaults applied to every commitment recommendation rather than per-commitment overrides. Set them once and adjust them whenever your buying strategy changes.
Changing commitment settings requires the Editor role or above. With the User role the Settings button is greyed out, with a tooltip inviting you to contact a manager in your organization — the rest of the page stays fully visible.
Why these figures differ from AWS Cost Explorer
Two differences are deliberate. Both exist so the figures answer the question you are actually asking when deciding what to buy next.
Eligible usage comes from what AWS actually sells. Stable measures your uncovered usage against AWS's published catalogue of usage a commitment can be bought for. Cost Explorer divides by everything you had running, including instance types and regions AWS sells no commitment for. The two denominators are different sets, so the percentages differ — in either direction, depending on your mix. Stable's figure answers "how much demand could I still commit?"; Cost Explorer's cannot, because part of what it counts as uncovered is usage no commitment is sold for.
Figures lag about two days. They are built from your AWS Cost and Usage Report, which AWS finalises with a delay, so the most recent hours are not plotted yet.
A gap in the chart means that day's data could not be read — not that your usage or your coverage was zero.