Inspect CloudFront request and transfer charges

Why this is worth a look

CloudFront pricing has multiple charging dimensions. AWS documents charges for HTTP or HTTPS requests and data transferred out from CloudFront edge locations, with pricing that varies by usage type, geography and feature selection. Real-time logs and invalidation paths can also be charged, while cache statistics show whether viewer requests are served at the edge or require CloudFront to get an object from the origin. Use the pricing page and billing records for the charge decision.

A read-only AWS console procedure to compare CloudFront billing dimensions, cache statistics and pricing-plan rules for one distribution and a defined UTC window.

Execution surface: AWS Management Console. Scope: one CloudFront distribution and one UTC reporting window in the last 60 days. Units: billing units and charges as displayed by AWS; request counts and report percentages; data units as displayed by AWS.

1. In Billing and Cost Management, inspect the Amazon CloudFront line items for the chosen billing period. Separate documented request, data-transfer, invalidation, real-time-log and other feature charges without assuming a field name or report schema.
2. In the CloudFront console, open Cache Statistics. Select the distribution, the same UTC date range, and All Locations or the relevant viewer continent. Review the documented total request, hit, miss, error, incomplete-download and HTTP-status statistics. Download the CSV when comparing periods.
3. Review cache behaviors and request policies. Record the query strings, cookies and headers used for forwarding or cache variation, and review TTL settings. Send proposed changes to the application owner for correctness review.
4. Identify whether the distribution uses pay-as-you-go or a flat-rate plan. For a flat-rate plan, compare usage with the published monthly allowance, included features and unsupported configurations. Each plan covers one distribution.
5. Compare billing and cache trends for the same UTC window. Treat cache misses as requests for which CloudFront must get the object from the origin, not as a direct charge calculation. Investigate unexplained feature or transfer lines against the applicable AWS pricing rules.

How to confirm it

1. 01

   Classify the billing dimensions

   Start with Amazon CloudFront billing records for the selected billing period. Separate documented request, edge data-transfer, invalidation, real-time-log and other feature charges, while retaining the usage labels and units AWS displays.

2. 02

   Match the report window

   Use Cache Statistics for one distribution, the same UTC window, and All Locations or a selected viewer continent. The report supports date ranges in the last 60 days, hourly points for ranges of 14 days or less, and occasional delays of up to 24 hours.

3. 03

   Review cache variation

   Check TTLs and the query strings, cookies and headers used for forwarding or cache variation. AWS says unnecessary value combinations can produce separate cached objects and more origin requests. Confirm application behavior before narrowing any policy.

4. 04

   Apply plan rules

   Pay-as-you-go pricing bills each service and feature on actual usage. Flat-rate plans combine specified services with published monthly allowances and no overage charges, cover one distribution, and exclude some configurations. Allowances are not hard limits, so sustained excess usage can lead AWS to use fewer or more distant edge locations or adjust performance until an upgrade restores full performance.

Primary sources