Interpreting your AWS bill and the AWS usage report for CloudFront
Your AWS bill for CloudFront includes codes and abbreviations that might not be immediately obvious. The first column in the following table lists items that appear in your bill and explains what each means.
In addition, you can get an AWS usage report for CloudFront that contains more detail than the AWS bill for CloudFront. The second column in the table lists items that appear in the usage report and shows the correlation between bill items and usage report items.
Most codes in both columns include a two-letter abbreviation that indicates the location of
the activity. In the following table, region
in a code is
replaced in your AWS bill and in the usage report by one of the following two-letter
abbreviations:
AP: Hong Kong, Philippines, South Korea, Taiwan, and Singapore (Asia Pacific)
AU: Australia
CA: Canada
EU: Europe and Israel
IN: India
JP: Japan
ME: Middle East
SA: South America
US: United States
ZA: South Africa
For more information about pricing by region, see Amazon CloudFront Pricing
Note
This table doesn't include charges for transferring your objects from an Amazon S3 bucket to CloudFront edge locations. These charges, if any, appear in the AWS Data Transfer portion of your AWS bill.
Items in your CloudFront bill | Values in the usage type column in the CloudFront usage report |
---|---|
Total bytes served from CloudFront edge locations in |
Bytes served via HTTP for objects with TTL ≥ 3,600 seconds.
Bytes served via HTTPS for objects with TTL ≥ 3,600 seconds.
Bytes served via HTTP for objects with TTL < 3,600 seconds.
Bytes served via HTTPS for objects with TTL < 3,600 seconds.
Bytes returned from CloudFront to viewers via HTTP in response to
Bytes returned from CloudFront to viewers via HTTPS in response to
|
Total bytes transferred from CloudFront edge locations to your origin or edge function in response to
|
Total bytes transferred via HTTP from CloudFront edge locations to your origin or edge function in response to
Total bytes transferred via HTTPS from CloudFront edge locations to your origin or edge function in response to
|
Number of HTTP |
Number of HTTP
Number of HTTP |
Number of HTTPS |
Number of HTTPS
Number of HTTPS |
Number of HTTP Also includes the number of HTTP WebSocket
requests ( |
Same as the corresponding item in your CloudFront bill. |
Number of HTTPS Also includes the number of HTTPS WebSocket
requests ( |
Same as the corresponding item in your CloudFront bill. |
Number of HTTPS |
Same as the corresponding item in your CloudFront bill. |
Total bytes transferred from the origin to any regional edge cache, including the regional edge cache that is enabled as Origin Shield. |
Total bytes transferred from the origin to any regional edge cache, including the regional edge cache that is enabled as Origin Shield. |
Total bytes transferred to the origin from any regional edge cache, including the regional edge cache that is enabled as Origin Shield. |
Total bytes transferred to the origin from any regional edge cache, including the regional edge cache that is enabled as Origin Shield. |
Number of requests that go to Origin Shield as an incremental layer. For dynamic (non-cacheable) requests that are proxied to the origin, Origin Shield is always an incremental layer. For cacheable requests, Origin Shield is sometimes an incremental layer. For more information, see Estimating Origin Shield costs. |
Number of requests that go to Origin Shield as an incremental layer. For dynamic (non-cacheable) requests that are proxied to the origin, Origin Shield is always an incremental layer. For cacheable requests, Origin Shield is sometimes an incremental layer. For more information, see Estimating Origin Shield costs. |
Invalidations The charge for invalidating objects (removing the objects from CloudFront edge locations); for more information, see Paying for file invalidation. |
Invalidations Same as the corresponding item in your CloudFront bill. |
SSL-Cert-Custom The charge for using an SSL certificate with a CloudFront alternate domain name such as example.com instead of using the default CloudFront SSL certificate and the domain name that CloudFront assigned to your distribution. |
SSL-Cert-Custom Same as the corresponding item in your CloudFront bill. |