mapbox / mapbox/magic-cfn-resources
Bucket permissions default to a scope
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 6
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
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?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the CloudFormation stack definition for the BucketNotificationResources parameter and review how its unset value produces the notification policy. Confirm whether any documented use case requires the wildcard default; done means the parameter is required, the broad default is removed, and the resulting policy is limited to explicitly supplied buckets.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, javascript
- Domain
- cloud, security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100