During database migration, the destination database needs to connect to the source database. Database Migration Service provides several ways to configure this connectivity. The connectivity method you choose depends on the type of source database, and whether it resides on-premises, in Google Cloud, or in another cloud provider.
You can configure the following connectivity methods:
- IP allowlists: Choose this method if you want to use public connectivity.
- Reverse SSH tunnel using a cloud-hosted VM: Choose this method if you want to use secure connectivity, and when you don't have a virtual private cloud (VPC) network in Google Cloud from which you can reach the source database.
- Private connectivity: Choose this method if you want the destination
database to connect to the private IP of your source. There are two types
of private connectivity available:
- Private Service Connect interfaces: This connectivity method lets your destination database initiate connections to the private IP of your source database without consuming peering quota. Instead, Private Service Connect interfaces use network attachments you create in your VPC.
- VPC peering: This method requires that you have a VPC network in Google Cloud from which you can reach the source database. Use VPC peering if you have a VPN or Cloud Interconnect connection set up in Google Cloud.
What's next
- Learn more about private services access.
- Learn more about Private Service Connect interfaces.
- Learn more about using VPC peering.
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-08-18 UTC.