-
Notifications
You must be signed in to change notification settings - Fork 4k
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
aws-lambda-nodejs: NodejsFunction should enable configuring log group #27414
Comments
This feels like a duplicate of #27413 but with a different target. I suspect that adding a more generic "It'd be nice to have log groups configurable where they might make one" ticket and binding these to it would be appropriate. I'll bring this up with the Construct Squad. |
NodejsFunction extends Function, and includes the same logging related props, so it has all the same functionality. Lambda functions create logs by default on creation, I'm pretty sure we offer the most control you can really have already. Maybe I don't understand the request? |
Thanks for the prompt response and clarification. I see that indeed even on the |
|
Customizing lambda log group is supported now and should get exposed on the Function construct: https://aws.amazon.com/blogs/compute/introducing-advanced-logging-controls-for-aws-lambda-functions/ When that is done, NodeJsFunction construct will also get this property. |
And it’s already done! #28039 |
Describe the feature
The NodejsFunction construct should enable setting the log group similar to how the underlying Lambda construct already does.
Use Case
We would like to centralize all of our application logs into a single log group.
Proposed Solution
Add a new
logGroup
property to the constructor props.Other Information
No response
Acknowledgements
CDK version used
2.95.0 (build cfa7e88)
Environment details (OS name and version, etc.)
Amazon Linux 2
The text was updated successfully, but these errors were encountered: