AWS CDK v1 will enter Maintenance Mode after June 1, 2022

[madeline-k]

AWS CDK v1 will enter Maintenance Mode after June 1, 2022. After this date, v1 releases will contain new and updated resource level “L1” constructs, critical bug fixes, and security updates only. We will not publish new features or minor bug fixes to v1. See the AWS SDKs and Tools maintenance policy for more detail on what this means.

Maintenance mode has a duration of 12 months. On June 1, 2023, CDK v1 will reach end-of-support. After this date, the AWS CDK v1 will no longer receive updates or releases. Previously published releases will continue to be available via public package managers and the code will remain on GitHub. Use of a CDK version which has reached end-of-support is done at your own discretion. We recommend you upgrade to the new major version.

To continue to get new AWS CDK features, migrate your CDK apps and construct libraries to AWS CDK v2. See this guide for details and instructions.

You can also use this tool to help you identify stacks in your account that were deployed with AWS CDK v1:

# Preload your shell with AWS credentials
npx awscdk-v1-stack-finder

# Use a profile
AWS_SDK_LOAD_CONFIG=1 AWS_PROFILE=<name> npx awscdk-v1-stack-finder

[robertd]

This issue/notice should be pinned. :)

[jmiumv]

Couple of questions regarding monocdk

1. What does this mean for monocdk ? With a weekly download rate hovering at ~13.5k, I am guessing you are going to publish a monocdk v2 as well ? If so what is the timeline for that ?
2. monocdk has been experimental, for nearly two years now, wondering why it is still marked as such (almost 2 years now based on git blame) and as a follow up, when would it be stable ?

[madeline-k]

@JoeNonExotic thanks for your questions!

1. monocdk is considered a part of AWS CDK v1, and monocdk users should migrate to v2 (aws-cdk-lib). You can follow the same migration guide linked in the issue above.
2. We have no plans to stabilize monocdk. It is essentially the experimental version of aws-cdk-lib. You can read more in this RFC about how monocdk was the basically a proof of concept for aws-cdk-lib.

[chejef]

Regarding to cdk 2.x, wondering when to move away from cloudformation resources, e.g. the CfnJobDefinition with aws_batch while cdk 1.x has its own constructs.

[madeline-k]

Hey, @chejef, the aws-batch L2 constructs are currently experimental. In AWS CDK v2, the experimental modules are separated from the main library (aws-cdk-lib) and published separately. You can find the aws-batch L2 constructs for v2 in the aws-batch-alpha module.

[girisaidinakar]

@madeline-k, how can we find who is using cdk v1 in aws org which is having 850 accounts ?

Thanks in advance

[indrora]

@girisaidinakar I'm not sure if there's a good way to tell if someone's using CDKv1 purely from the CloudFormation output, but, there are some potential signs if you have access to the CDK stack definitions that are very easy to start with. These all come from the CDKv1 vs v2 migration page in the CDK docs:

• Not using the aws-cdk-lib and instead relying on @aws/...
• Using deprecated properties and APIs that were deprecated between CDKv1 and v2.
• Not using the Constructs library -- This is the most likely hint that you're on V1 if I'm reading everything right.

However, there is another indicator that can determine a bare minimum version that it could have been deployed using V1: there is a Metadata resource that is added to each stack that contains some analytics data, AWS::CDK::Metadata. If you haven't opted out of it, a quick check will tell you:

• If the AWS::CDK::Metadata contains a property called Analytics, it was deployed using a CDK released after 1.93. The CDK contains an encoder for this format, but I don't have a good decoder for it.
• If it has a Modules property, it was deployed before CDKv2 was released.

[girisaidinakar]

@girisaidinakar I'm not sure if there's a good way to tell if someone's using CDKv1 purely from the CloudFormation output, but, there are some potential signs if you have access to the CDK stack definitions that are very easy to start with. These all come from the CDKv1 vs v2 migration page in the CDK docs:

• Not using the aws-cdk-lib and instead relying on @aws/...
• Using deprecated properties and APIs that were deprecated between CDKv1 and v2.
• Not using the Constructs library -- This is the most likely hint that you're on V1 if I'm reading everything right.

However, there is another indicator that can determine a bare minimum version that it could have been deployed using V1: there is a Metadata resource that is added to each stack that contains some analytics data, AWS::CDK::Metadata. If you haven't opted out of it, a quick check will tell you:

• If the AWS::CDK::Metadata contains a property called Analytics, it was deployed using a CDK released after 1.93. The CDK contains an encoder for this format, but I don't have a good decoder for it.
• If it has a Modules property, it was deployed before CDKv2 was released.

@indrora , thanks for update in detailed

[awspsgithub]

Command line tool to identify stacks that were deployed with AWS CDK V1 (as opposed to V2). We can use this to help with the migration process from V1 to V2.

[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.

[robertd]

Even though your global version of CDK is 2.x, your dependencies are still referencing 1.x version of CDK.

…

On Mon, Feb 20, 2023 at 6:46 AM s-nt-s ***@***.***> wrote: I am getting this message: 19836 AWS CDK v1 End-of-Support June 1, 2023 Overview: AWS CDK v1 is currently in maintenance mode. Support for AWS CDK v1 will end entirely on June 1, 2023. Migrate to AWS CDK v2 to continue to get the latest features and fixes! Affected versions: framework: 1.*, cli: 1.* More information at: #19836 but I think I am using the last version: $ cdk --version 2.65.0 (build 5862f7a) $ python --version Python 3.8.0 $ cat requirements.txt aws-cdk.aws-cloudfront==1.193.0 aws-cdk.core==1.193.0 am I missing something? — Reply to this email directly, view it on GitHub <#19836 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAHWN5ZGOHQEUPFLPP5XC3WYNKSFANCNFSM5S5SUCBA> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[Mickael-van-der-Beek]

We're seeing issues with CDKv2 producing different hashes for exported cross-stack references preventing us from migrating.

Any tips on how to handle this? This currently prevents us from migrating to CDKv2.

cf: #20650

[Aarbel]

This is a big problem as V2 does only run on recent version of node, on which not all of javascript packages run.

AWS should be less pressed to change versions like that.

Node V14 with V1 was LTS in 2021... only two years.

[GreatEarl]

is CDK v1 still deployable?

(deployment doesn't pick up changes)

[ArsalanDotMe]

It is still deployable.