Overview
To create a migration in the Database Migration Service for MySQL, connectivity must be established between the source instance and the Cloud SQL destination instance. There are various methods supported. Choose the one that works best for the specific workload.
Networking method | Description | Advantages | Disadvantages |
---|---|---|---|
IP allowlist |
This method works by configuring the source database server to accept connections from the outgoing IP of the Cloud SQL instance. If you choose this method, the Database Migration Service for MySQL guides you through the setup process during the migration creation. |
|
|
Reverse SSH tunnel through cloud-hosted VM |
Establishes connectivity from the destination to the source through a secure reverse SSH tunnel. Requires a bastion host VM in the GCP project as well as a machine (for example, a laptop on the network) that has connectivity to the source. The Database Migration Service for MySQL collects the required information at migration creation time, and auto-generates the script for setting it all up. |
|
|
VPC-peering |
This method works by configuring the VPCs to communicate with one another. |
|
|
VPN | This method works by configuring an IPSec VPN tunnel, and connecting the source network and Google Cloud VPC through a secure connection over the public Internet. Uses Google Cloud VPN or any VPN solution that is set up for the internal network. |
|
|
Cloud Interconnect | Uses a highly available, low latency connection between the on-premises network and Google Cloud. |
|
|