What it shows
A sentence at the top: how many changes would save how much a month and a year, at list price, and what the changes made so far save. Under Actions needed, every recommendation grouped by kind, each resource with its account, environment and region, the change, why, and the saving a month. Where the change is one command, a preview command that only reads and an apply command are given; where it belongs in the code that owns the resource, or takes several steps, the page's notes give the steps, what to watch and the effort.
The kinds today: On-Demand EC2 or database usage that runs around the clock and is not under a Savings Plan, and steady databases to reserve; EKS clusters and ElastiCache engines in extended support; gp2 volumes to move to gp3; instances with a newer generation of the same size; managed databases that would cost less run on EC2; unattached volumes and idle Elastic IPs; idle load balancers, idle NAT gateways and idle transit gateway attachments; load balancers that could be shared; network paths that cost more than they need to, such as S3 or DynamoDB traffic through a NAT gateway, heavy downloads through NAT, traffic to your own public address, pods calling across availability zones and traffic to another region; container images nobody uses; S3 buckets in Standard-IA whose retrieval fees cost more than Standard would, and rarely read buckets in Standard that would cost less in Intelligent-Tiering, or, if almost never read, in Glacier Instant Retrieval; DynamoDB capacity above its use; CloudWatch alarms whose metric is gone or that tell nobody, log groups kept forever, busy log groups that would cost less in Infrequent Access, detailed monitoring on instances, and flow logs sent to CloudWatch Logs rather than S3; and API Gateway REST APIs that would cost less as HTTP APIs, stage caches nothing uses, and execution logs kept at INFO. A Done list keeps what was changed, with the saving it had on its last day. Bars by recommendation and by account and a trend of the saving over time close the page.
Questions it answers
- What should we change first to spend less on AWS, and what would it save a month?
- What does this idle NAT gateway, unattached volume or old-generation instance cost us for nothing?
- Should we buy a Savings Plan, and for how much an hour?
- What have the changes we made this quarter saved?
What it reads
Once a day, after the day's costs and inventory are read through the read-only role, qloudpulse looks for the changes above. Each is priced as a saving per month at list price: what the resource cost over the last seven days, against what it would cost after the change, from AWS's list prices, its published Savings Plan and reservation rates beside what the bill shows commitments already cover, CloudWatch usage, and the sampled network traffic. Container images are priced at the registry's storage price by their sizes, which count shared layers more than once, so each such figure is an upper bound, capped at what the bill charged the repository. A change counts as done once its recommendation is gone because the resource was changed or removed.
What to do with it
Take the top of the list. Run the preview command, which only reads, and then make the change in the Pulumi, Terraform or CloudFormation stack that owns the resource, or run the apply command where there is one. Every figure is at list price, before discounts and the Savings Plan, so the bill will show a little less than the page says. A Savings Plan or a reservation is a commitment: the page sizes it to what ran in every hour of the last 7 days, not the average, and it is a decision for a person. The AWS waste report sorts the same money by how easily it goes.
Related reports
- AWS waste: Money paid for what is not used, sorted by how easily it goes: unused, overprovisioned or stranded, by category and by service.
- AWS infrastructure findings: Unattached volumes, idle Elastic IPs and versions past support, by rule and by account, with the resources that fail.
- AWS network flows: Which resources talk to which, how much, and what the traffic costs, from sampled VPC flow logs.
- 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.
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.