Help us improve the AWS re:Post Knowledge Center by sharing your feedback in a brief survey. Your input can influence how we create and update our content to better support your AWS journey.
Calculating the Natgateway DataTransfer-Out costs down to instance or tag level
IHAC who have ec2 nodes tagged. When they send traffic out to the Internet from these nodes, they can see that traffic (DataTransfer-Out-Bytes) in the aggregate outbound reporting, but the traffic outbound to the Internet passes through a NAT gateway (for example, nat-XXXXXX). Passing through the NAT gateway, the tagging attribution is lost. Consequently, when they use cost explorer and filter on Tag and Usage type: DataTransfer-Out-Bytes, they get nothing. Is there a solution for this, so that they can correctly attribute data transfer out costs from natgateway by product or tag.
- Language
- English
- Newest
- Most votes
- Most comments
Not exactly, what you are looking for but throwing alternate approach to find data transfer Bytes for individual hosts by querying the data.
https://aws.amazon.com/premiumsupport/knowledge-center/vpc-find-traffic-sources-nat-gateway/ https://aws.amazon.com/premiumsupport/knowledge-center/cloudwatch-vpc-flow-logs/ https://aws.amazon.com/premiumsupport/knowledge-center/vpc-flow-logs-and-cloudwatch-logs-insights/ https://aws.amazon.com/about-aws/whats-new/2021/04/amazon-vpc-flow-logs-announces-out-of-box-integration-with-amazon-athena/
Relevant content
- asked 2 years ago
- AWS OFFICIALUpdated 4 months ago
