CloudFront Low Cache Hit Ratio
Every miss is fetched from the origin and billed as origin transfer as well as CloudFront transfer, so a low hit ratio pays for the same bytes twice.
Free to start. No card. The playground just needs your work email.
AWS
Found, explained, fixed.
Findings with a dollar figure attached, idle, oversized, orphaned, unscheduled and undiscounted spend.
Detect
ZopNight checks this automatically across AWS, with read-only access to the account.
Explain
Every finding says exactly what to change: Improve the CloudFront cache hit ratio. Where the saving can be proven it is priced; where it cannot, the finding says so.
Fix
After a guided review, where you confirm the change, ZopNight applies a lifecycle policy, then checks the change took.
- Applies to
- CloudFront Distributions on AWS
- The fix, by hand
- Review cache behaviors and increase TTL values where possible.
- Normalize query strings and headers in cache key settings.
- Use Origin Shield to reduce origin requests.
- Enable compression (gzip/Brotli) to reduce data transfer.
ZopNight does this for you after a guided review.
- Category
- Rightsizing. Resources sized for headroom they never use. A smaller size runs the same workload for less.
- Where it appears
- The Savings tab of Recommendations, with every affected resource listed.
- Rule ID
RC-1511- Full reference
Related checks
See the oversized resources in your account.
Connect a read-only role and the first pass runs on your own estate. This check, and the rest of the catalogue, with it.
Prefer to talk it through first? Book 20 minutes with the team.
- $30M+annualised cloud spend under management
- 550K+resources tracked since launch
- 20-60%off the bill in the first month
- SOC 2Type II report, plus ISO 27001
Figures published on zop.dev.