Konektivitas IP publik paling sesuai jika database sumber bersifat eksternal terhadap Google Cloud
dan memiliki alamat IPv4 dan port TCP yang dapat diakses secara eksternal. Jika database
sumber dihosting di VPC lain di Google Cloud, cara termudah untuk
menghubungkan database sumber dengan instance Cloud SQL adalah dengan menggunakan Peering VPC.
Jika database sumber Anda bersifat eksternal terhadap Google Cloud, tambahkan alamat IP
keluar database tujuan (dan port 3306) sebagai aturan firewall masuk di jaringan sumber. Dalam
istilah umum (setelan jaringan spesifik Anda mungkin berbeda), lakukan hal berikut:
Buka aturan firewall jaringan mesin database sumber.
Buat aturan masuk.
Tetapkan jenis Aturan ke MySQL.
Tetapkan Protocol ke TCP.
Tetapkan Rentang port ke 3306.
Tetapkan alamat IP Sumber ke alamat IP keluar database tujuan. Contoh: 12.20.36.126/32. (Penunjukan /32 dalam notasi CIDR membatasi
rentang alamat hanya ke satu alamat, yaitu alamat yang diberikan. Ini menetapkan mask
subnet ke 255.255.255.255). Jika instance Cloud SQL yang Anda buat
adalah instance ketersediaan tinggi, sertakan alamat IP keluar untuk
instance utama dan sekunder.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-09-05 UTC."],[[["\u003cp\u003ePublic IP connectivity is suitable when the source database is outside Google Cloud and has an externally accessible IPv4 address and TCP port.\u003c/p\u003e\n"],["\u003cp\u003eFor 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.\u003c/p\u003e\n"],["\u003cp\u003eThe source IP address in the inbound rule should be set to the destination database's outgoing IP address, using CIDR notation such as \u003ccode\u003e12.20.36.126/32\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eIf the Cloud SQL instance is high availability, include the outgoing IP addresses for both the primary and secondary instances in the firewall rule.\u003c/p\u003e\n"],["\u003cp\u003eUsing SSL/TLS during source connection profile definition is highly recommended to secure data transmission.\u003c/p\u003e\n"]]],[],null,["# Configure connectivity using IP allowlists\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\nMySQL \\| [PostgreSQL](/database-migration/docs/postgres/configure-connectivity-ip-allowlists \"View this page for the PostgreSQL version of Database Migration Service.\") \\| [PostgreSQL to AlloyDB](/database-migration/docs/postgresql-to-alloydb/configure-connectivity-ip-allowlists \"View this page for the PostgreSQL to AlloyDB version of Database Migration Service.\")\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\nOverview\n--------\n\nPublic IP connectivity is most appropriate when the source database is external to Google Cloud\nand has an externally accessible IPv4 address and TCP port. If the source\ndatabase is hosted in another VPC in Google Cloud, then the easiest way to\nconnect the source database with the Cloud SQL instance is by using VPC Peering.\n\nIf your source database is external to Google Cloud, then add the destination database's **outgoing\nIP address** (and port 3306) as an inbound firewall rule on the source network. In\ngeneric terms (your specific network settings may differ), do the following:\n\n1. Open the source database machine's network firewall rules.\n\n2. Create an inbound rule.\n\n3. Set the Rule type to `MySQL`.\n\n4. Set the Protocol to `TCP`.\n\n5. Set the Port range to 3306.\n\n6. Set the Source IP address to the destination database's **outgoing IP address** . For example:\n `12.20.36.126/32`. (The /32 designation in CIDR notation limits the\n address range to one address only, the one provided. It's setting the subnet\n mask to `255.255.255.255`). If the Cloud SQL instance you created\n is a high availability instance, include the outgoing IP addresses for both\n the primary and the secondary instance.\n\n\n You can use the **SQL Instances** page in the Google Cloud Console to [locate the outgoing IP addresses](/database-migration/docs/mysql/debugging-connectivity#locateoutgoingIPaddress).\n\n \u003cbr /\u003e\n\n7. Save the firewall rule and exit.\n\n| You can test connectivity by adding another, temporary inbound firewall rule using the IP address of your local machine (or `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.\n\nIt's also highly recommended to use SSL/TLS during the definition of the source\nconnection profile so that the data sent to and received by the source is\nsecure.\n[Learn more](/sql/docs/mysql/authorize-ssl) about SSL/TLS certificates for MySQL."]]
