Durante la migración de la base de datos, la base de datos de destino debe conectarse a la base de datos de origen. Database Migration Service proporciona varias formas de configurar esta conectividad. El método de conectividad que elijas dependerá del tipo de base de datos de origen y de si reside de forma local, en Google Cloudo en otro proveedor de servicios en la nube.
Puedes configurar los siguientes métodos de conectividad:
Túnel de SSH inverso con una VM alojada en la nube: Elige este método si deseas usar conectividad segura y cuando no tengas una red de nube privada virtual (VPC) en Google Cloud desde la que puedas acceder a la base de datos de origen.
Conectividad privada: Elige este método si deseas que la base de datos de destino se conecte a la IP privada de tu fuente. Existen dos tipos de conectividad privada disponibles:
Interfaces de Private Service Connect:
Este método de conectividad permite que tu base de datos de destino inicie
conexiones a la IP privada de tu base de datos de origen
sin consumir la cuota de interconexión. En cambio, las interfaces de Private Service Connect usan adjuntos de red que creas en tu VPC.
Intercambio de tráfico entre VPC: Este método requiere que tengas una red de VPC en
Google Cloud desde la que puedas acceder a la base de datos de origen.
Usa el intercambio de tráfico entre VPCs si tienes una conexión de VPN o Cloud Interconnect configurada en Google Cloud.
Proxy TCP a través de VM alojada en la nube: Elige este método cuando migres desde una
instancia de Cloud SQL para PostgreSQL que use la arquitectura de red de productor anterior.
[[["Fácil de comprender","easyToUnderstand","thumb-up"],["Resolvió mi problema","solvedMyProblem","thumb-up"],["Otro","otherUp","thumb-up"]],[["Difícil de entender","hardToUnderstand","thumb-down"],["Información o código de muestra incorrectos","incorrectInformationOrSampleCode","thumb-down"],["Faltan la información o los ejemplos que necesito","missingTheInformationSamplesINeed","thumb-down"],["Problema de traducción","translationIssue","thumb-down"],["Otro","otherDown","thumb-down"]],["Última actualización: 2025-09-05 (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)."]]
