-
Notifications
You must be signed in to change notification settings - Fork 4k
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
iam: add more granular grant permissions #24074
Comments
Hi @justinwiley , thanks for reaching out and suggesting this feature request. I am marking this issue as p2, which means that we are unable to work on this immediately. We use +1s to help prioritize our work, and are happy to revaluate this issue based on community feedback. You can reach out to the cdk.dev community on Slack to solicit support for reprioritization. Meanwhile, you could use Escape hatches as a workaround. |
I've added an optional parameter `allowedActionPatterns` that will restrict the permissions to a certain list of action patterns for the `grantWrite` method. Closes #24074 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
|
Describe the feature
The IAM grant mechanism (grantWrite, grantRead, etc) should allow for additional parameters that can override the default permissions.
Use Case
The default permissions granted using grantWrite, grantRead etc can be overly permissive for certain usecases. For example
bucket.grantWrite(principale)
leads to the IAM permissions:For certain usecases, these are overly permissive. One example is granting a principal access to a write only bucket containing an audit log; the principal shouldn't be able to delete objects.
Proposed Solution
One possible implementation:
Other Information
No response
Acknowledgements
CDK version used
2.63.2
Environment details (OS name and version, etc.)
mac os
The text was updated successfully, but these errors were encountered: