-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AwsCustomResource support for log retention #6652
Comments
Copy: @jogold |
Add a `logRetention` prop to `AwsCustomResourceProps` to specify a custom log retention. Closes aws#6652
…ts--> feat(custom-resources): log retention for AwsCustomResource (#6677) <!--Use this to give a more detailed message that describes the change--> Add a `logRetention` prop to `AwsCustomResourceProps` to specify a custom log retention. <!--For every issue your PR resolves, add `fixes #<issue>` or `closes #<issue>`--> Closes #6652 <!--Shout out to collaborators.--> <!--If your PR includes breaking changes, uncomment and fill in the following (notice how multiple breaking changes should be formatted):--> <!-- BREAKING CHANGE: Description of what broke and how to achieve this behavior now<br> \* **module-name:** Another breaking change<br> \* **module-name:** Yet another breaking change --> <!--IMPORTANT: This section cannot contain any additional markdown headers (#)-->
@eladb Thank you! 👍 Question - is there any task on the RoadMap for Function/SingletonFunction to use the LogRetention construct - that is comprised of both logRetentionDays and the related Role? |
@mcalello do you mean using the custom resource with log retention and also a custom IAM role for this log retention ( |
Thanks @jogold - I was about to do that, when I realized that there's a construct that would capture both of those mentioned above. But if Lambda isn't going to support that soon - yes, we would need to add the logRetentionRole prop to AwsCustomResource. |
Currently, whenever an AwsCustomResource is deployed it creates its own Lambda function - with the LogRetention set to INFINITE. This feature requests is asking for that to be overridable by an additional Contruct prop within the AwsCustomResource or the AwsSdkCall.
Use Case
Without this feature, teams must manually find and delete logs created by these lambdas.
This is a 🚀 Feature Request
The text was updated successfully, but these errors were encountered: