This repository was archived by the owner on May 21, 2025. It is now read-only.
Add permission to configure retention in CW LogGroups #13
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.

This is based on the following SIM from an external customer. Please test before merging: https://sim.amazon.com/issues/AWSDocsSchedule-27532
Page URL
https://docs.aws.amazon.com/eks/latest/userguide/fargate-logging.html Issue type:
Incomplete information
Name:
[none provided]
Email:
l**a@dock.tech
Trying to do:
Enable Retention in logGroup over the EKS Fargate LogRouter Make Better:
The IAM Policy recommended in this documentation, not has permission to configure retention in CW LogGroups.
https://raw.githubusercontent.com/aws-samples/amazon-eks-fluent-logging-examples/mainline/examples/fargate/cloudwatchlogs/permissions.json
This policy needs add the follow permissions:
"logs:PutRetentionPolicy"
"logs:DeleteRetentionPolicy"
Issue #, if available (include keywords to close issue as applicable, e.g. "fixes <##>"):
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.