특정 마이그레이션 시나리오에서는 소스 데이터베이스와 대상 데이터베이스 간에 직접 연결을 설정할 수 없습니다. 이 경우 트래픽 라우팅에 TCP 프록시 VM을 사용하는 것이 좋습니다. Database Migration Service에서 생성한 자동화 스크립트를 사용하여 TCP 프록시 VM을 설정할 수 있습니다.
[[["이해하기 쉬움","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-04-22(UTC)"],[[["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."]]],[]]
