Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

#

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Jump to bottom

Bucket permissions default to a scope #23

Open
zmully opened this issue Mar 24, 2018 · 0 comments
Open

Bucket permissions default to a scope #23

zmully opened this issue Mar 24, 2018 · 0 comments

Comments

@zmully
Copy link
Contributor

zmully commented Mar 24, 2018

If the parameter BucketNotificationResources is not set, the stack creates a policy giving read/write notification permissions on all buckets within the account. Can this logic be inverted by making the BucketNotificationResources parameter is required, and removing the * default? Is there a use case for * that prevents this inversion?
# for free to join this conversation on GitHub. Already have an account? # to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@zmully