USE CASE

Know exactly what your CloudFront origin is serving , and what it shouldn't be

CloudFront logs show cache hits. S3 access logs show origin requests. reCost combines both to give you the full picture , which variants are hot, which files are cold, and where your CDN is failing to cache.

Book a Demo
THE PROBLEM

CloudFront tells you hits. Not what's being served.

Your CDN cache hit rate looks fine. But underneath, you're serving image variants that haven't been accessed in months, storing originals in the wrong storage class, and missing cache warm patterns.

  • Unknown which resized image variants are actually being served
  • Files in Intelligent Tiering with zero access , paying for nothing
  • No visibility into origin request vs cache-served breakdown per file
  • Peak S3 origin load patterns invisible without per-object analysis
  • EOL FFmpeg or imaging library versions in production pipelines
WHAT RECOST DOES

Object-level CDN origin visibility

reCost reads your S3 access logs to reconstruct exactly what CloudFront is fetching from your origin , by file, by variant dimension, by content type, and by time of day.

  • Resized variant popularity by dimension (728x, 336x, 1200x, etc.)
  • Original vs derivative file access ratios
  • Cache miss rate , 200 (S3 served) vs 304 (CloudFront cached)
  • Files with zero GETs despite Intelligent Tiering cost
  • Peak CDN→S3 traffic hours for capacity planning
RELEVANT FEATURES

Media & CDN

Resized variant popularity, original vs derivative access patterns, peak CDN to S3 hours, cache miss rate analysis.

Storage Intelligence

Files in Intelligent Tiering with zero GETs. Data temperature per prefix. Bandwidth by content type.

IAM & Security

EOL SDK detection from media pipeline user agents, FFmpeg, imaging libraries, and legacy upload clients.

"68% of CloudFront origin requests were for image variants that hadn't been accessed in 90+ days. The cache was warming the wrong assets entirely."

Identified in a first scan. Origin egress costs dropped by 40% after cache key adjustments.

See exactly what's happening in your S3 data layer

Works with your existing AWS setup. Read-only access. No agents. No data exposure.

Book a Demo