CloudFront cache observability

Know why your CloudFront cache misses
— and exactly how to fix it.

AWS shows you an overall hit-rate graph. cf-cache-monitor breaks it down by path and behavior, tells you why each request missed, and hands you concrete TTL & cache-policy fixes — from your access logs, read-only, never on your request path.

Read-only IAM role · No agent · No code on your edge · Set up in minutes

CloudFront tells you the score. Not how to win.

The built-in Cache Statistics report gives a single distribution-wide hit/miss percentage, and Popular Objects tops out at 50 URLs. Neither tells you which paths are bleeding, why they miss, or what to change. So teams hand-roll Athena queries — or fly blind.

The cache diagnostics AWS never built

📊

Hit rate by path & behavior

Per-path, per-cache-behavior hit rates — not one distribution-wide number. See exactly where offload is leaking.

🔍

Miss-reason analysis

True miss, origin error, and every CloudFront result-type state read straight from your logs — plus inferred cookie/encoding fragmentation and likely-uncacheable paths.

🛠️

Concrete recommendations

"Raise TTL on /assets/*, drop the session cookie from the key" — with estimated hit-rate and egress impact.

📉

Origin-offload & cost

Track origin-offload % and tie a low hit rate directly to the egress dollars it's costing you.

🧊

Cache result-type insight

Hit, Miss, RefreshHit, Error and redirect states — including revalidation effectiveness — the result types that actually explain your cache.

🔔

Alerts & weekly digest

Email/Slack alerts on hit-rate regressions, plus a weekly cache-efficiency digest so wins don't quietly erode.

How it works

1

Enable CloudFront logs

Point standard access logs at an S3 bucket you own. That's the only data we ever touch.

2

Grant a read-only role

Deploy our one-click CloudFormation stack — a least-privilege, read-only IAM role scoped to just that log bucket. Locked to our account with a unique ExternalId.

3

Get diagnostics & fixes

Analysis runs on a schedule (never on your request path). Within minutes your dashboard shows per-path hit rates, miss reasons, and prioritized recommendations.

🔒 Read-only, log-only 🚫 Never touches your origin or traffic 🇪🇺 In-region processing · IPs truncated by default 💤 Scale-to-zero · near-zero idle cost

Stop guessing at your hit rate.

Connect one distribution and see your first recommendations in minutes.

See pricing & start free