Investigate AWS Network Costs

Status: CloudBurn Platform has not launched publicly yet. Join the waitlist.

AWS Network Costs helps you investigate billed network charges and identify which services, Regions, or resources account for an increase.

Prerequisites

• A connected AWS account with working role access and results storage
• A Pro or Enterprise plan: see Plans and billing

Detailed billing adds resource IDs and reported transfer Regions from CUR 2.0. Cost Explorer is used when imported billing data is unavailable or does not cover the comparison.

Trace a cost increase

1. Open AWS Network Costs under Cost analysis and choose an AWS account.
2. Group billed sources by Service, Region, or Resource when available.
3. Choose Compare to compare the last 7, 14, or 30 days with the same number of preceding days.
4. Choose Spend to size connections by billed cost, or Increase to size them by growth. Charges that fell contribute nothing to Increase mode.
5. Select a node or connection to inspect current and previous cost, the change, billed quantities, and attribution. Follow its connections to investigate the billed sources behind it.

Billing shows where a charge was billed. The graph does not show the actual traffic path or identify the workload that caused it. Unattributed charges remain in totals; an increase is not a savings estimate.

Check billing coverage

The Billing data panel shows the source, freshness, coverage, and detailed billing status. The first CUR 2.0 delivery can take up to 24 hours. Until both periods are covered, comparisons can use Cost Explorer; missing history is not zero spend.

If a comparison is marked provisional, AWS may still add or revise charges. If no billing source covers it, try a shorter comparison. Follow the panel's guidance to update the connection or address an unhealthy billing export.

What's next