AWS CDK Aurora: Migrating from v1 to v2 with AWS CDK

[TejasRGitHub]

Describe the issue

We have a deployment made with aws cdk and are using aurora serverless v1. We use the cdk code in our deployment pipeline and since it is a part of our deployment pipeline, our infrastructure changes happen through it.

We are getting Aurora V1 deprecation notices and it is planned to be deprecated in March 2025.

Can you please provide information about if there is aws cdk support to migrate to a serverless / provisioned aurora RDS with v2 . Can you please provide any example ?

Currently we are using AWS CDK version - 2.115.0.

Links

I can see there is some work done here - https://github.com/aws/aws-cdk/blob/main/packages/aws-cdk-lib/aws-rds/adr/aurora-serverless-v2.md but I don't know if its available in aws cdk aurora code.

[ashishdhingra]

Following links provide some general guidance for migration:

• Amazon Aurora: Migrating to Aurora Serverless v2
• Upgrade from Amazon Aurora Serverless v1 to v2 with minimal downtime

CCing @pahud for any CDK specific guidance.

[pahud]

Hi

Aurora Serverless V1 and V2 are very different by design and we don't have official CDK guidance on migrating this and I doubt it's possible to just in-place migrate it from CDK.

Please consult the document links above by @ashishdhingra thank you.

[TejasRGitHub]

Hi @pahud , @ashishdhingra , thanks a lot for the info

We have our entire pipeline's CF template generated with aws cdk. There are cross references from our aurora cdk code to other parts of infrastructure.

Could you please recommend a path in which we can migrate to aurora v2 and also keep on using the aws cdk ( in our code pipeline ) to perform deployments ?

[RichardSieg]

We are also following the tutorial for migrating from V1 to V2 with CDK in combination with the CLI.

However, we are stuck at Step 2: "cdk import". Without --force we get an error that update/delete operations are not allowed and with --force we get a message that the stack is ignored. The CloudFormation template also just stays with the serverless engine. cdk import however imports the newly created instance but does not update the cluster to provisioned.

What are we missing here?

[modul]

Any updates on this? Is it at least possible to create a new V2-instance/cluster with CDK and then use that as a target to manually migrate to?