Extensibility of datadog-cdk-constructs-v2 + more regular cadence of aws-cdk-lib npm version updates

[frankpengau]

Hi Datadog Team,

Just looking into this datadog-cdk-constructs-v2 library and how our organisation might be able to create wrappers around your custom constructs that extend off the aws-cdk L2 Constructs (e.g. DatadogECSFargate, DatadogECSFargateTaskDefinition).

However, we noticed that it is relying on aws-cdk-lib v2.177.0 (released 25th January 2025), which would be released about 6 to 7 months at the time of writing, so wondering if there was any support for a more regular cadence of releasing with newer versions of aws-cdk-lib.

Also whether if there was potentially any appetite in expanding the exports to include things like just the ecs.FirelensDriver, as we have already have an internal custom cdk construct library that extends off aws-cdk's L2 Constructs.

Ideally, we don't want to migrate all our custom cdk constructs manually to Datadog's cdk constructs that extend off aws cdk constructs. We want to just retrofit and add the logging driver and the sidecar container to our existing aws-cdk stacks and custom cdk constructs.

Apologies for the loaded question(s), but just wanted to see if we want to proceed with the lambda log forwarder pathway or whether if the maintenance schedule of this repo and datadog-cdk-constructs would allow for more aws native integration methods.

[gabedos]

Hi @frankpengau, thanks for reaching out!

As you can see in the mentions, we've upgraded the aws-cdk-lib version and have created some scripts to help with maintaining it up to date!

Regarding your second point about the ECS Fargate construct’s ecs.FirelensDriver: I think there’s potential to expose the driver so users can supply a custom definition. That said, we’d want to be thoughtful about how we approach this—mainly to ensure the developer experience remains clean and intuitive, especially since the construct already supports a few built-in options for configuring the driver.

datadog-cdk-constructs/src/ecs/fargate/interfaces.ts

Lines 41 to 50 in 4118ab4

	export interface FluentbitConfig {
	/**
	* Configuration for the Datadog log driver.
	*/
	readonly logDriverConfig?: DatadogECSLogDriverProps;
	/**
	* Firelens options for the Fluentbit container.
	*/
	readonly firelensOptions?: DatadogFirelensOptions;
	/**

I'll keep track of this issue and discuss further with my team to see how we can provide more flexibility for users.

[avangelillo]

Thanks for reaching out, like @gabedos mentioned we've fixed our automation around updating the CDK version. We just released v2-3.2.0 which has a newer version of CDK, and moving forward these updates should happen automatically.