Overview
Public IP connectivity is most appropriate when the source database is external to Google Cloud and has an externally accessible IPv4 address and TCP port. If the source database is hosted in another VPC in Google Cloud, then the easiest way to connect the source database with the Cloud SQL instance is by using VPC Peering.
If your source database is external to Google Cloud, then add the destination database's outgoing IP address (and port 5432) as an inbound firewall rule on the source network. In generic terms (your specific network settings may differ), do the following:
Open the source database machine's network firewall rules.
Create an inbound rule.
Set the Rule type to
PostgreSQL.Set the Protocol to
TCP.Set the Port range to 5432.
Set the Source IP address to the destination database's outgoing IP address. For example:
12.20.36.126/32. (The /32 designation in CIDR notation limits the address range to one address only, the one provided. It's setting the subnet mask to255.255.255.255). If the Cloud SQL instance you created is a high availability instance, include the outgoing IP addresses for both the primary and the secondary instance.You can use the SQL Instances page in the Google Cloud Console to locate the outgoing IP addresses.
Update the
pg_hba.conffile or AWS RDS security groups to accept connections from this IP address.Save the firewall rule and exit.
It's also highly recommended to use SSL/TLS during the definition of the source connection profile so that the data sent to and received by the source is secure.
Learn more about SSL/TLS certificates for PostgreSQL.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-03-21 UTC.