Was looking for how to configure your DNS to make this work. Trying to do option 2 to a single path/domain. It seems like a simple A record alias to the s3 website endpoint but doesn't seem to work and I'm not sure where I'm getting stuck. I have configured it for the apex record of the domain so example.org > example.org.s3-website.us-e.... Verified the s3 endpoint is doing the redirect when I go to it explicitly but hitting just the apex record example.org is timing out. Do i need to have cloudfront in the mix as well? Other documentation i've read hasn't mentioned it unless I wanted to do more elaborate path redirects like in case 3 you mentioned.

If you're using CloudFormation to provision a stack with the CloudFront + Lambda@Edge redirect option, I'm pretty sure your stack must be deployed in N.Virgina for CloudFront+Lamda@Edge config to work. It's possible I have this wrong as it's from memory when I tried this a few months ago.

That's embarrassing. you said this already. Sorry.

such an awesome guide thank you so much

Thanks for a very informative blog! Helped me to understand how to solve a problem I had. The only thing I found missing here is the IAM configurations for Lambda. These are not trivial to configure, at least not for those not fluent with IAM. Any chance you can provide an advice on that?