S3 block public access and simplified routing for S3 Static Website Hosting feature

Question

Hi AWS,

I am hosting two frontends on two different S3 bucket as static website using CloudFront as CDN which is secured using TLS/SSL ACM public certificate. I have a couple of questions around the same, in order to use the bucket as a static website you need to make your bucket and objects public (security constraint), else you need to go through Route53 way where you need to create DNS record entries. We are using Cloudflare for creating DNS entries so how can we fill that gap of not making bucket and objects public.

Secondly my question is how can I use only one bucket to host both my application and storybook pipeline (another application) and will have different routes (URLs).

Please guide!

Gary Mclean · Answer

You can secure your S3 bucket to only allow cloudfront while hosting your website and prevent anyone accessing it here using OAC  https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/private-content-restricting-access-to-s3.html

This is the way to secure your bucket.

Your 2nd question you can route different uris to different sources https://advancedweb.hu/how-cloudfront-routing-works/#:~:text=Routing%20in%20CloudFront%20is%20based%20on%20the%20path%20of%20the%20request.&text=This%20is%20the%20distinguishing%20factor,backend%20server%20the%20request%20goes.

https://repost.aws/knowledge-center/cloudfront-distribution-serve-content

S3 block public access and simplified routing for S3 Static Website Hosting feature

Add your answer

Relevant content