A conetividade de IP público é mais adequada quando a base de dados de origem é externa a Google Cloud
e tem um endereço IPv4 e uma porta TCP acessíveis externamente. Se a base de dados de origem estiver alojada noutra VPC no Google Cloud, a forma mais fácil de ligar a base de dados de origem à instância do Cloud SQL é usar o VPC Peering.
Se a base de dados de origem for externa ao Google Cloud, adicione o endereço IP
de saída (e a porta 3306) da base de dados de destino como uma regra de firewall de entrada na rede de origem. Em termos gerais (as definições de rede específicas podem ser diferentes), faça o seguinte:
Abra as regras de firewall de rede da máquina da base de dados de origem.
Crie uma regra de entrada.
Defina o tipo de regra como MySQL.
Defina o protocolo como TCP.
Defina o intervalo de portas para 3306.
Defina o endereço IP de origem como o endereço IP de saída da base de dados de destino. Por exemplo:
12.20.36.126/32. (A designação /32 na notação CIDR limita o intervalo de endereços a apenas um endereço, o fornecido. Está a definir a máscara de sub-rede para 255.255.255.255. Se a instância do Cloud SQL que criou for uma instância de alta disponibilidade, inclua os endereços IP de saída para a instância principal e a secundária.
Também é altamente recomendável usar SSL/TLS durante a definição do perfil de ligação de origem para que os dados enviados e recebidos pela origem sejam seguros.
Saiba mais acerca dos certificados SSL/TLS para o MySQL.
[[["Fácil de entender","easyToUnderstand","thumb-up"],["Meu problema foi resolvido","solvedMyProblem","thumb-up"],["Outro","otherUp","thumb-up"]],[["Difícil de entender","hardToUnderstand","thumb-down"],["Informações incorretas ou exemplo de código","incorrectInformationOrSampleCode","thumb-down"],["Não contém as informações/amostras de que eu preciso","missingTheInformationSamplesINeed","thumb-down"],["Problema na tradução","translationIssue","thumb-down"],["Outro","otherDown","thumb-down"]],["Última atualização 2025-08-21 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."]]
