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.
TCP Proxy via cloud-hosted VM: Choose this method when migrating from a
Cloud SQL for PostgreSQL instance that uses the old producer network architecture.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-25 UTC."],[[["\u003cp\u003eDatabase Migration Service requires the destination AlloyDB for PostgreSQL to connect to the source PostgreSQL database.\u003c/p\u003e\n"],["\u003cp\u003eThe choice of connectivity method depends on the source database type and its location (on-premises, Google Cloud, or another cloud provider).\u003c/p\u003e\n"],["\u003cp\u003eConnectivity options include public connectivity via IP allowlists, secure connectivity via a reverse SSH tunnel using a cloud-hosted VM, and private connectivity via VPC peering.\u003c/p\u003e\n"],["\u003cp\u003eTCP Proxy via a cloud-hosted VM is a connectivity option for migrating from a Cloud SQL for PostgreSQL instance with the old producer network architecture.\u003c/p\u003e\n"]]],[],null,["# Configure connectivity\n\n\u003cbr /\u003e\n\n[MySQL](/database-migration/docs/mysql/configure-connectivity \"View this page for the MySQL version of Database Migration Service.\") \\| [PostgreSQL](/database-migration/docs/postgres/configure-connectivity \"View this page for the PostgreSQL version of Database Migration Service.\") \\| PostgreSQL to AlloyDB\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\nDuring database migration, the destination database needs to connect\nto the source database. Database Migration Service provides several ways to configure\nthis connectivity. The connectivity method you choose depends on the type of\nsource database, and whether it resides on-premises, in Google Cloud, or in another\ncloud provider.\n\nYou can configure the following connectivity methods:\n\n- [IP allowlists](/database-migration/docs/postgresql-to-alloydb/configure-connectivity-ip-allowlists): Choose this method if you want to use public connectivity.\n- [Reverse SSH tunnel using a cloud-hosted VM](/database-migration/docs/postgresql-to-alloydb/configure-connectivity-reverse-ssh-tunnel): 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.\n- 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:\n - [Private Service Connect interfaces](/database-migration/docs/postgresql-to-alloydb/configure-connectivity-vpc-peering#psc-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.\n - [VPC peering](/database-migration/docs/postgresql-to-alloydb/configure-connectivity-vpc-peering#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](/database-migration/docs/postgresql-to-alloydb/configure-connectivity-vpns) or Cloud Interconnect connection set up in Google Cloud.\n- [TCP Proxy via cloud-hosted VM](/database-migration/docs/postgresql-to-alloydb/configure-connectivity-tcp-proxy-via-cloud-hosted-vm): Choose this method when migrating from a Cloud SQL for PostgreSQL instance that uses the old producer network architecture.\n\nWhat's next\n-----------\n\n- Learn more about [private services access](/vpc/docs/private-services-access).\n- Learn more about [Private Service Connect interfaces](/vpc/docs/about-private-service-connect-interfaces).\n- Learn more about [using VPC peering](/vpc/docs/using-vpc-peering)."]]
