Update CloudWatch plugin's required IAM permissions #1566
+3
−2
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Adis Osmonov <[email protected]>
esmerel
approved these changes
Jan 29, 2025
|
@adis-io do you have a valid test case for this? |
No, I don't have test case, I've just had this issue in my case
|
pipeline/outputs/cloudwatch.md
Outdated
| @@ -84,7 +84,8 @@ The following AWS IAM permissions are required to use this plugin: | |||
| "Action": [ | |||
| "logs:CreateLogStream", | |||
| "logs:CreateLogGroup", | |||
| "logs:PutLogEvents" | |||
| "logs:PutLogEvents", | |||
| "logs:putRetentionPolicy" | |||
There was a problem hiding this comment.
Is the case important here?
There was a problem hiding this comment.
Nope, I've just noticed. It can be changed to PutRetentionPolicy for consistency
Signed-off-by: Adis Osmonov <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Without this policy it won't be possible to use custom retention period