Help Center/ Data Replication Service/ User Guide (Ankara Region)/ Preparations/ From the Public Cloud to the Public Cloud/ Accessing the Public Cloud Through a VPN (Different Regions)
Updated on 2024-04-11 GMT+08:00
View PDF
Share

Accessing the Public Cloud Through a VPN (Different Regions)

Figure 1 shows how to use DRS to migrate data across databases in different regions over a VPN network on the public cloud.

Figure 1 Network diagram

If you use DRS to access a cross-region database through a VPN, create the VPN service on the public cloud in Region-B and configure the VPC and subnet associated with the DRS replication instance. In addition, create the VPN service in Region-A, configure the VPN peer device, and add inbound rules for the network ACL and security group associated with the source database in Region-A to allow traffic from the private IP address of the replication instance. Then, configure outbound rules for the network ACL and security group associated with the replication instance in Region-B to allow outbound traffic. Figure 2 shows the process.

Figure 2 Flowchart

Network Configurations

  1. Create a DRS instance and obtain the subnet and private IP address of the DRS instance.

    By default, the DRS instance is in the same subnet as the destination database.

    After the DRS replication instance is created, the private IP address of the replication instance is displayed.

  2. Query the name of the VPC to which the DRS instance belongs.

    By default, the DRS replication instance and the destination RDS database are created in the same VPC. You can log in to the destination RDS instance to view information about the VPC where the replication instance is located.

  3. Create a VPN in the target region and configure the VPN gateway and connection.

    For details, see Virtual Private Network User Guide.

    When you create a VPN gateway, configure the VPC by referring to the VPC information obtained in 2. When you create a VPN connection, configure the subnet associated with the replication instance by referring to the subnet information obtained in 1.

  4. Create a VPN in the source region and configure the VPN peer device.

    For details, see Virtual Private Network User Guide.

  5. Configure inbound rules for the network ACL and security group associated with the source database.

    Security group: Add an inbound rule to allow traffic from the private IP address of the DRS replication instance to the database listening port.

    Network ACL: By default, a VPC does not have a network ACL. If you have a network ACL, add an inbound rule to allow traffic from the private IP address and random port of the DRS replication instance to the IP address and listening port of the source database.

  6. Configure outbound rules for the network ACL and security group associated with the replication instance.

    By default, a VPC does not have a network ACL, and the default security group rules allow all outbound traffic. The replication instance and destination RDS database in the same security group can communicate with each other by default, so you do not need to configure a network ACL.

    If you have configured a network ACL or security group, log in to the VPC management console and check the settings:

    Security group: Ensure that the outbound traffic from the security group associated with the replication instance to the IP address and listening port of the source database is allowed.

    Network ACL: Ensure that the outbound traffic from the VPC where the replication instance resides and the DRS random port to the IP address and listening port of the source database is allowed.

  7. Test the connection.

    Log in to the DRS console, locate the created DRS task, and click Edit in the Operation column. On the Configure Source and Destination Databases page, enter the IP address, port, username, and password of the source database and then click Test Connection to check whether the connection is successful.