Amazon CDK End of Life (EOL) Dates and End of Support (EOS) Dates

Latest Release: 2.277.0

Amazon CDK 2.277.0 is the current supported release. Track Amazon CDK end of life dates — EOL, EOS and EOSL dates — across all 1 release. Also see Amazon Kindle end of life dates for related end-of-life information.

Currently Supported Amazon CDK Releases - Active EOS/EOSL Support (1)

Release Released Security Support Latest
2 (4 years and 11 months ago) Active 2.277.0 (1 week and 2 days ago)

Amazon CDK end of life is not a single date: the AWS CDK retires major versions and Node.js runtimes on separate schedules, and CDK v1 and Node.js 18.x are already past end-of-support. If you write infrastructure as code in one of its supported programming languages, this guide explains what each end-of-life date means for your AWS resources, the CDK CLI, the Construct Library and ecosystem tools such as JSII, Projen and CDK8s, so developers can plan upgrades before new features pass them by.

Amazon CDK end of life: where each release stands

Only one major line of the AWS Cloud Development Kit is active today: CDK v2, first released on December 1, 2021. The endoflife.date tracker, last updated on October 21, 2026, lists 2.274.0 (published October 20, 2026) as the latest version. The release schedule is roughly weekly, with extra builds in between for critical issues, so each version is replaced quickly. The practical rule is to stay current on v2 and watch two other clocks: the end of the major version itself and the end of the Node.js runtime beneath it. The source code and release notes live on GitHub.

AWS CDK v1 end-of-support

CDK v1 entered maintenance on June 1, 2022 and reached end of support on June 1, 2023. Since then AWS offers no maintenance, updates or technical support for it. Old releases stay on public package managers and the code stays online, but staying on them exposes your stacks to security vulnerabilities and breaks compatibility with newer AWS services. To find stacks still deployed with v1, run the awscdk-v1-stack-finder utility.

Security patches and bug fixes after June 2023

An unsupported release gets no security patches and no bug fixes, and its performance and feature gaps widen every week. Questions about moving off it go to the community on the cdk.dev Slack workspace or to a GitHub discussion.

CDK v2 migration away from unsupported releases

Moving to AWS CDK v2 is usually straightforward for most projects. Stable constructs now ship in one package, and deprecated v1 APIs were removed, so work through these steps in order:

  • Update to a recent v1 release first and fix every deprecation warning.
  • Review feature flags, because behavior they gated in v1 is on by default in v2.
  • Check CDK Toolkit compatibility with your app's version.
  • Deploy to a non-production account before touching production deployments.

Upgrade dependencies and import statements

Replace the many per-service packages with aws-cdk-lib through npm, import Construct from the separate constructs module, and rewrite import statements to the new namespaces. TypeScript developers need version 3.8 or later.

Re-bootstrapping your AWS environments

CDK v2 requires the modern bootstrap stack; the legacy one is no longer supported. Re-bootstrapping each account and Region once is secure and low risk, and because the library follows strict semantic versioning, later 2.x releases will not break your app.

Node.js LTS support policy and end-of-life dates

The CDK runs on Node.js and supports only Long Term Support (LTS) versions. When the community marks a version end-of-life, the CDK keeps supporting that runtime for an additional six months, then stops issuing security fixes or compatibility updates. As of July 2025 the Active Long Term Support release is Node.js 22.x. Check the Node.js release schedule for upcoming dates.

Node.js versionNode.js end-of-lifeCDK support ends
24.xApril 30, 2028October 30, 2028
22.xApril 30, 2027October 30, 2027
20.xApril 30, 2026October 30, 2026
18.xApril 30, 2025November 30, 2025

Timeline of the 18.x deprecation

AWS announced the Node.js 18.x deprecation in July 2025, giving a five-month transition period before support ended on November 30, 2025. Once it ended, reports tied to Node.js 18.x must be reproduced on 20.x or 22.x first, and new features are built on modern runtime APIs, so unsupported projects drift further from the latest version. Third-party libraries in the community ecosystem tend to follow the same schedule.

Checking your runtime before the next end of support

Do this now, especially because Node.js 20.x support ends on October 30, 2026, only three days after this page was written:

  1. Run node -v on every laptop, CI/CD pipeline and deployment system.
  2. Update the runtime with nvm or the official installer, preferably to Node.js 22.x.
  3. Test custom constructs in non-production, then roll the update to production.
  4. Bookmark the AWS CDK Node.js support page and open a GitHub issue if a version looks wrong.

EOL dates of related software products