You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I recently noticed that my AWS account has a lot of loggroups of lambdas from old, deleted blueprints clusters. All loggroups have their retention set to Never expire. It would be nice if there's a blueprints option to configure the lambda settings (including retention).
Not sure if that's somehow already possible but i was not able to find an option for that.
Use Case
To prevent AWS accounts to be flooded with old, uneeded CloudWatch loggroups.
Proposed Solution
No response
Other Information
No response
Acknowledgements
I may be able to implement this feature request
CDK version used
2.147.3 (build 32f0fdb)
EKS Blueprints Version
1.16.3
Node.js Version
v20.12.2
Environment details (OS name and version, etc.)
Ubuntu 22.04
The text was updated successfully, but these errors were encountered:
@muckelba I assume you mean log groups for the lambdas that support custom resources for CDK such as the one handling EKS cluster creation or helm chart installation. I looked around in the past and could not find a specific controls in CDK to make it happen. Let me take another look now. Worst case, I will have to create an issue against CDK and reference it there.
Describe the feature
I recently noticed that my AWS account has a lot of loggroups of lambdas from old, deleted blueprints clusters. All loggroups have their retention set to
Never expire
. It would be nice if there's a blueprints option to configure the lambda settings (including retention).Not sure if that's somehow already possible but i was not able to find an option for that.
Use Case
To prevent AWS accounts to be flooded with old, uneeded CloudWatch loggroups.
Proposed Solution
No response
Other Information
No response
Acknowledgements
CDK version used
2.147.3 (build 32f0fdb)
EKS Blueprints Version
1.16.3
Node.js Version
v20.12.2
Environment details (OS name and version, etc.)
Ubuntu 22.04
The text was updated successfully, but these errors were encountered: