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
When CDK brings its own lambdas for certain tasks, those lambda functions log to a log group that has no retention configured and I don’t see a way to configure one.
I can configure retention time for my own Lambdas, but not for those deployed and used transparently by CDK-internal functionality. Is it possible to either set a default retention time for those logs or make it somehow configurable?
It would be great if this could be addressed somehow. Is there a plan to include this in a future release ?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hello All,
When CDK brings its own lambdas for certain tasks, those lambda functions log to a log group that has no retention configured and I don’t see a way to configure one.
I can configure retention time for my own Lambdas, but not for those deployed and used transparently by CDK-internal functionality. Is it possible to either set a default retention time for those logs or make it somehow configurable?
It would be great if this could be addressed somehow. Is there a plan to include this in a future release ?
Beta Was this translation helpful? Give feedback.
All reactions