Use this page to:
See whether a commitment is worth it for you - the Eligible Consumption block splits your recent spend into the part a commitment can apply to and the part it cannot.
Check what your existing commitments return - the Your compute savings block plots the price you pay after discounts next to the savings those discounts produced.
Track how much of your usage is covered - the Your compute coverage block plots your consumption against the part of it covered by Reserved Instances and Savings Plans.
Decide where to go next - a low coverage figure sends you to Purchase Analyzer to size a purchase, and a high one sends you to Detailed to check that what you hold is being used.
The Dashboard is read-only. Nothing on this page changes your commitments, and purchasing is done in the AWS Console.
Accessing the Dashboard tab
Open Reservation from the left-hand menu.
Select the Dashboard tab.
The page loads the three blocks for the accounts currently selected at the top of the page.
Reservation analyses AWS commitments, so the two blocks built from AWS billing data appear for a scope that contains AWS accounts. You need view permission for Reservation to open the page;
Selecting accounts (scope)
The account selector at the top of the page sets the scope for all three blocks. It lists the accounts connected to Uniskai, grouped by cloud provider, with the number of accounts in each group beside the provider name.
A whole provider - tick the provider group to take every selectable account in it at once.
Individual accounts - tick accounts one by one; a selection can mix providers.
Use Select All and Reset inside the selector, or type in the field to filter the list by name. Selected accounts appear as chips, and when there are more than the field can show the remaining ones are collapsed into a counter.
A greyed out account is not available for selection. An account carrying a warning icon can be selected but has a problem with its data connection; hover the icon to see the reason.
This selector belongs to the Dashboard alone. The other Reservation tabs have their own scope controls, and a scope you set here does not carry over to them.
Eligible Consumption
This block splits your recent spend into the part a commitment can be applied to and the part it cannot. Based on the last 30 days under the title states the window; this block always describes the last 30 days.
The bar spreads that spend across a scale from 0 to 100 percent with a segment per category, and the four tiles below give the same split as amounts:
Tile | What it shows |
Consumption Eligible For Commitments | Your EC2 instance spend. This is the figure to bring to Purchase Analyzer, because it is what the recommendations are sized against. |
Spots | Spend on Spot Instances. Spot pricing is already discounted and cannot be covered by a commitment. |
Compute (Lambda, Fargate) | |
Not Compute Services | Everything else in the selected scope, such as databases, storage and networking. |
The four tiles add up to the total the bar describes. A category with no spend draws no segment, and a category with a very small share draws a segment too narrow to carry its label, so the tiles are the reliable place to read every value.
A large eligible share means a commitment has plenty to work with. A small one means most of your bill sits in Spot usage or in services outside compute, so a commitment will move your total less than the headline discount rates suggest.
Your compute savings
This block shows what the commitments you already hold are returning, over two ranges. Monthly gives one bar per month across your entire available history, which is where a trend shows. Hourly gives the recent detail, which is where a change in usage pattern shows.
Series | What it shows |
Price After Saving | What you actually paid for that period after the discount from your commitments was applied. |
Own Savings | The difference between the on-demand price of that usage and what you paid. |
Estimated Price After Saving | The price the platform expects for a period that has not finished yet. |
Own Estimated Savings | The savings the platform expects for a period that has not finished yet. |
The two Estimated series exist because the current period is still running, so their values are a projection and can still move. The finished periods beside them will not.
The height of a bar is what the usage would have cost at on-demand rates, and the Own Savings part of it is what the commitment kept back. Savings that grow while the bar height stays flat mean your coverage improved; savings that fall while it stays flat usually mean a commitment expired or your usage moved to instance types the commitment does not cover.
Hover any point to open a tooltip for that period. It shows the period, a Total price, and one row per series present in that period.
Total price is the sum of the rows below it, so on a period with savings it equals Price After Saving plus Own Savings. That total is what the usage would have cost without your commitments. A period with no savings lists Price After Saving alone, and Total price equals it.
Total price is the sum of the rows below it, so on a period with savings it equals Price After Saving plus Own Savings. That total is what the usage would have cost without your commitments.
A period with no savings lists only Price After Saving, and Total price equals it. The savings row is left out rather than shown as a zero.
Your compute coverage
Savings tell you what you gained. Coverage tells you how much of your usage a commitment reached in the first place. Both charts use the same Monthly and Hourly ranges as the savings block, so the two can be read side by side.
Series | What it shows |
Consumption | Your usage for that period, priced without commitment discounts. |
RI Coverage | The part of that usage covered by Reserved Instances. |
SP Coverage | The part of that usage covered by Savings Plans. |
Consumption Estimated, RI Coverage Estimated, SP Coverage Estimated | The same three series for a period that has not finished yet. |
Coverage never exceeds consumption for the same period. A period returned without coverage is plotted as absent rather than as a zero, so a gap in a coverage line means there was no coverage then.
The distance between the consumption line and the coverage lines is unused opportunity: usage running at on-demand rates that a commitment could have discounted. Take the size of that gap to Purchase Analyzer and let it size a commitment for it. Coverage that tracks consumption closely means you are already well covered, and the next question is whether what you hold is fully used, which Reservation Detailed answers.
The coverage tooltip lists Consumption and then only the coverage types present in that period, so a month covered by a Reserved Instance and not by a Savings Plan shows an RI Coverage row and no SP Coverage row.
How the two blocks relate
The two blocks describe the same usage from two angles, and their tooltips line up for the same period:
Consumption in the coverage tooltip is the same figure as Total price in the savings tooltip. Both are what the usage would have cost at on-demand rates.
RI Coverage and SP Coverage tell you how much of that usage a commitment applied to.
Own Savings in the savings tooltip tells you how much money that application actually saved.
So coverage is measured in usage reached, and savings is measured in money kept. A large coverage figure with a small saving means the commitment is reaching your usage but at a shallow discount.







