Use this page to:
Check whether a commitment is being used - the utilization and unused commitment columns show what you are paying for and not consuming.
See where coverage sits and where it does not - the coverage columns show how much of each specification is running under a commitment.
Find out where a saving came from - the tree attributes savings down to the instance type, region, tenancy and platform.
Tell your own commitments from shared and reseller ones - each metric is reported separately for the three sources.
Take the numbers away - the whole tree exports to a spreadsheet.
The other Reservation tabs look forward and ask what to buy. This one looks back and asks how well what you already bought is performing.
The Detailed tab is read-only.
Accessing the Detailed tab
Open Reservation from the left-hand menu.
Select the Detailed tab.
The page loads the three cards and the tree for the accounts currently selected at the top of the page.
The Detailed tab supports AWS accounts only. You need view permission for Reservation to open it.
Selecting accounts (scope)
The controls at the top of the page pick the organization and how much of it to include.
Whole Org - the page covers every account linked to the organization.
Account - choose accounts yourself; the selected ones appear as chips, and when there are more than the field can show the remaining ones are collapsed into a counter.
Use Select All and Reset inside the selector to adjust the selection quickly.
The three cards
Card | What it shows |
Savings | The net saving your commitments produced over the last 30 days. |
Overall Utilization | How much of the commitments you hold your usage actually consumed, with the number of commitments beside it. |
Overall Coverage | How much of your consumption ran under a commitment. |
The cards describe your whole selected scope, while each row of the table describes its own branch. That is why Overall Coverage is usually lower than the coverage percentage on the first row: the card divides by all consumption in scope, including services that carry no commitments at all, while the row divides only by its own branch. The two are not meant to match.
Details By Specification
The table is a tree. The top level groups the services that share a commitment type, the levels below break that group down until each row is one exact specification.
For compute the tree goes four levels deep:
All Compute - the group
Amazon EC2 - the service
t3a | eu-central-1 - the instance family in a region
t3a.medium | eu-central-1 | Shared | Linux/UNIX - the exact specification
Not every branch reaches four levels. A group that holds a single service breaks straight down to its usage rows, so the depth depends on how much there is to break down. The set of top level groups follows your data: a group appears when the selected scope has consumption in it.
A row expands with the plus control beside its label and collapses with the minus. The deepest rows have no control, because there is nothing further to break down.
Own, Reseller and Shared
Nine of the columns come in three variants, because a commitment reaching your usage can come from three places:
Own - commitments that belong to the accounts in your selected scope.
Shared - commitments that belong elsewhere in the organisation and reach your usage through sharing.
Reseller - commitments obtained through a reseller.
A column reads a hyphen when that source holds nothing for the row, which is why a scope with only its own commitments shows hyphens down the whole Reseller and Shared side of the table.
The columns
Column | What it shows |
Type & Specification | The group, service, family or exact specification the row describes. |
Consumption (w/o discount) | What the usage on that row would cost at on-demand rates, before any commitment discount. Hover a value for its full precision. |
Own Commitments Utilization | How much of the commitments held on that row your usage consumed, as a percentage with a bar. |
Own / Reseller / Shared Commitments Count | How many commitments of each source apply to the row, split into Reserved Instances and Savings Plans. |
Own / Reseller / Shared Commitments Coverage | How much of the row’s consumption each source covered, in currency, with a percentage chip. |
Net Savings | What the commitments on that row saved, after the cost of any commitment that went unused. |
Own RI Unused Coverage | The on-demand value of the coverage an unused Reserved Instance would have provided. |
Own RI Unrealized Savings | The saving that unused coverage would have produced. |
Own RI Unused Commitments | What you paid for Reserved Instance capacity that your usage did not consume. |
Own SP Unused Commitment | What you paid for Savings Plan commitment that your usage did not consume. |
Waste is reported in three columns for Reserved Instances and in one for Savings Plans.
How the numbers relate
Four relationships hold across the table and are worth knowing, because each of them explains a figure that looks wrong at first glance.
Consumption and coverage add up down the tree. A family row equals the sum of its specification rows, and a service row equals the sum of its family rows. If you expand a branch and add up the children, you get the parent.
The coverage percentage is the row’s own ratio, not an average. It is the coverage amount divided by the consumption on the same row. A parent row is therefore not the average of its children’s percentages; it is the ratio of the summed amounts, which is why a parent can sit outside the range its children span.
Commitments belong to a level, and they are not pushed down. A Savings Plan bought for compute in general belongs to the group row, not to any one service, so the group can report Savings Plans that none of its children report, and a high utilization on the group can sit above a zero on a child that holds only a fully unused reservation. Those are not broken sums; they say where the commitment lives.
A row’s waste explains its own savings. For a Reserved Instance that went entirely unused, the unrealized savings equal the unused coverage minus the unused commitment, and the net saving on that row is the unused commitment as a loss. A commitment paid for and never used costs exactly what it cost.
Sorting
Every column has a sort control. Clicking it once sorts ascending, again descending, and a third time removes the sort and returns the rows to the order they loaded in.
Sorting works inside each level of the tree rather than across the whole table, so children stay under their own parent and the hierarchy is never flattened. Only one column can be sorted at a time; sorting a second column releases the first. Rows whose value is a hyphen are treated as the lowest value, so they group at the start when sorting ascending and at the end when sorting descending. Sorting is dropped when the page reloads.
Customizing columns
Click the columns icon above the top-right corner of the table to choose which columns are displayed.
Type & Specification, Consumption (w/o discount) and Net Savings are always shown and cannot be removed.
Click Select All to display every available column, or Reset to return to the mandatory set.
Click Save to apply your selection, or Cancel to discard it.
Note: your column selection is stored against your account, so it survives a refresh and is still there the next time you open the tab.
Exporting the report
Save To Excel downloads the tree as a spreadsheet.
The export is not a copy of what is on screen. It uses its own schema, and there are three differences worth expecting:
Every level is included, regardless of what you had expanded. The file describes the whole tree, and a Level column carries the depth as a number from one to four in place of the indentation.
The columns are split further than in the table. Each combined count cell becomes a separate column per commitment type, and the file adds the total commitment amounts for Savings Plans and Reserved Instances, which the table does not show at all.
Empty cells are written as zero. Where the table draws a hyphen, the file carries a numeric zero, so read the count and total commitment columns to tell an absent commitment from a measured zero.
The file also carries one more decimal place than the table in places, so a figure can differ from the screen in the last digit.