- Newest
- Most votes
- Most comments
You will need to front the one bucket with a CloudFront distribution and have both example.com and www.example.com point, via a Route 53 Alias, to the distribution. You get the added benefits of being able to serve up HTTPS (with free ACM certificate), it does not matter what your bucket is named, and you don't need to make your bucket public. Plus it may save some money, AWS price reduction for data transfers out to the internet
What kentrad mentioned is of course valid but it will just serve your page from both addresses
- www.example.com
- example.com
I assume that you want to always redirect non www domain to www domain.
Then to achieve it you can follow kentrad advice, but you need two CloudFront distributions.
- for www.example.com serving page from S3
- for example.com add CloudFront function to redirect to www.example.com - example of such function you can find on my GitHub
It can be achieved with one CloudFront distribution, but it will increase the amount of invocations of CloudFront Function. This implementation is described here.
Relevant content
AWS OFFICIALUpdated 9 months ago- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a month ago
- AWS OFFICIALUpdated 2 years ago
OK I have this exact issue described here in this new question. I rewrote it in this new question because the old question does not elaborate on the situation enough. and there is nearly zero information out there about this problem. here is my new question: repost.aws/questions/QUGfaD2IwsTuirmrDTrQ6JEg/is-there-a-way-to-not-have-2-cloudfront-distributions-for-the-1-website-www-base-domains