aws-logs-destinations: Missing `FirehoseDestination` or `DataFirehoseDestination`

[czechnology]

Describe the feature

Currently, the aws_cdk.aws_logs_destinations package only contains KinesisDestination and LambdaDestination. However, logs subscriptions are possible also to Amazon Data Firehose, yet there seems to be no way to configure such subscription using CDK at the moment?

Use Case

I want to subscribe to CloudWatch Logs with Firehose as the destionation, as per this example in docs. My particular use case is forwarding of logs from CloudWatch to Dynatrace using Firehose.

Proposed Solution

Add a [Data]FirehoseDestination class to aws_logs_destinations.

Other Information

No response

Acknowledgements

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

CDK version used

2.159.1

Environment details (OS name and version, etc.)

WSL2, Python 3.12

[ashishdhingra]

Valid feature request.

• Per aws-cdk-lib.aws_logs_destinations, it only supports KinesisDestination and LambdaDestination.
• Log destination L2 construct gets synthesized to AWS::Logs::Destination resource.
• Per Real-time processing of log data with subscriptions, it also supports Amazon Data Firehose stream.
• The implementation for Amazon Data Firehose stream could follow Example 3: Subscription filters with Amazon Data Firehose.

[tomoki10]

@ashishdhingra
I would like to implement this feature request and have already started working on it.
However, previous discussions concluded that they should use L2 Firehose, and the PR was closed.
#14918
Since L2 Firehose has remained in alpha for over 3 years, would it be acceptable to implement this for L1 Construct instead? Or should I implement it for the alpha version of L2 Construct?
Please advise on the best approach. Thanks.