Stay organized with collections Save and categorize content based on your preferences.
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 3306) 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 MySQL.
Set the Protocol to TCP.
Set the Port range to 3306.
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 to 255.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.
Save the firewall rule and exit.
0.0.0.0/0 to allow access from anywhere), and then running the following telnet command: telnet [SOURCE_DB_IP_ADDRESS] 3306. The connection should succeed. Delete the temporary firewall rule.
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 moreabout SSL/TLS certificates for MySQL.
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."],[[["Public IP connectivity is suitable when the source database is outside Google Cloud and has an externally accessible IPv4 address and TCP port."],["For source databases external to Google Cloud, add the destination database's outgoing IP address and port 3306 as an inbound firewall rule on the source network."],["The source IP address in the inbound rule should be set to the destination database's outgoing IP address, using CIDR notation such as `12.20.36.126/32`."],["If the Cloud SQL instance is high availability, include the outgoing IP addresses for both the primary and secondary instances in the firewall rule."],["Using SSL/TLS during source connection profile definition is highly recommended to secure data transmission."]]],[]]
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