Beta

Reports Cost now

AWS run rate by service

Which services drive the hourly cost, which accounts each one runs in, and the resources behind it. The page to open when the question is "why is EC2 so much" or "what are we paying NAT gateways for".

What it shows

The services by cost, with each one's cost per hour, the month projected from it and the change over 7 days. A trend over time draws one line per service, bars put the services side by side and a donut shows each one's share. Select a service and the rest of the page filters to it: the accounts it runs in, the resources behind it with their type, size, usage and unit price, and a heatmap of the hour of day.

A service here is what AWS calls one: EC2, RDS, ElastiCache, EKS, Elastic Load Balancing, NAT gateways under VPC, S3, CloudWatch and so on. The resource rows name the thing itself, with a ↗ to it in the AWS console. Tick Bill (CUR) to see what the bill charged each service for its usage per hour, Savings Plan discounts included, beside the run rate.

Questions it answers

  • Which AWS service costs the most an hour, and is it growing?
  • What do NAT gateways, load balancers or EKS control planes cost us across all accounts?
  • Which instances make up the EC2 cost, and in which accounts?
  • What is the cost of RDS per hour, and which databases carry it?

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

Start with the largest service and open its resources. The ones that are oversized, idle or on an older generation are also on the savings recommendations, priced as a saving a month. A service whose heatmap is flat around the clock in a dev environment is a schedule waiting to be set. For data transfer, which the run rate carries from the bill, the network flows report shows which resources talk to which and what the path costs.

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 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 savings recommendations: Changes that would cut the bill, priced per month, largest first, and what the changes made so far save.
  • AWS waste: Money paid for what is not used, sorted by how easily it goes: unused, overprovisioned or stranded, by category and by service.

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.