Configure network connectivity for Amazon Aurora and Amazon RDS sources

This page describes how to configure network connectivity for Amazon Aurora and Amazon RDS sources for homogeneous migrations to Cloud SQL for MySQL migrations with Database Migration Service. There are several methods you can use:

Configure Private Service Connect interfaces

To use private connectivity with Private Service Connect interfaces for Amazon RDS or Amazon Aurora sources, follow these steps:

  1. Set up direct connectivity with Cloud VPN from Google Cloud to your source VPC.

    Depending on your network architecture, you might need to set up additional VPN gateways in your system. For more information, see Create HA VPN connections between Google Cloud and AWS in the Cloud VPN documentation.

  2. Create a destination Cloud SQL instance enabled for Private Service Connect. See Create a Private Service Connect-enabled instance in the Cloud SQL documentation.
  3. Configure Private Service Connect for outbound connectivity on your instance. At a high level, this process involves:
    1. Creating a network attachment in the VPC network where you set up your Cloud VPN. Note that the subnet range reserved for the network attachment must be within RFC 1918 range.
    2. Assigning the network attachment to your destination Cloud SQL for MySQL instance.

    For the full process, see Configure outbound connectivity in the Cloud SQL documentation.

  4. At a later stage, when you create the source connection profile use the private IP address of your source database instance.
  5. When you create the migration job select PSC interface for your connectivity method.

Configure VPC peering

To use private connectivity with Virtual Private Cloud peering for Amazon RDS or Amazon Aurora sources, follow these steps:

  1. Set up direct connectivity with Cloud VPN from Google Cloud to your source VPC.

    Depending on your network architecture, you might need to set up additional VPN gateways in your system. For more information, see Create HA VPN connections between Google Cloud and AWS in the Cloud VPN documentation.

    Ensure the Virtual Private Cloud network is configured for private services access. For more information, see Configure private services access.

  2. Make sure your destination Cloud SQL instance is configured with a private IP and Private Service Access (PSA). For more information, see Use private IP in the Cloud SQL documentation.
  3. At a later stage, when you create the source connection profile use the private IP address of your source database instance.
  4. When you create the migration job select VPC Peering for your connectivity method.

Configure IP allowlist connectivity

To use the public IP allowlist connectivity method, follow these steps:

  1. Enable public IP for your destination Cloud SQL instance. Enable public IP in the Cloud SQL documentation.

    If you are migrating to a new destination instance, make sure to create the destination with a public IP enabled.

  2. In the AWS Management Console, perform the following steps:
    1. Ensure that your source Amazon RDS database is configured for public IP connections.
    2. Identify the endpoint name and port number. You need to enter these values when you create the connection profile.

  3. Create a security group that allows traffic from the public IP of your destination Cloud SQL instance to your Amazon RDS or Amazon Aurora VPC. See Provide access to your DB instance in your VPC by creating a security group.

  4. At a later stage, when you create the source connection profile use endpoint name for the source database IP.
  5. When you create the migration job select IP allowlist for your connectivity method.

What's next