- Newest
- Most votes
- Most comments
Here are some ideas:
-
Use the AWS CLI to force delete the clusters. You can use the following command to force delete the clusters:
aws rds delete-db-cluster --profile develop --region us-east-1 --skip-final-snapshot --db-cluster-identifier develop-globaldb-instance-1-cluster --force
aws rds delete-db-cluster --profile develop --region ap-southeast-2 --skip-final-snapshot --db-cluster-identifier snowflake-cluster --force
-
Use the AWS CloudFormation template to delete the clusters. You can use the following AWS CloudFormation template to delete the clusters:
{ "Resources": { "DevelopGlobalDbInstance1Cluster": { "Type": "AWS::RDS::DBCluster", "Properties": { "DBClusterIdentifier": "develop-globaldb-instance-1-cluster", "Engine": "MySQL", "EngineVersion": "5.6.10a", "Region": "us-east-1", "DeletionPolicy": "ForceDelete" } }, "SnowflakeCluster": { "Type": "AWS::RDS::DBCluster", "Properties": { "DBClusterIdentifier": "snowflake-cluster", "Engine": "MySQL", "EngineVersion": "5.6.10a", "Region": "ap-southeast-2", "DeletionPolicy": "ForceDelete" } } } }
-
Use the AWS API to delete the clusters. You can use the following AWS API call to delete the clusters:
DELETE /rds/clusters/develop-globaldb-instance-1-cluster
DELETE /rds/clusters/snowflake-cluster
Note: If you are using the AWS API to delete the clusters, you will need to make sure that you have the appropriate permissions.
-
Contact AWS Support. AWS Support can help you troubleshoot and delete your database clusters.
Hi Marawan, these were great suggestions, thank you! Unfortunately they haven't helped this time.
-
I can't see the
--force
option among the delete-db-cluster parameters, and if I try to use it I get an error that it's not supported. aws-cli v2.11.13 so I think I'm up to date (well I was when I tested this yesterday). -
This looked promising! Unfortunately the stack creation fails with the message "DB cluster isn't available for modification with status incompatible-restore" (status "creating" for the other cluster). So basically the same result as the cli.
-
Both the cli and the console are using the API to perform the task, so I'd say that's where the error is generated.
-
This looks like my next step! Thanks
-
Ended up resolving this through support
Relevant content
- asked 5 years ago
- Accepted Answerasked 9 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 4 years ago
- AWS OFFICIALUpdated 9 months ago
What happens if you let the threatened compulsory upgrades happen? Presumably the upgrades will fail, but it may leave each cluster in a known state (even if that's a known bad state) rather than the inconclusive/unknown states they are in now.
Hey RWC, I guess we're going to find out!