-
Notifications
You must be signed in to change notification settings - Fork 877
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deny s3:ListBucket #203
Deny s3:ListBucket #203
Conversation
Do you think it is reasonable to expand the comment to say that while ListBucket is denied it is still possible for someone to guess a valid URL and in that case this infrastructure would serve the file? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Might want to expand the comment to explain the subtle issue that anything you put in the bucket is still public, assuming you could guess the path.
* Deny s3:ListBucket * Update comment
* Revert "Deny s3:ListBucket (pulumi#203)" This reverts commit 71225e5.
* Deny s3:ListBucket * Update comment
* Revert "Deny s3:ListBucket (pulumi#203)" This reverts commit 71225e5.
* Deny s3:ListBucket * Update comment
Update the static website on AWS example to deny the
s3:ListBucket
permission. We set the "public-read" ACL on the bucket, so that CloudFront can read the bucket's contents. However, just following best practices with regard to content security, we deny thes3:ListBucket
permission to prevent unintentional disclosure of the website's contents.See pulumi/get.pulumi.com#33, pulumi/docs#734