CloudFormation error: DB cluster isn't available for modification with status modifying
I am getting the following error in CloudFormation when deploying a stack:
DB cluster isn't available for modification with status modifying. (Service: Rds, Status Code: 400, Request ID: 26f5ddfb-f2b2-49bc-94e9-8a1690956718)
The condition is that the RDS cluster is Serverless v1 (PostgreSQL) and it is auto-scaling.
However, the update is only applying tag changes.
IMO, tag changes shall not be prevented by cluster scaling.
Can someone escalate this with the right team, please?
EDIT: Ok, I think there is something more going on. I have deleted the tags that are volatile (build IDs) and deployed from local to clear out those tags. It worked. Then I pushed it thru the pipeline, at which point there should be no changes (no diff), and yet, it still fails with the same error message.
- Newest
- Most votes
- Most comments
Relevant content
- Accepted Answerasked a year ago
- asked 10 months ago
- asked 6 years ago
AWS OFFICIALUpdated 2 years ago- AWS OFFICIALUpdated 15 days ago
- AWS OFFICIALUpdated a year ago
I have no solution for you unfortunately, but I can commiserate. I'm getting the same thing with Aurora mysql serverless. Initially I thought it was due to my stack having drifted, however after making sure the cluster aligned with my stack I'm still seeing the same error. I'm able to make manual changes via the Cloudformation console but not via CI pipeline which is running a stack update.