Beta

Reports The bill

Projected month vs AWS forecast

What AWS says this month will cost against qloudpulse's own projection, the gap between them over time, and AWS's range for each account. Two forecasts are better than one when they disagree.

What it shows

For each day, what that day said the month would cost, two ways: AWS Cost Explorer's spend so far plus its forecast for the rest of the month, and qloudpulse's own projection, the bill's whole days so far this month plus the last 24 hours' run rate for the hours left. Four figures head the page: AWS's forecast, our projection, ours minus AWS and what AWS says has been spent so far. Trends draw both projections over time and the difference between them; tables split both by account, and a last table shows AWS's own range, its low and high, for each account.

Both are amortized, and both leave out tax, credits and refunds. AWS forecasts each account on its own, so the total is the sum of the accounts.

Questions it answers

  • What will AWS cost this month, and do AWS and qloudpulse agree?
  • When did the two projections start to diverge, and which account caused it?
  • How wide is AWS's own range for the month, per account?

What it reads

Once a day qloudpulse asks AWS Cost Explorer what each account has spent so far this month and what it forecasts for the rest of it, and keeps the answer: AWS keeps no past forecasts, so a day with no run stays empty rather than being filled in later. The projection of our own is read at the same moment, from the bill and the run rate. Cost Explorer's API is one of the few calls qloudpulse makes that AWS charges for, about $0.35 per account a month, so it is off until one of your admins turns on AWS's month forecast under Options on the AWS accounts page; the pricing page says what the reads add to your bill.

What to do with it

When the two agree, either is a fair number for the month. When they diverge, the difference over time says when: a step in our projection and not in AWS's means something changed in the last 24 hours that AWS's trend has not caught up with, and the run rate has the detail. A step in AWS's and not in ours is usually a bill adjustment, a credit or a reservation. Check the account tables to see which account moved.

Related reports

  • AWS cost per day, bill and analysis: What AWS cost per day: the bill for each day it holds whole, the run rate after that.
  • AWS cost from the bill: The settled bill per day, with discounts and the Savings Plan, the month projected from it, and the cost by service and by line item type.
  • 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.