Beta

Reports Network

AWS network flows

Which resources talk to which, how much, and what the traffic costs, from sampled VPC flow logs. The data transfer line on the bill, with names on it.

What it shows

The cost per day of the traffic, the month projected from it and the GiB per day. A flow from the type of resource that sends, through the path the traffic takes, to the type that receives shows how the resources connect by volume. Under Connections, every pair by cost, with the GiB, the VPC and the availability zones at each end; bars by path, a donut by environment and a trend by path over time. The paths priced: across availability zones, through a NAT gateway, over a transit gateway, through a VPC endpoint, and out to the internet. Hourly charges, such as the NAT gateway or load balancer itself, are not here; they are in the run rate. This report prices the data.

An estimate: each VPC is sampled about 10% of the day and scaled up, so one day can be off while a week is close. A VPC sampled under 60 minutes on a day is left out of it; Network flow coverage says which, and Network flows vs bill says how close the estimate comes to what AWS charged.

Questions it answers

  • What is our NAT gateway data processing cost, and which resources send the traffic through it?
  • Which services talk across availability zones, and what does that cost a month?
  • Where does our internet egress come from?
  • Would a VPC endpoint for S3 or DynamoDB pay for itself?

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.

Each day's samples are scaled up to the whole day, per VPC. Every address is matched to the resource behind it from the accounts' network setup, as read by the inventory, and the traffic is priced at AWS's list price per GB for the path it takes. A resource gone before the hourly read of the network interfaces shows as its subnet.

What to do with it

Sort the connections by cost. Traffic to S3 or DynamoDB through a NAT gateway wants a gateway endpoint, which is free; a heavy download through NAT wants a NAT instance or a different route; pods calling across availability zones want topology-aware routing. Each of those is a recommendation on AWS savings recommendations, priced from this report's traffic, with the steps.

Related reports

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.