search

aws-cloudformation / cloudformation-coverage-roadmap

The AWS CloudFormation Public Coverage Roadmap
https://aws.amazon.com/cloudformation/
Creative Commons Attribution Share Alike 4.0 International
1.11k stars 56 forks source link

DBCluster Allow Engine Mode Change #1743

Open mattfirtion opened 1 year ago

mattfirtion commented 1 year ago

Name of the resource

AWS::RDS::DBCluster

Resource name

No response

Description

The migration from Aurora Serverless V1 to V2 requires the DBCluster be changed from serverless to provisioned. This can be completed using the AWS CLI using the --allow-engine-mode-change option. This does not require a replacement of the resource, just an interruption. Cloudformation should also allow for an engine mode change without requiring a replacement to support the migration from serverless v1 to v2.

Other Details

No response

s0enke commented 10 months ago

While waiting for this, I have documented a workaround here: https://ruempler.eu/2023/12/31/upgrade-aws-aurora-serverless-v1-to-v2-cloudformation-cdk/

FlorianSW commented 10 months ago

I know there is a bit of time left here, however, is there already a plan or roadmap of when the upgrade path from V1 to V2 will be available in Cloud formation? Just want to make sure if it is coming sooner than later and if we would need to find alternatives (like the workaround which was already posted).

abatkin commented 9 months ago

Also please allow changing from "global" to "provisioned" (since it literally does nothing)

matthiasa4 commented 5 months ago

Also curious about this becoming available!

mdecamillis-mpr commented 3 months ago

Is there a reason this was moved from "Coming Soon" back to "Researching" after almost a year?

We're really hoping this becomes available to facilitate our serverless v1->v2 migration within CloudFormation without having to resort to user-created workarounds.

mahe-work commented 2 weeks ago

Aurora v1 to v2 deadline is fast approaching and this is a blocker for anyone having CDK / Cloudformation deployed clusters who is not willing to jump the hoops of exporting/importing resources from their db stacks, which is a total PITA to be blunt. I'm frankly disappointed in lack of AWS activity on this ticket. We've approached AWS through business support and our contacts but apparently we're not going to get a solution...