Data Transfer charges across AWS Regions
A customer is getting charged for data transfer ($700/month) from US-East to US-West. I verified with them and they don't have any cross region replication setup for S3, no snapshots, no RDS read replicas, 5 tiny EBS snapshots in US-West. What could be the other reasons that may cause data egress charges? any thoughts or comments?
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
With Cost Explorer, customers can now find the cause themselves, before reaching out to support.
Within Cost Explorer, use the Filter of Usage Type as 'DataTransfer-Out-Bytes (GB)'. It is avaialble for each region and this usage type is prefixed with region's 3 alphabet alias like 'USW2' (i.e. US West-2) etc.
After the correct UsageType is selected, chose the GroupBy as 'Service', this will show the DataTransferOut cost originating from each service, helping understand the cause of the issue. There is additional filter of 'API Operation' available, if the customer wants to see which specific API operation within a service caused that DataTransferOut.
Cost Explorer provides date range window to narrow down on different date ranges.
Hope it helps.
Relevanter Inhalt
AWS OFFICIALAktualisiert vor 5 Monaten- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor 3 Jahren