[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["難以理解","hardToUnderstand","thumb-down"],["資訊或程式碼範例有誤","incorrectInformationOrSampleCode","thumb-down"],["缺少我需要的資訊/範例","missingTheInformationSamplesINeed","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間:2025-05-15 (世界標準時間)。"],[[["In migration scenarios where direct connectivity between source and destination databases is not possible, a TCP proxy VM is recommended for routing traffic."],["Database Migration Service can generate a script to automate the setup of a Compute Engine VM instance, which acts as a transparent TCP proxy, within the same project and VPC as the destination database."],["When setting up connectivity, users can select \"Proxy via cloud-hosted VM - TCP\" and specify the Compute Engine VM's configuration, such as name, machine type, and subnetwork."],["By default, the proxy VM is assigned both private and public IP addresses, but users can configure it with only a private IP by enabling Private Google Access and modifying the generated script."],["After setting up the proxy, it's essential to update security settings, such as `pg_hba.conf` or security groups, to accept connections from the TCP proxy's outgoing IP address, and test the connection before creating the migration job."]]],[]]