'How to prevent AWS RDS instances from changing AZs after Multi AZ true/false
I have an RDS instance that has a waiting required OS update, So I decided to open Multi AZ while applying the update. Update is finished, everything is fine, but I realized that AWS RDS instance is staying in us-east-1b, I was using us-east-1a. I closed the Multi AZ and configured DB as single AZ again, but my AZ config wasn't be applied back. it's still in us-east-1b. However, most of my resources are in us-east-1a and I don't want to pay for extra inter-AZ networking cost.
Is there a workaround for this,
Any help will be highly appreciated, Thank you very much.
amazon-web-services
amazon-rdsSolution 1:[1]
AWs doesn't give the option to choose in which zone to create seconday rds. If you can have a maintenace period of let's say 1 hour(depends on how big is the RDS), you can create the db from snapshot in the AZ of your choice but if it's not possible, the only option is to change to MultiAZ and hope the secondary DB is created in us-east-1a. Once you have it here, turn off MultiAZ.
Solution 2:[2]
- Tur on multiAZ again
- Restart database with force failover parameter. https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_RebootInstance.html
- Turn off multiAZ
Solution 3:[3]
You can create DB subnet zone in your preferred AZ, then create a snapshot of your database. From the snapshot you can restore a new database and assign the create subnet group while restoring that database which will create your instance in AZ of your choice. Hope this resolves your issue!
Sources
This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.
Source: Stack Overflow
| Solution | Source |
|---|---|
| Solution 1 | Riz |
| Solution 2 | Tomasz Bre? |
| Solution 3 | Kavish Baghel |