CloudFront not serving site – DNS resolves but no content on sdaudit.com

Question

I'm hosting a static website at sdaudit.com using an S3 bucket + CloudFront. DNS is working (confirmed via Resolve-DnsName and nslookup) and the CloudFront domain (dlwszbd1ksu6c.cloudfront.net) resolves.

The domain points to the distribution via Route 53, and SSL is properly set up. However, nothing loads—no errors, just a blank site.

I’ve confirmed:

S3 bucket name matches the domain: sdaudit.com

Bucket has public read policy and index.html is present

CloudFront is deployed with correct origin (sdaudit.com.s3-website-us-east-1.amazonaws.com)

Viewer policy is set to redirect HTTP to HTTPS

What else should I check to get my site visible?

Malini Agrawal · Accepted Answer

hi,

you have already resolved the domain and delegated to route 53---- But in route53 hosted Zone still need to create A/Alias record to point to  endpoint to resolve,  in you case your  CloudFront distribution.

Without A/AAAA record in hosted zone, domain is there, but there is no record telling DNS where to go, so you end up with blank page.

so, to fix it:

Go to Route53 > Hosted Zones >sdaudit.com
Records Type A-IPV4 and/or AAAA IPV6

Alias: Yes

Alias target: your distribution "dlwszbd1ksu6c.cloudfront.net"  --- it auto suggest.

create a record.

and that is all,  your sdaudit.com will resolve and load your distribution.

Best,

re:Post Agent · Answer

Based on the information provided, it seems you've covered many of the common issues, but there are a few additional areas to check:

1. CloudFront Cache: Ensure that your CloudFront distribution's cache is up to date. You may need to create an invalidation for "/*" to clear the cache and force CloudFront to fetch the latest content from your S3 bucket.

2. S3 Bucket Configuration: Verify that your S3 bucket is properly configured for static website hosting. Make sure you have both an index document (usually index.html) and an error document specified in the static website hosting settings.

3. CloudFront Origin Settings: Double-check that your CloudFront distribution is using the S3 website endpoint as the origin, not the regular S3 bucket endpoint. The origin should be in the format "bucket-name.s3-website-region.amazonaws.com".

4. CloudFront Behaviors: Review your CloudFront behaviors to ensure they're configured correctly. Check that the default cache behavior allows GET and HEAD HTTP methods at minimum.

5. S3 Bucket Policy: Confirm that your S3 bucket policy allows CloudFront to access the content. You may need to update the policy to explicitly allow the CloudFront service principal.

6. Browser Cache: Try accessing the site from an incognito/private browsing window or after clearing your browser cache to ensure you're not seeing a cached version of the blank page.

7. CloudFront Error Pages: Check if you have any custom error responses set up in CloudFront that might be interfering with the display of your content.

8. CloudFront Distribution Status: Verify that your CloudFront distribution status is "Deployed" and not "In Progress".

If after checking these items you still can't see your content, you may want to review the CloudFront logs or contact AWS support for further assistance.  
**Sources**  
[Static site not displaying updates even if cloudfront distribution url is showing changes | AWS re:Post](https://repost.aws/questions/QUF4RR5uJOQO-wn1yjvou-Rw/static-site-not-displaying-updates-even-if-cloudfront-distribution-url-is-showing-changes)  
[Cloudfront cannot access s3 bucket | AWS re:Post](https://repost.aws/questions/QUMENLErL3QRuNc7miIXHhhQ/cloudfront-cannot-access-s3-bucket)  
[my website is loading on HTTP after redirecting traffic from HTTP to HTTPS from CloudFront. | AWS re:Post](https://repost.aws/questions/QUUQE77HJ1Q4GJ18N-2oVX2Q/my-website-is-loading-on-http-after-redirecting-traffic-from-http-to-https-from-cloudfront)

CloudFront not serving site – DNS resolves but no content on sdaudit.com

Add your answer

Relevant content