[[["이해하기 쉬움","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-08-22(UTC)"],[[["\u003cp\u003eDatabase Migration Service requires establishing connectivity between the source database and the Cloud SQL destination instance for successful migration.\u003c/p\u003e\n"],["\u003cp\u003eThe IP allowlist method involves configuring the source database to accept connections from the Cloud SQL instance's outgoing IP address, and is recommended for short-lived migrations.\u003c/p\u003e\n"],["\u003cp\u003eReverse-SSH tunnel via cloud hosted VM method creates a secure connection from the destination to the source, requiring a bastion host VM and is also preferred for short lived migrations.\u003c/p\u003e\n"],["\u003cp\u003eVPC peering involves configuring VPCs to communicate with each other, and is ideal for long-running or high-volume migrations, but works if both databases are hosted in google cloud or are connected to the same VPC.\u003c/p\u003e\n"]]],[],null,["# Networking methods\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n[MySQL](/database-migration/docs/mysql/networking-methods \"View this page for the MySQL version of Database Migration Service.\") \\| PostgreSQL \\| [PostgreSQL to AlloyDB](/database-migration/docs/postgresql-to-alloydb/networking-methods \"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\nTo create a migration in Database Migration Service, connectivity must be established between the source instance and the Cloud SQL destination instance. There are various methods supported. Choose the one that works best for the specific workload."]]
