// troubleshooting guide · aws cloudfront
CloudFront 403 Access Denied With S3 Origin
- Status
- Workaround available
- platforms:
- AWS Console, AWS CLI, Terraform, CloudFormation
- updated:
- November 17, 2026
- reports:
- 6
- Method
- how we research
RUNBOOK · aws-cloudfront/403-access-denied-s36 FIXES
// quick answer
CloudFront 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.
Most likely fix: Use OAC with the S3 REST endpoint
How to fix it
// try these in order, the most common fix is first
FIX 1Use OAC with the S3 REST endpoint
- 01Open CloudFront > Distributions > your distribution > Origins > Edit
- 02Pick the bucket from the list (bucket.s3.region.amazonaws.com), not the s3-website endpoint
- 03Under Origin access choose Origin access control settings and create or select an OAC
- 04Save changes
Did this fix it?FIX 2Copy the bucket policy CloudFront generates
- 01After saving the origin, click Copy policy in the yellow banner
- 02Open S3 > your bucket > Permissions > Bucket policy > Edit
- 03Paste the policy so it allows s3:GetObject with Condition AWS:SourceArn set to your distribution ARN
- 04Keep Block Public Access on; OAC doesn't need public access
Did this fix it?FIX 3Set the default root object
- 01Open the distribution > General > Settings > Edit
- 02Enter index.html in Default root object
- 03Save and wait for the distribution to finish deploying
Did this fix it?FIX 4Check whether the file exists
- 01Run aws s3 ls s3://your-bucket/path/to/file
- 02Check the key's exact case and prefix (S3 keys are case-sensitive)
- 03If you want real 404s, add s3:ListBucket for CloudFront to the bucket policy
Did this fix it?FIX 5Allow KMS decryption for encrypted objects
- 01If objects use SSE-KMS, open the KMS key policy
- 02Allow kms:Decrypt for the cloudfront.amazonaws.com service principal with your distribution ARN as source
- 03Retry the request
Did this fix it?FIX 6Work out who returned the 403
- 01Run curl -I https://your-domain/file and look at x-cache and Server headers
- 02If the request appears in S3 server access logs, S3 denied it: fix the bucket or KMS policy
- 03If it never reaches S3, look at WAF rules, geo restriction or signed URL settings on the distribution
Did this fix it?
Symptoms
Browser shows an XML page with <Code>AccessDenied</Code>, or a 403 on the root URL while /index.html works, or 403 for some files only.
Why it happens
- C-01Bucket policy doesn't grant s3:GetObject to cloudfront.amazonaws.com for your distribution ARN
- C-02Origin is the S3 static website endpoint, which can't use OAC or OAI
- C-03Default root object (index.html) not set, so requests to / fail
- C-04The object doesn't exist and CloudFront has no s3:ListBucket, so S3 returns 403 instead of 404
- C-05Explicit deny, IP/VPC conditions or SSE-KMS encryption without KMS permissions for CloudFront
- C-06Objects uploaded by another account are not owned by the bucket owner
// this guide also covers
- cloudfront 403 access denied s3
- cloudfront accessdenied
- cloudfront oac 403
- s3 cloudfront 403 forbidden
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 usOther AWS CloudFront errors
- 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
- Why Is My CloudFront Bill So High?