将 RDS Aurora 实例从私有迁移到公共 su.net

Question

I currently have the typical setup of an RDS cluster with 1 instance running in a private su.net. I am migrating our application out of AWS and into Heroku (while leaving the DB as is), but I need to be able to connect to the DB from the Heroku dynos.

What I can't figure out is how to move the DB out of the private su.net and into a public one.

The AWS docs have instructions for moving from public to private, and I thought I could just follow them for the opposite direction too. But the process involves standing up a new secondary in the desired su.net using Multi-AZ configuration and a failover. But when I go to Modify my instance, there is no option for configuring Multi-AZ:

It seems like Aurora instances in particular do not support Multi-AZ? "Multi-AZ DB clusters are in preview for RDS for MySQL and RDS for PostgreSQL" Leaving me somewhat stuck.

Edit I did just see this message elsewhere: "You have no Aurora Replicas in your DB cluster." which might be why Multi-AZ is not available. But I'm not seeing any options to spin up a replica anywhere.

Again my goal is to get my Aurora DB into a public su.net (or otherwise make it accessible from the inte.net, but not through an SSH tunnel)

Answer 1

The Availability Zone options are in the "Availability & durability" section above "Connectivity" FYI

I just had your same issue but with a Postgres DB, though I have the option to change its "Su.net group" in the Connectivity section , which you don't have it seems, but it only appears for me if the DB is NOT currently multi-AZ. AWS will prevent you from moving the DB between su.net groups* in the same VPC, but you can just move the DB to a su.net group in a different VPC and then move it back to the su.net group that you actually want it in (configured with the appropriate public su.nets).

*You can create su.net groups in the RDS service, left side menu.