Amazon CloudFront Origin
Does ZopNight manage Amazon CloudFront Origin?
A CloudFront origin drives 2 of the distribution's cost meters: every cache miss becomes an origin fetch that bills data transfer, and the distribution itself bills per GB out and per 10,000 HTTPS requests. ZopNight discovers origins and tracks distribution cost; its cache-hit and idle rules (RC-1511, RC-165) evaluate the distribution, not the origin.
Rules that fire on Amazon CloudFront Origin
No active rule family targets Amazon CloudFront Origin today. Rules that used to are retired, and retired rules publish no pages and fire no findings. Scheduling and permissions coverage are unaffected.
At a glance
| Field | Value |
|---|---|
| Scheduling notes | discovery, metrics, and cost tracking only; recommendations apply to the distribution. |
A CloudFront origin is the backend (S3 bucket, load balancer, or custom server) that a CloudFront distribution pulls content from. Origin configuration drives cache hit rates and origin-fetch data transfer, both of which shape CDN cost.
Where the CDN meters are
CloudFront bills the distribution, not the origin: per GB transferred out to viewers at rates that vary by geographic price class, plus per 10,000 HTTPS requests. The origin’s role in the bill is indirect and large: every cache miss triggers an origin fetch, and those fetches generate origin-side data transfer and backend load. A distribution with a poor cache hit ratio pays twice per object: once serving it from the edge and once pulling it from the origin again.
What origin configuration controls
Cache hit ratio is mostly a configuration outcome. Short or absent Cache-Control headers force revalidation; forwarding query strings, cookies, or headers that do not change the response fragments the cache so identical content is fetched repeatedly; and multiple distributions in front of one origin split what could be a shared cache. Each of these turns cacheable traffic into origin traffic.
The waste signatures
Two dominate. Distributions with a low cache hit ratio, where origin fetches (and the backend capacity serving them) do work the CDN was bought to absorb. And idle distributions still deployed in front of retired sites: the distribution has no hourly fee of its own, but the origin infrastructure behind it, typically a load balancer, keeps billing hourly while serving nothing but health checks.
How ZopNight sees origins
Origins are discovered through a dedicated CloudFront provider on the 6-hour cycle, because CloudFront is a global service rather than a regional one. CloudFront CloudWatch metrics run with a 90-day lookback and distribution cost is attributed from Cost Explorer or CUR 2.0. The cache-efficiency and unused-distribution rules (RC-1511 and RC-165) evaluate the distribution, not its origins, so their findings never appear on an origin. Origins cannot be scheduled; the levers are cache configuration and decommissioning.
Origins and cache statistics in the console
CloudFront console, then Distributions, then the distribution’s Origins tab. Cache statistics under Reports and analytics show the hit ratio the recommendations key on.