Create an S3 Bucket

From @jayair on Mon Apr 10 2017 01:08:56 GMT+0000 (UTC)

Link to chapter -

Copied from original issue:

When the bucket policy given in the book is applied, aws console displays a warning;

This bucket has public access
You have provided public access to this bucket. We highly recommend that you never grant any kind of public access to your S3 bucket.

Is this expected behavior? If so, what should one do instead?

In this case, we want our S3 bucket (and the app inside it) to be publicly accessible. So it is safe to ignore this. However, we shouldn’t make our file uploads bucket publicly accessible.

There are two new default settings in the boilerplate setup that prevent you from adding public policies to buckets, and, apparently, from allowing a bucket to be public while you “fix the policy.”

Or at least I had these come up, and was wondering why I was getting 403s on updating the policy. If you’re getting these, edit the “Public access settings,” and uncheck the options for “Manage public bucket policies for this bucket.”


Thanks for sharing. Sounds like we need to update the screenshots.

Yes, I had the same issue and found the same solution. This screenshot shows the two boxes that need to be unchecked:

1 Like

Got it. Yeah it needs to be updated.

FYI, I also had this same issue, but to solve it, unchecking of these two ‘manage public policies’ boxes had to also be done on the larger, console level for the entire account – i.e., change the bucket-changing policies for ALL Buckets, not just the individual client app bucket. Thank you so much for your incredible tutorial!!!

1 Like

Thanks for letting us know!

It would be a great example to show how this entire bucket setup and cloud formation, SSL certificates, etc. Could all be done by SST as part of an IAC project. This way everything is ready to go and then in the react or angular project you can simply sync it to the bucket, invalidate the index.html (if you want?) and be good to go.

Bonus points to extract the bucket name from the output of the stack to use in the deployment?

Yeah we’ll do this at some point in the near future!