fix(events-targets): KinesisStream
target not working when the stream is encrypted using a customer kms key
#30956
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue #10996
Closes #10996
Reason for this change
Unless there is a specific reason that I am missing, I don't see why it was necessary to manipulate the policy directly rather than delegate to the
granWrite
method already provided by theIStream
interface, whose implementation would automatically also add the necessary KMS permissions to theRole
.Description of changes
Use
stream.grantWrite
rather than managing the IAM policy directly.Description of how you validated changes
Delegating to existing unit tests. I would also test these changes on our real code if a SNAPSHOT is released.
Checklist
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license