What it shows
One page a manager can read in a minute. At the top, the run rate projected to a month, how it compares with 24 hours and 7 days ago, and the accounts that moved it. Below that, what could still be saved a month and how many changes that is, what the changes made so far save, the open AWS Health issues and the scheduled changes coming up, and the number of findings the infrastructure rules fail on.
A table splits the same figures by account, so you can see which account carries the cost, which holds the savings and which has the open issues. A trend of the run rate over time, the services behind it and the largest savings close the page. Step the page back to any day of the last 13 months and the figures are what that day said.
On a phone it is slimmer still, for whoever runs the budget rather than the servers: the cost a month in one sentence, what could be saved, what has been saved, the changes worth most and where the money goes, then a button to the changes to make. The full page is one tap away.
Questions it answers
- What does AWS cost this month, at today's rate, across all accounts?
- How much could we save, and how much have we saved already?
- Is anything open on AWS Health that we should know about before the weekly meeting?
- Which account has the most failing infrastructure findings?
What it reads
Nothing is collected for this page on its own. Each day's figures come from the reports that have the detail: the run rate from AWS run-rate cost, the savings from AWS savings recommendations, the open issues and upcoming changes from AWS Health, and the failing findings from AWS infrastructure findings. Among the savings, untagged container images and images nobody pulls are upper bounds: priced by the images' sizes and capped at what the bill charged their repository for storage.
All of it reaches qloudpulse through the read-only IAM role you create in each account. Nothing is installed in your accounts and nothing is changed.
What to do with it
Open it on Monday. If the month's projection moved, follow the figure to the run-rate report and the service or account behind the change. If the savings figure is large, follow it to the recommendations and pick the first change. Share the link: it holds the view, so a colleague who opens it sees the same page, and the PDF download gives you a copy for the meeting.
Related reports
- AWS run-rate cost: What AWS costs an hour now, by account, service and environment, priced from what is running rather than read from a bill that arrives a day late.
- AWS savings recommendations: Changes that would cut the bill, priced per month, largest first, and what the changes made so far save.
- AWS Health: AWS's open issues, upcoming scheduled changes and notifications for every account, in one list, with what closed recently.
- AWS infrastructure findings: Unattached volumes, idle Elastic IPs and versions past support, by rule and by account, with the resources that fail.
The hosted plan has every report, and is free during early access: see pricing. Like every report, this one splits and filters by account, environment, service and resource, steps back 13 months, downloads as PDF and CSV and keeps the view in its link: what every report does. All reports.