Aurora Serverless v1 cluster (end of life)
What it checks
Aurora Serverless v1 cluster (end of life)
Where it applies
Terraform: aws_rds_cluster
CloudFormation: AWS::RDS::DBCluster
How to fix it
- Check Serverless v2 engine-family, version and Region support. Upgrade if the current version is below its supported minimum; a MySQL 5.7-compatible family needs a supported newer family, whereas a supported PostgreSQL version does not necessarily need a major upgrade. Do not blindly copy a v1 engine_version into the migration configuration.
- Plan and test ModifyDBCluster in-place conversion from serverless to provisioned with the required engine-mode-change authorization, or restore a snapshot into a compatible cluster. Terraform engine_mode and CloudFormation EngineMode edits can require replacement; do not apply a bare mode swap as a migration. Reconcile IaC and state with the chosen migration before applying a reviewed deployment plan.
- Remove the v1 scaling block and configure serverlessv2_scaling_configuration / ServerlessV2ScalingConfiguration with supported capacities. Create a supported instance_class / DBInstanceClass: db.serverless writer, or validate a serverless reader and plan failover. Review client endpoints, backups and rollback before switching production traffic.
Frameworks
- AWS Well-Architected REL.5
These mappings are advisory, not an attestation of compliance.