AWS CloudFront Not Working? Common Errors & Fixes
The 12 AWS CloudFront problems users hit most often, why they happen, and the fixes that actually work — collected from user reports, forums, and official support docs.
CloudFront 403 Access Denied With S3 Origin
Workaround availableAWS Console, AWS CLI, Terraform, CloudFormationCloudFront returns 403 AccessDenied when S3 refuses its request: usually a missing OAC bucket policy, the S3 website endpoint used with OAC, no default root object, or a file that doesn't exist. Fix the bucket policy for your distribution ARN and use the S3 REST endpoint.
CloudFront 403 Error: The Request Could Not Be Satisfied
Workaround availableAll browsers, AWS ConsoleThis CloudFront-generated 403 page usually means the hostname isn't listed as an alternate domain name on the distribution, the viewer used HTTP where only HTTPS is allowed, or WAF/geo restriction blocked the request. Add the CNAME with a matching certificate and check the security rules.
CloudFront Invalidation Not Working (Still Serving Old Content)
Workaround availableAWS Console, AWS CLI, CI/CDIf CloudFront still serves old files after an invalidation, the path probably didn't match the cached object, the invalidation hasn't finished, the browser cached the file, or the origin itself still has the old version. Check x-cache/age headers and invalidate /* or use versioned filenames.
CloudFront CORS Error: No 'Access-Control-Allow-Origin' Header
Workaround availableChrome, Firefox, Safari, AWS ConsoleCORS fails behind CloudFront when the Origin header isn't forwarded or isn't part of the cache key, or when the origin's own CORS header overrides yours. Attach a CORS response headers policy (or forward Origin with CORS-S3Origin/CORS-CustomOrigin) and allow OPTIONS.
CloudFront SSL Certificate Not Showing (ACM us-east-1)
Workaround availableAWS Console, Terraform, CloudFormationCloudFront only lists ACM certificates from us-east-1 (N. Virginia), and only ones whose names cover your alternate domain names. Request the certificate in us-east-1 with every hostname (apex and www) and validate it via DNS.
CloudFront 502 Bad Gateway Error
Workaround availableAWS Console, custom origins (EC2, ALB, external servers)CloudFront returns 502 when it can't complete a valid connection to your origin: most often the origin's TLS certificate doesn't match the origin domain, is expired, self-signed or missing intermediates, or the origin DNS doesn't resolve. Fix the certificate or the Host header forwarding.
CloudFront 504 Gateway Timeout Error
Workaround availableAWS Console, EC2, ALB, API originsA 504 means the origin didn't connect or respond in time: by default CloudFront tries 3 connections of 10 seconds each and waits 30 seconds for a response. Open the origin firewall to CloudFront, speed up the endpoint, then raise the origin response timeout if needed.
CloudFront React App 403/404 on Page Refresh
Workaround availableReact, Vue, Angular, Next.js static exportRefreshing a client-side route (like /dashboard) on an S3 + CloudFront SPA returns 403 because no S3 object exists at that path. Map 403 and 404 to /index.html with status 200, or rewrite routes with a CloudFront Function.
Why Is My CloudFront Bill So High?
Workaround availableAWS Billing, Cost Explorer, CloudFront consoleCloudFront 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.
CloudFront Error: Your Account Must Be Verified
OngoingAWS Console, CDK, Amplify, TerraformNew AWS accounts often get 'Your account must be verified before you can add new CloudFront resources' when creating a distribution. Nothing in CloudFront fixes it: open an Account and billing support case asking to verify the account for CloudFront.
CloudFront CNAMEAlreadyExists Error
Workaround availableAWS Console, AWS CLICNAMEAlreadyExists means another distribution (possibly in another AWS account) already uses that alternate domain name. Remove it from the old distribution, move it with a wildcard or the AssociateAlias API, or ask AWS Support for apex domains you can't access.
How to Cancel AWS CloudFront (Stop Charges)
Workaround availableAWS Console, AWS CLITo stop CloudFront charges, cancel any flat-rate pricing plan on the distribution, then disable and delete the distribution. Paid plans keep their price until the end of the billing cycle, and a disabled distribution on a plan is still billed.
Problem not listed? See all AWS CloudFront complaints or compare AWS CloudFront alternatives.
// We build software. Any software.
Have an idea for an app? We'll build it.
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