News for hackers. Stuff that matters.
Re:Investigating Multi-Account IAM Issues in S3 and CloudFront by jeffnappi on Wednesday July 17, 2019 @11:38PM (#20466477)
An issue I've encountered with static website hosting on CloudFront+S3 is that if you want `index.html` to be served at the root path of a URL - e.g. https://www.yoursite.com/folder/ vs https://www.yoursite.com/folder/index.html, you must use the s3 website endpoint rather than the S3 Origin. And in that case, unfortunately, it is not possible to use Origin Access Identity.
Re:Investigating Multi-Account IAM Issues in S3 and CloudFront by kevinslin on Thursday July 18, 2019 @01:23AM (#20466969)
good news is that you can remedy that now by using lambda@edge to rewrite requests - there's even an aws blog post about it: https://aws.amazon.com/blogs/compute/implementing-default-di...
Re:Investigating Multi-Account IAM Issues in S3 and CloudFront by fishtacos on Friday July 19, 2019 @08:49AM (#20478182)
From the blog post above:

"It does not work on any subdirectory (such as http://www.example.com/about/). If you were to attempt to request this URL through CloudFront, CloudFront would do a S3 GetObject API call against a key that does not exist."