Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from http://cloud.google.com/database-migration/docs/postgresql-to-alloydb/configure-connectivity below:

Configure connectivity | Database Migration Service

Stay organized with collections Save and categorize content based on your preferences.

During database migration, the destination AlloyDB for PostgreSQL database needs to connect to the source PostgreSQL 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 types of 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.
• VPC peering: Choose this method if you want to use private connectivity, and when 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 which is using the old producer network architecture.

• Learn more about private services access.
• 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-07 UTC.

[[["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-07 UTC."],[[["Database Migration Service requires the destination AlloyDB for PostgreSQL to connect to the source PostgreSQL database."],["The choice of connectivity method depends on the source database type and its location (on-premises, Google Cloud, or another cloud provider)."],["Connectivity 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."],["TCP 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."]]],[]]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4