- Newest
- Most votes
- Most comments
To move an Amazon RDS instance from one availability zone to another, you can use the following steps:
- Pick an outage window with minimal impact to users. Take a snapshot of your RDS instance.
- Create a new RDS instance in the desired availability zone using the snapshot you just created.
- Verify that the new RDS instance was created successfully and is working as expected.
- When you are ready to switch to the new RDS instance, change your application's configuration to point to the new RDS instance, and then stop the original RDS instance.
- If you want to delete the original RDS instance, you can do so once you are sure you no longer need it.
Note that while the RDS instance is being moved, your application may be unavailable. It is important to plan this operation during a maintenance window to minimize the impact on your users.
Why dont you change the region of the EC2 instance? Ideally, you can create a snapshot out of the EC2 and then an AMI. Through that you can create the same EC2 in the region where you have your database.
You mentioned, that your RDS is already Multi-AZ. I think you can see in what AZ your standby instance is and run promotion or failover, so the standby instance will be a new standby instance.
Or you can create a read replica in ap-northeast-1a
AZ, and once replication lag is zero, you can promote it to a new primary instance. No downtime required. Just not forget to change RDS endpoints in your app.
Let me know if you have any questions.
Check out this official Knowledge Center article: https://repost.aws/knowledge-center/rds-move-availability-zone
Relevant content
- asked 6 months ago
- asked a year ago
- AWS OFFICIALUpdated 2 days ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
There are six EC2 instances connect to this RDS instance, so I thought maybe simple to change one instead of six.