Versioning and upgrades
Recent releases#
This is a snapshot of the version history visible on the Releases page at the time this page was written — check the link above for the current list, since new versions ship regularly:
| Version | Highlights |
|---|---|
| v2.7.0 (latest) | Skips the TagResources call when the version tag is already current; fixes container-image Lambdas being skipped instead of crashing the whole batch. |
| v2.6.0 | Filters unactionable Lambda events before processing, parallelizes instrumentation work, adds uk1.datadoghq.com as a supported Datadog site. |
| v2.5.0 | Adds a metric for time-to-instrument; refines tag matching around colons and underscores. |
| v2.4.0 | Integration test fixes and dependency updates. |
| v2.3.0 | Tooling migration to Node 24, Yarn 4, and Vitest for tests. |
| v2.2.0 | Adds support for the AWS SSM API Key parameter store option. |
| v2.1.0 | Adds support for Node 24, Python 3.14, and Ruby 3.4 Lambda runtimes. |
| v2.0.0 | Major version: runtime support expands beyond Node/Python to Ruby, Java, .NET, and custom OS runtimes. |
| v1.10.0 | Alternates batch operations and adds adaptive retries. |
| v1.9.0 | Reliability and error-handling improvements. |
How to upgrade an existing stack#
Update your CloudFormation stack using the latest template, which Datadog keeps at a stable URL regardless of version:
https://datadog-cloudformation-template.s3.amazonaws.com/aws/remote-instrument/latest.yaml
Because the instrumenter's Lambda function is versioned alongside the template, a stack update picks up both the new CloudFormation resources and the new instrumenter code in one operation. See the CloudFormation stack-update behavior described in How It Works — an update deletes the stored configuration hash so the next scheduled run re-evaluates every function against the (possibly changed) targeting rules.