3 ms·
When you setup an S3 bucket the permissions are pretty explicit. The issue here is the UI is confusing (arguably it's wrong but I digress) and is related to a c
by BinaryIdiot 7y ago
When you setup an S3 bucket the permissions are pretty explicit. The issue here is the UI is confusing (arguably it's wrong but I digress) and is related to a configuration that you'd have to hunt for. It's not an obvious permission that you can easily know it should be changed unless you have experience with it (whereas S3 it's listed right there when you created it and by default it's pretty private).
- deleted 7y ago[deleted]
- paulstovell 7y agoIt didn’t used to be. When you set up a bucket with public read access, you might also decide to give other people on your team write access to the bucket. AWS conveniently provided an All Users option for this. Except it wasn’t “All Users in your AWS account”, it literally meant ALL USERS of AWS. Disaster. This led to the same problems as this Jira issue. AWS changed it so that’s no longer an option. Atlassian should do the same.