DMS Multi-AZ standby replica IP address
Hi, When deploying DMS in a multi-az configuration, I understand the standby replication instance will be in a different AZ and sat in a different subnet.
In the event the standby replication instance is called into action as per the documentation;
"If the primary replication instance fails or becomes unresponsive, the standby resumes any running tasks with minimal interruption"
I am correct in thinking you can specify the standby replication instance IP address from the subnet of the AZ? -
Reason being is I use DMS within private subnets that connect to a client via a site-to-site vpn, so I often have to specify the subnets in use and also the IP addresses of the replication instance. There is no such thing as a floating or shared private IP for the primary and standby replication instances?
We cannot specify direct ip address but it could be from pool of ipaddress as defined by subnets included to setup the replication instance.
Replication instance is setup using DMS replication subnet group which contains atleast two subnets
Say we have two subnets defined 10.0.1.0/27 (with 32 ips) and 10.0.1.32/27 (32 IPs) then we can open firewall for those total range 10.0.1.0/26 (64 ips)
Postgres Read Replica (in a different region) Stuck in Deleting Stateasked 3 years ago
How can EC2 maintain IP addresses in a multi-AZ failover situation?Accepted Answerasked 2 years ago
AWS DMS doing a SELECT on TEXT column during continuous replicationasked 3 months ago
What happens to a DMS job when a SQL Server AG fails over?Accepted Answerasked 2 years ago
DMS Multi-AZ standby replica IP addressAccepted Answerasked 3 months ago
DMS between MySQL RDS in 2 different accountsasked 11 days ago
How do you connect to a VPC Endpoint when your in a different AZ?asked 6 months ago
CDK DMS replication instanceAccepted Answerasked 2 years ago
DMS instance sizing guidanceAccepted Answerasked 2 years ago
How to estimate size and number of DMS instances for a given number of ongoing replicationsAccepted Answerasked 2 years ago