AWS bill line item
US-DataTransfer-Out-Bytes
You are being charged per gigabyte for content CloudFront serves from its edge locations to end users, plus a per-10,000-requests charge, with rates varying by the edge-location group (US, EU, AP, and so on) that served the request.
CloudFront data transfer and requests
Verified against official AWS documentation last checked
Why it shows up
This looks similar to plain internet egress on the bill but is a distinct, usually cheaper, product line keyed off the edge location that answered the request rather than the origin's AWS region. The prefix here is a broad geography code, not the fine-grained region codes used elsewhere.
Costs climb with cache-miss rate (uncacheable or short-TTL dynamic content forces more origin fetches), high request-per-second traffic from bots or scrapers, and serving traffic from higher-cost edge-location groups rather than cheaper tiers.
How to cut it
- Increase cache hit ratio with longer TTLs and cache keys that don't over-fragment the cache.
- Use a price-class restriction to serve only from lower-cost edge-location regions if global reach isn't required.
- Enable compression and right-size assets at origin to reduce bytes served per request.
- Separate cacheable GET/HEAD traffic from proxied write traffic in your monitoring, since proxied requests to origin can't benefit from caching.
How to read a usage type
US-DataTransfer-Out-Bytes carries no region or direction token, so there's nothing to break down here.
Source
Source: AWS docs →Found US-DataTransfer-Out-Bytes on your own bill?
Drop your Cost Explorer CSV into the AWS Bill Analyzer. It'll flag line items like this one on your own bill and link straight back to the fix.
Analyze your own bill →The meter you don't watch still grows.
Waste rarely hides in the service you check every week. CostMon watches every meter on your stack, including the ones you forgot were running.