[[["이해하기 쉬움","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-09-05(UTC)"],[[["\u003cp\u003eDatabase Migration Service requires establishing connectivity between the source database and the Cloud SQL destination instance for migrations.\u003c/p\u003e\n"],["\u003cp\u003eThe IP allowlist method involves configuring the source server to accept connections from the Cloud SQL instance's outgoing IP, making it easy to configure but less secure.\u003c/p\u003e\n"],["\u003cp\u003eReverse-SSH tunnel via a cloud-hosted VM creates connectivity from the destination to the source through a secure SSH tunnel and is good for short-lived migrations.\u003c/p\u003e\n"],["\u003cp\u003eVPC peering enables VPCs to communicate with each other, offering high bandwidth and is ideal for long-running or high-volume migrations, but only if both the source and destination databases are in Google Cloud or connected to the same VPC.\u003c/p\u003e\n"]]],[],null,["# Networking methods\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\nMySQL \\| [PostgreSQL](/database-migration/docs/postgres/networking-methods \"View this page for the PostgreSQL version of Database Migration Service.\") \\| [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."]]
