Beta

Reports Cost now

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. Compared with an hour, 8 hours, 24 hours or 7 days ago, with what went up and what went down.

What it shows

The headline is the cost of the current hour and how it moved against an hour, 8 hours, 24 hours and 7 days ago, with the services that went up and those that went down. Selecting an hour on the trend shows the whole page at that hour. The cost summary has the cost per hour, the month projected from it, the resources by cost with what each one is (an instance type, a volume's size, a database class) and a trend over time.

A flow from account to service to resource shows where the money goes. Bars by service, a donut by environment and a heatmap by hour of day close the page: the heatmap is where a nightly batch job or a dev environment left running over the weekend shows up at once.

It is a run rate, not the bill: no discounts, Savings Plans, credits or free tier. The figures are in US dollars at list price, excluding VAT. The settled days of the bill replace the run rate once the bill holds them, so the recent hours are the run rate and everything older is what AWS charged.

Questions it answers

  • What does AWS cost right now, this hour, and what does that make the month?
  • What changed since yesterday, or since last week, and in which service?
  • Which resources cost the most this hour, and in which account and environment do they run?
  • Did the change we deployed an hour ago raise the cost?

What it reads

Every hour qloudpulse reads what is running in each AWS account (instances, databases, caches, volumes, load balancers, NAT gateways, VPN and network connections, storage and more) in every region the account pays for, and how much of each was used that hour, as CloudWatch measures it. Each resource is priced at AWS's public list price from the AWS Price List, refreshed every morning. What no collector prices itself, such as data transfer, snapshots and requests, is carried from the bill's newest settled day, about two days old, spread evenly over its 24 hours.

The bill comes first: every day the AWS bill holds whole, usually all but the last one or two, shows the bill at amortized cost instead of the run rate, and a day changes over as soon as the bill has it. The run rate fills only the hours after, so expect a small step where the two meet. The run rate keeps 14 days of hours; days older than that, and older than 62 days, come from the bill as a day divided by 24.

What to do with it

Look at it after a deployment or a scaling change: the next hour tells you what it cost, a day before the bill does. Filter to an environment and compare it with 7 days ago to find what grew. A resource that should not be running goes to the savings recommendations; a resource you cannot explain has a ↗ that opens it in the AWS console, in the account that holds it. The Run rate vs bill report says how far this figure is from what the bill then charges.

Related reports

  • AWS run rate by account: Each account's hourly cost and how it moves, its share of the whole, and the services and resources inside the accounts you pick.
  • AWS run rate by service: Which services drive the hourly cost, which accounts each one runs in, and the resources behind it.
  • AWS cost, bill and analysis: One line for what AWS cost an hour: the bill for every day it holds whole, the run rate after that, so the latest hours are never empty.
  • Run rate vs bill: How far the run rate is from what the bill charged, per day, by service and by resource, so you know how far to trust the hourly figure.

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.