Beta

Reports Network

Network flows vs bill

How close the sampled flows' estimate is to what the bill charged, per day and per charge. A companion to the network flows report, so its figures come with a confidence.

What it shows

Two figures per day: the estimate from the sampled flows, scaled to the whole day, and the bill's cost for the same kind of traffic. A table by charge sets the two side by side for each kind: NAT gateway data processing, data transfer across availability zones, transit gateway data, VPC endpoint data, internet out. A trend draws the estimate and the bill over time.

Only days when every VPC seen was sampled at least 60 minutes are compared, and the bill lags about a day, so the newest day or two are not here yet. A charge far from the bill means the estimate for it cannot be trusted yet; a charge that tracks the bill means the connections behind it can be read as money.

Questions it answers

  • Is the network flows report's NAT gateway figure close to the bill, or is the sample too thin?
  • Which kind of data transfer does the sample estimate well, and which badly?
  • Has the estimate got closer to the bill as more days were sampled?

What it reads

Network traffic is sampled, not recorded in full: each VPC's traffic is recorded for 15 minutes at a time, then not for two to three hours, which gives about two hours of samples a day. The flow logs go to a bucket in your account and are read through the read-only role.

The cost those samples add up to, scaled to the whole day as in AWS network flows, is set beside what the AWS bill charged for the same kind of traffic that day, read once a day from the Cost and Usage Report export you connect.

What to do with it

Check it before acting on a network recommendation worth real money. If the charge the recommendation rests on tracks the bill, go ahead; if it is far off, wait for more sampled days, and look at Network flow coverage to see whether a VPC is being left out.

Related reports

  • AWS network flows: Which resources talk to which, how much, and what the traffic costs, from sampled VPC flow logs.
  • Network flow coverage: How many minutes of each VPC's traffic were sampled, per day.
  • 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.