Database Migration Service는 대상 인스턴스의 공개 또는 비공개 IP 주소에 연결할 수 있습니다. 이 페이지에서는 사용 가능한 각 대상 데이터베이스 연결 방법에 대한 개요와 마이그레이션에 적합한 솔루션을 선택하는 데 도움이 되는 추천 섹션을 제공합니다.
Database Migration Service는
Private Service Connect를 사용하여 비공개 IP 주소를 사용하여 대상 Cloud SQL 인스턴스에 연결합니다.
Private Service Connect를 사용하면 수신되는 보안 연결에 대상 데이터베이스를 노출하고 데이터베이스에 액세스할 수 있는 사용자를 제어할 수 있습니다.
이 연결은 Database Migration Service에서 암호화합니다.
Private Service Connect의 네트워크 아키텍처 설정은 PSC 지원 대상 Cloud SQL 인스턴스를 사용하는지 또는 PSC 지원 대상이 아닌 Cloud SQL 인스턴스를 사용하는지에 따라 다릅니다.
PSC 지원 Cloud SQL 인스턴스의 경우
대상 Cloud SQL 인스턴스에 비공개 IP 연결을 사용하는 가장 쉬운 방법은 PSC 지원 Cloud SQL 인스턴스를 만드는 것입니다.
그림 2. 이전 네트워킹 예: 공개 IP 소스 연결 (확대하려면 클릭)
PSC 지원 인스턴스의 요구사항
PSC 지원 Cloud SQL 인스턴스를 사용하려면 PSC가 사용 설정된 대상 인스턴스를 만들어야 합니다. 다음과 같은 제한사항이 적용됩니다.
기능 제한사항
PSC 지원 Cloud SQL 인스턴스에는 특정 기능 제한사항이 있습니다. 이러한 구성이 요구사항을 충족하는지 확인합니다. Cloud SQL 문서의
Private Service Connect 제한사항을 참고하세요.
만들기 제한사항
gcloud 또는 Cloud SQL API를 사용하여야만 PSC 지원 Cloud SQL 인스턴스를 만들 수 있습니다.
PSC 지원 Cloud SQL 인스턴스를 대상 데이터베이스로 사용할 수 없는 경우에도 비공개 IP 연결을 사용할 수 있습니다. 이 구성은 데이터베이스 마이그레이션 서비스와 대상의 비공개 IP 간에 트래픽을 전달하기 위해 네트워크에 추가 배스천 가상 머신 (VM)이 필요하므로 더 복잡합니다.
그림 3. 이전 네트워킹 예: 공개 IP 소스 연결 (확대하려면 클릭)
PSC 지원이 아닌 인스턴스의 요구사항
PSC가 사용 설정되지 않은 Cloud SQL 인스턴스의 비공개 IP 연결에는 다음이 필요합니다.
서비스 연결: 대상 Cloud SQL 비공개 IP를 Google Cloud VPC 네트워크의 다른 서비스에 노출하는 네트워크 리소스입니다.
서비스 연결을 만드는 Google Cloud 프로젝트가 서비스 제작자입니다. 서비스 소비자는 Database Migration Service입니다.
PSC 전달 규칙: 서비스 연결에서 수신 트래픽을 전용 배스천 VM으로 라우팅하는 규칙입니다.
배스천 VM: 네트워크 인터페이스 컨트롤러(NIC)가 2개인 Compute Engine VM입니다. 하나는 전용 서비스 연결 네트워크에 연결되고 다른 하나는 PostgreSQL용 Cloud SQL이 피어링된 네트워크에 연결됩니다. 배스천 VM은 Dante SOCKS 서버를 실행하여 연결을 전달합니다.
[[["이해하기 쉬움","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-18(UTC)"],[],[],null,["# Networking methods for destination database connectivity\n\nDatabase Migration Service can connect to your destination instance's public or private IP\naddress. This page provides an overview of each available destination database\nconnectivity method, as well as a recommendation section to help you choose\nthe right solution for your migration:\n\n- [Method comparison](#methods-comparison) provides a comparison table for available\n destination connectivity methods.\n\n- [Public IP connectivity](#public-ip) describes destination connectivity over\n public internet.\n\n- [Private IP connectivity](#private-ip) explains how Database Migration Service uses\n Private Service Connect to connect to the private IP of your\n destination instance.\n\nAfter you familiarize yourself with different connectivity methods and their\nrequirements, you can use the\n[decision tree diagram](#decision-tree) to pick the right solution for your scenario.\n\nMethod comparison\n-----------------\n\nEvery destination connectivity method comes with different benefits and requirements.\nUse the following table to compare them at a glance, and then learn more\ndetails in the sections dedicated for each method.\n\nPublic IP connectivity\n----------------------\n\nWhen you use the public IP connectivity method, Database Migration Service attempts\nto establish a connection to the public IP address of your destination\nCloud SQL instance. This connection is encrypted and secured\nby Database Migration Service.\n[](#lightbox-trigger) **Figure 1.** Migration networking example: public IP destination connectivity. (click to enlarge)\n\n### Requirements for public IP connectivity\n\nTo use this connectivity method you need to ensure that your destination\nCloud SQL instance has a public IP address enabled. For more information, see\n[Configure public IP](/sql/docs/postgres/configure-ip) in the Cloud SQL for PostgreSQL documentation.\n\n### Configure IP allowlist connectivity\n\nConfiguring public IP connectivity is covered in\n[Configure public IP connectivity](/database-migration/docs/oracle-to-postgresql/configure-dst-connection-public-ip).\n\nPrivate IP connectivity\n-----------------------\n\nDatabase Migration Service uses [Private Service Connect](/vpc/docs/private-service-connect) to connect to your destination\nCloud SQL instance using a private IP address.\nWith Private Service Connect, you can expose your destination\ndatabase to incoming secure connections, and control who can access the database.\nThis connection is encrypted by Database Migration Service.\n\nNetwork architecture setup for Private Service Connect differs\ndepending on whether you use a PSC-enabled or a non-PSC-enabled destination\nCloud SQL instance.\n\n### For PSC-enabled Cloud SQL instances\n\nThe easiest way to use private IP connectivity for destination Cloud SQL\ninstances is to create a PSC-enabled Cloud SQL instance.\n[](#lightbox-trigger) **Figure 2.** Migration networking example: public IP source connectivity. (click to enlarge)\n\n#### Requirements for PSC-enabled instances\n\nTo use PSC-enabled Cloud SQL instances, you need to create the destination\ninstance with PSC enabled. The following limitations apply:\n\n- **Functionality limitations**\n\n PSC-enabled Cloud SQL instances come with\n certain functionality limitations. Make sure such configurations meet your\n requirements. See\n [Private Service Connect limitations](/sql/docs/postgres/configure-private-service-connect#limitations) in Cloud SQL\n documentation.\n- **Creation limitations**\n\n You can create PSC-enabled Cloud SQL instances only with\n `gcloud` or the Cloud SQL API.\n\n#### Configure private connectivity for PSC-enabled instances\n\nConfiguring private IP connectivity is covered in\n[Configure private IP connectivity for PSC-enabled instances](/database-migration/docs/oracle-to-postgresql/configure-dst-connection-private-ip#psc-enabled).\n\n### For non-PSC-enabled instances\n\nYou can use private IP connectivity even if you can't use a PSC-enabled\nCloud SQL instance as your destination database. The configuration is more\ncomplex, as it requires an additional bastion virtual machine (VM) in your\nnetwork to forward traffic between Database Migration Service and your destination's\nprivate IP.\n[](#lightbox-trigger) **Figure 3.** Migration networking example: public IP source connectivity. (click to enlarge)\n\n#### Requirements for non-PSC-enabled instances\n\nPrivate IP connectivity for non-PSC-enabled Cloud SQL instances\nrequires the following:\n\n- You need to have a [Virtual Private Cloud network with private services access enabled](/vpc/docs/configure-private-services-access).\n\n This is the network that you peer with your Cloud SQL destination instance.\n- Your destination Cloud SQL must have private IP enabled.\n\n- Additionally, you need to be able to create the following network components\n in your project:\n\n - A service attachment: A network resource that exposes destination\n Cloud SQL private IP to other services in a Google Cloud VPC network.\n The Google Cloud project where you create the service attachment is\n the *service producer* . The *service consumer* is Database Migration Service.\n\n - PSC forwarding rules: A rule that routes the incoming traffic\n from the service attachment to the dedicated bastion VM.\n\n - A bastion VM: A Compute Engine VM with two network interface controllers\n (NICs). One is attached to the dedicated service attachment network; the other,\n to the network where Cloud SQL for PostgreSQL is peered. The bastion VM runs\n a Dante SOCKS server to forward the connections.\n\n#### Configure private connectivity for non-PSC-enabled instances\n\nConfiguring private IP connectivity is covered in\n[Configure private IP connectivity for non-PSC enabled instances](/database-migration/docs/oracle-to-postgresql/configure-dst-connection-private-ip#non-psc).\n\nDestination network connectivity decision tree\n----------------------------------------------\n\nWhen you are familiar with all supported destination connectivity methods\nand their requirements, you can follow the questions in the diagram\nto help you pick the right connectivity method for your scenario.\n**Figure 4.** Destination network connectivity decision tree.\n\nWhat's next\n-----------\n\n- Learn about source database connectivity. See\n [Networking methods for source database connectivity](/database-migration/docs/oracle-to-postgresql/networking-methods-source).\n\n- To get a complete, step-by-step migration walkthrough, see\n [Oracle to Cloud SQL for PostgreSQL migration guide](/database-migration/docs/oracle-to-postgresql/guide)."]]
