This is not a bug. This error is as a result of not having enough of the chosen instance class in the chosen availability zone at the time of request . When the issue occurs, our internal team works at the backend to increase the capacity so that you will be able to create the instance later on.
Having said that, below could be the potential workarounds.
- Wait a while and then try again after a few minutes; capacity can shift frequently.
- Create instances in a different availability zone. (This applies when you creating a new instance)
- Try to scale up/down to a different instance class.
Refactoring from Oracle to postgres, Do I need to drop foreign key constraitns at postgresasked 3 months ago
d3.micro Postgres RDS resetting instance every dayasked 2 months ago
Can't Modify RDS Postgres "R6i" Stand-Alone instance to Multi-AZ, Failsasked 8 days ago
RDS modify instance not workingasked 2 months ago
Issues connecting to Postgres RDS instance from within a VPCasked 3 years ago
How to export / import rows reliably from one MySQL RDS server to anotherasked 3 months ago
How to create SSL dblink connection from RDS to postgres on premise?asked 8 months ago
Cannot modify Postgres RDS instance class in us-east-1easked 9 months ago
Can I import an RDS uncrypted mysql snapshot to an RDS encrypted mysql?Accepted Answerasked 6 months ago
Cannot modify RDS instanceasked 3 months ago