Cannot modify db instance when it's state is Available

0

I am trying to increase the storage for a single AZ postgres instance. The current DBInstanceStatus is "available" and there have been no other storage changes for some time, however when trying to resize it, I'm getting the below error

  $ aws rds modify-db-instance --db-instance-identifier dbname --allocated-storage 14644
An error occurred (InvalidParameterCombination) when calling the ModifyDBInstance operation: You can't currently modify the storage of this DB instance because the previous storage change is being optimized.

Has anyone seen this before or know how to fix?

Thanks

asked 5 years ago448 views
5 Answers
0

If this persists I suspect you will need to open a support case. The forums are for community discussion and don't function well for individualized support (though sometimes you do get lucky and an AWS employee intervenes here).

HalTemp
answered 5 years ago
0

While the support case answer is probably correct, paying for the support to tell AWS about a bug on their side is not in the budget. I can work around it if it gets to the critical stage but a quick fix would have been nicer.

answered 5 years ago
0

This is a expected behavior and can be found in the below link-
"https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/CHAP_Storage.html#CHAP_Storage.AddingChanging"

After you modify the storage for a DB instance, the status of the DB instance is storage-optimization. The DB instance is fully operational after a storage modification. However, you can't make further storage modifications for either six hours or while the DB instance status is storage-optimization, whichever is longer.

answered 5 years ago
0

It has been several days now and I'm still getting the same error, which I don't expect. The issue is that I believe is a bug is that the status of the DB instance is "available", usually I have seen it enter that state after "storage-optimization" is complete.

answered 5 years ago
0

I eventually managed to resize the storage by converting the instance to Multi-AZ, then forcing a failover and convert back to single-AZ.

answered 5 years ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions