(custom-resources): CustomResourceProvider should allow configuring log group destination

[AlJohri]

Describe the feature

The Custom Resource Provider Framework (particularly the Provider construct) should enable configuring the log group destination for both the lambdas and step functions that it automatically generates.

Use Case

I would like to centralize our entire application to use the same log group for easier observability. We utilize different stream prefixes to keep the logs organized across the various services.

Proposed Solution

No response

Other Information

Related: #26553

Acknowledgements

• I may be able to implement this feature request
• This feature might incur a breaking change

CDK version used

2.95.0 (build cfa7e88)

Environment details (OS name and version, etc.)

Amazon Linux 2

[indrora]

Thank you so much for the feature request.

Since there's a good chance that other systems make use of a log group destination, it could be worth looking into Aspects as a way to override log groups: Aspects are checked just after your application has generated the framework for CloudFormation but before it's reified into full cloudformation structures.

if you'd like to offer a PR for this particular feature, we'd be more than happy to review it.

[peterwoodworth]

Lambda functions will create their own log groups, you cannot customize the log group name or to use an existing log group as far as I know, which is why the existing solution is the way it is. Maybe I'm mixing up what you mean by "destination"?

[AlJohri]

Lambda functions will create their own log groups, you cannot customize the log group name or to use an existing log group as far as I know, which is why the existing solution is the way it is. Maybe I'm mixing up what you mean by "destination"?

Thanks for the prompt response and clarification. I see that indeed even on the Function construct, there is no construct property for log group. Coming from the ECS world, I did not realize that you can't change the log group of a lambda.

In this case, there is also the internal "waiter state machine" for async custom providers where we could allow configuring the log group, but given we can't change the log group of the lambdas, this likely doesn't make much sense.

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

[AlJohri]

Looks like customizing lambda log group is supported now: https://aws.amazon.com/blogs/compute/introducing-advanced-logging-controls-for-aws-lambda-functions/

[github-actions]

Comments on closed issues and PRs are hard for our team to see.
If you need help, please open a new issue that references this one.