// troubleshooting guide · aws cloudfront
CloudFront 403 Error: The Request Could Not Be Satisfied
- Status
- Workaround available
- platforms:
- All browsers, AWS Console
- updated:
- November 17, 2026
- reports:
- 5
- Method
- how we research
RUNBOOK · aws-cloudfront/403-request-could-not-be-satisfied4 FIXES
// quick answer
This 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.
Most likely fix: Add the alternate domain name
How to fix it
// try these in order, the most common fix is first
FIX 1Add the alternate domain name
- 01Open the distribution > General > Settings > Edit
- 02Under Alternate domain name (CNAME) add the exact hostname, including www if used
- 03Select a custom SSL certificate from us-east-1 that covers that name
- 04Save and wait for the status to show the new deployment finished
Did this fix it?FIX 2Fix the viewer protocol policy
- 01Open Behaviors > select the behavior > Edit
- 02Set Viewer protocol policy to Redirect HTTP to HTTPS instead of HTTPS only
- 03Save changes
Did this fix it?FIX 3Check WAF and geo restrictions
- 01Open Security > Web ACL (or the WAF console) and look at sampled requests for BLOCK actions
- 02Open Security > CloudFront geographic restrictions and confirm the country isn't blocked
- 03Adjust or put the blocking rule in Count mode to test
Did this fix it?FIX 4Allow the HTTP methods you need
- 01Open Behaviors > Edit
- 02Under Allowed HTTP methods choose GET, HEAD, OPTIONS, PUT, POST, PATCH, DELETE for API paths
- 03Save changes
Did this fix it?
Symptoms
A plain page titled '403 ERROR - The request could not be satisfied. Bad request.' with a 'Generated by cloudfront (CloudFront)' footer and a Request ID.
Why it happens
- C-01DNS points at CloudFront but the domain isn't added under Alternate domain names (CNAMEs)
- C-02Viewer protocol policy is HTTPS only and the request came over HTTP
- C-03AWS WAF web ACL rule blocked the request
- C-04Geographic restriction blocks the visitor's country
- C-05HTTP method (POST, PUT) not allowed on the cache behavior
// this guide also covers
- the request could not be satisfied cloudfront
- 403 error the request could not be satisfied
- cloudfront bad request 403
- generated by cloudfront 403
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.
Have an app idea? Our small team builds any software: web and mobile apps, games, desktop, AI tools. Price agreed together.
Talk to usThe same problem in other apps
All not loading, error messages & connection guides →
Cloudflare Error 521: Web Server Is Down (Cloudflare)
Fastly Error: Unknown Domain (Fastly)
Google Cloud Quota Exceeded Error (Google Cloud)
Netlify Page Not Found on Refresh (SPA 404) (Netlify)
Other AWS CloudFront errors
- CloudFront 403 Access Denied With S3 Origin
- 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
- Why Is My CloudFront Bill So High?