Using AWS Transit Gateway Flow Logs to chargeback data processing costs in a multi-account environment
Networking & Content Delivery Blog
This article explains how to use AWS Transit Gateway Flow Logs to chargeback data processing costs in a multi-account environment.
Specifically, the article covers:
- Prerequisites: Enabling Transit Gateway Flow Logs and setting up AWS Cost and Usage Reports
- Steps to get the AWS Transit Gateway data processing charge per account, including calculating total network traffic, costs, and allocating costs proportionally to spoke accounts
- Extending the approach to chargeback for other shared network services like NAT Gateway, Gateway Load Balancer, or VPC endpoints
- Cleanup steps to prevent unwanted charges
The AWS News Feed is currently looking for gold sponsors. If you want to support the AWS community and reach a large audience of AWS professionals, consider sponsoring the AWS News Feed.
Related articles
Jan 8
2025
2025
Analyzing AWS Transit Gateway Data Processing charges with cost allocation tags
Apr 1
2025
2025
Monitor AWS Transit Gateway Flow Logs centrally using Amazon Managed Grafana
Feb 17
2026
2026
Reduce unexpected AWS costs: Tracing AWS billing charges with log correlation techniques
Apr 26
2023
2023
Best practices and considerations to migrate from VPC Peering to AWS Transit Gateway
The AWS News Feed is currently looking for silver sponsors. If you want to support the AWS community and reach a large audience of AWS professionals, consider sponsoring the AWS News Feed.