AWS S3 Bucket policy editor access denied
Amazon Web-ServicesAmazon S3BucketAmazon Web-Services Problem Overview
Amazon Web-Services Solutions
Solution 1 - Amazon Web-Services
This could be due to recent changes in S3
. To fix this issue, you need to assign Public Access to the bucket, follow the below steps:
Solution 2 - Amazon Web-Services
"Manage public bucket policies for this bucket" section need to be unchecked for to introduce "Allow" policies.
> But be cautious, unchecking these might enable you to introduce a > policy but that policy is a public policy making your bucket public.
Having these checked - You won't be able to introduce "Allow" policies that for this bucket.
You can however introduce "Deny" policies, with these options checked.
Solution 3 - Amazon Web-Services
Solution 4 - Amazon Web-Services
The accepted answer works even if related comments suggest it's not a good idea for security reasons. In fact it is in line with AWS instructions for static website hosting here
https://docs.aws.amazon.com/AmazonS3/latest/userguide/HostingWebsiteOnS3Setup.html
which answers the OP's question.
To summarise the steps (given in the linked page) to configure a static website on Amazon S3:
- Create a bucket
- Enable static website hosting
- Unblock all public access
- Add the bucket policy that makes your content publicly available (the yaml config you have in your post)
- Configure your index document (usually index.html)
- Configure any error/redirect/no-auth documents (for React this is usually also index.html)