// troubleshooting guide · aws cloudfront
Why Is My CloudFront Bill So High?
- Status
- Workaround available
- platforms:
- AWS Billing, Cost Explorer, CloudFront console
- updated:
- November 17, 2026
- reports:
- 5
- Method
- how we research
RUNBOOK · aws-cloudfront/bill-too-high5 FIXES
// quick answer
CloudFront bills grow from data transfer per GB, per-request fees, low cache hit ratios, invalidations past 1,000 paths, origin transfer to custom origins, WAF and Lambda@Edge. Break the bill down in Cost Explorer by usage type, fix caching, or move the distribution to a flat-rate plan.
Most likely fix: Find the cost driver
How to fix it
// try these in order, the most common fix is first
FIX 1Find the cost driver
- 01Open Billing > Cost Explorer
- 02Filter Service = CloudFront and group by Usage type
- 03Check the CloudFront console Reports & analytics > Popular objects and Top referrers
Did this fix it?FIX 2Move to a flat-rate plan
- 01Open the distribution and choose Pricing plan > Subscribe
- 02Pick Free, Pro ($15), Business ($200) or Premium ($1,000) based on your monthly GB and requests
- 03Disable unsupported features first (real-time logs, OAI, legacy cache settings, dedicated IP SSL)
- 04Note: accounts on the AWS Free Tier can't subscribe
Did this fix it?FIX 3Raise the cache hit ratio
- 01Use the CachingOptimized managed cache policy for static content
- 02Remove unneeded headers, cookies and query strings from the cache key
- 03Enable Origin Shield for multi-region traffic if origin load is high
Did this fix it?FIX 4Block abusive traffic
- 01Attach AWS WAF with rate-based rules and Bot Control
- 02Use signed URLs or referer checks for downloadable assets
- 03Set AWS Budgets alerts on CloudFront spend
Did this fix it?FIX 5Invalidate less
- 01Use versioned filenames for assets
- 02Invalidate /* (one path) instead of listing every file
Did this fix it?
Symptoms
Monthly AWS invoice shows large Amazon CloudFront charges, often for DataTransfer-Out-Bytes or Requests-Tier1/Tier2-HTTPS, sometimes in unexpected regions.
Why it happens
- C-01Traffic beyond the free 1 TB billed at $0.085/GB or more depending on region
- C-02Millions of small requests where request fees outweigh bandwidth
- C-03Low cache hit ratio sending most requests to the origin
- C-04Hotlinking, scrapers, bots or attacks inflating traffic
- C-05Invalidating many individual paths on every deploy
- C-06Real-time logs, Lambda@Edge, WAF or dedicated IP SSL ($600/month) enabled
// this guide also covers
- cloudfront bill too high
- cloudfront expensive
- reduce cloudfront costs
- cloudfront data transfer cost
Still not working?
If AWS CloudFront keeps failing, you're not alone. See every AWS CloudFront problem users report or the alternatives people switch to.
// We build software. Any software.
Paying for apps that don't quite fit? We build exactly what you need.
We're a small team of developers who build custom software fast. Not just tools like AWS CloudFront: web and mobile apps, games, desktop software, AI tools, internal tools: whatever you have in mind. 50+ custom products built for clients so far, and we run our own products too: booking platforms, games, learning apps. See our work
- Web apps & SaaS
- Mobile apps (iOS & Android)
- Games
- Desktop software
- AI tools & automations
- Internal tools & dashboards
- Client portals & booking
- Your own version of any tool
- ✓ Free 15-min call to scope it
- ✓ Price agreed up front
- ✓ Your data, your code
The same problem in other apps
All billing, cancellation & refunds guides →
How to Cancel Cloudflare Subscription (Pro, Business, Add-ons) (Cloudflare)
How to Cancel Fastly Account (Fastly)
Google Cloud Billing Account Suspended (Google Cloud)
How to Cancel Netlify Subscription (Netlify)
Other AWS CloudFront errors
- CloudFront 403 Access Denied With S3 Origin
- CloudFront 403 Error: The Request Could Not Be Satisfied
- CloudFront Invalidation Not Working (Still Serving Old Content)
- CloudFront CORS Error: No 'Access-Control-Allow-Origin' Header
- CloudFront SSL Certificate Not Showing (ACM us-east-1)
- CloudFront 502 Bad Gateway Error
- CloudFront 504 Gateway Timeout Error
- CloudFront React App 403/404 on Page Refresh