이 페이지에서는 비공개 연결 구성을 만드는 방법을 설명합니다.
비공개 연결 구성은 Database Migration Service 서비스 네트워크와 프로젝트의 가상 프라이빗 클라우드 (VPC) 네트워크 간에 피어링 연결을 만드는 데 도움이 되는 Database Migration Service 구조입니다. 비공개 연결 구성을 만들어 소스 Oracle 데이터베이스에 비공개 연결을 설정합니다.
프로젝트 Virtual Private Cloud 네트워크가 있는 동일한 리전을 사용해야 합니다. 마이그레이션 작업과 연결 프로필을 만들려는 리전과 동일해야 합니다. Database Migration Service는 완전한 리전 제품입니다. 즉, 마이그레이션과 관련된 모든 항목 (소스 및 대상 연결 프로필, 마이그레이션 작업, 대상 데이터베이스, 변환 작업공간)을 단일 리전에 저장해야 합니다.
승인된 VPC 네트워크 드롭다운 메뉴에서 Database Migration Service가 비공개 연결 액세스 권한을 갖도록 할 VPC를 선택합니다.
이 VPC는 소스 Oracle에 비공개 IP가 할당된 네트워크여야 합니다.
IP 범위 할당 필드에 최소 CIDR 블록이 /29인 IP 범위를 입력합니다. 예를 들면 다음과 같습니다.
10.72.149.40/29.
Database Migration Service는 선택한 VPC에서 해당 IP 범위를 기반으로 서브넷을 만듭니다. 네트워크 관리자에게 문의하여 적합한 IP 범위를 확보하는 것이 좋습니다.
테스트 목적으로 가상 프라이빗 클라우드 비공개 서비스 액세스 인터페이스를 사용하여 IP 범위를 생성해 볼 수도 있습니다. 이 자동 할당은 Database Migration Service 비공개 연결 구성을 위한 것이 아닙니다. Database Migration Service에서 사용하기 전에 자동으로 할당된 범위를 해제해야 합니다. 자세한 내용은 다음 섹션을 펼치세요.
예: 비공개 서비스 액세스로 IP 범위 생성
비공개 서비스 액세스 설정을 만들 때 VPC 네트워크에서 사용되지 않는 IP 범위를 생성할 수 있습니다. 나중에 VPC 구성에서 이 범위를 해제하고 Database Migration Service 비공개 연결 구성에 사용할 수 있습니다.
[[["이해하기 쉬움","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-01(UTC)"],[[["\u003cp\u003eThis page provides instructions on creating a private connectivity configuration in Database Migration Service to establish a peering connection between the service network and your Virtual Private Cloud (VPC).\u003c/p\u003e\n"],["\u003cp\u003eA VPC network is required, without peering restrictions, where your source database's private IP is available, and it must have an available IP range with a minimum CIDR block of \u003ccode\u003e/29\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eSpecific IAM roles are required for both the user account performing the migration and the Database Migration Service account, including \u003ccode\u003edatamigration.admin\u003c/code\u003e and \u003ccode\u003ecompute.networkViewer\u003c/code\u003e for the user, and \u003ccode\u003ecompute.networkAdmin\u003c/code\u003e for the service account.\u003c/p\u003e\n"],["\u003cp\u003eCreating the configuration involves selecting an authorized VPC network, entering an IP range (with a minimum \u003ccode\u003e/29\u003c/code\u003e CIDR block), and ensuring the chosen region is consistent across migration entities.\u003c/p\u003e\n"],["\u003cp\u003eAn unoccupied IP range can be generated in your VPC using the private services access interface and then released for use in the Database Migration Service private connectivity configuration, by utilizing the "Allocate an internal IP range" feature.\u003c/p\u003e\n"]]],[],null,["# Create a private connectivity configuration for the source database\n\nThis page describes how to create a private connectivity configuration.\nPrivate connectivity configuration is Database Migration Service construct that helps\nyou create a peering connection between Database Migration Service service network\nand your project's Virtual Private Cloud (VPC) network. You create private connectivity\nconfigurations to establish private connections to source Oracle\ndatabases.\n\nFor more information about network connectivity in Database Migration Service, see\n[Network connectivity for heterogeneous Oracle migrations](/database-migration/docs/oracle-to-postgresql/networking-overview)\nand\n[Source networking methods overview](/database-migration/docs/oracle-to-postgresql/networking-methods-source).\n\nBefore you begin\n----------------\n\n1. Ensure you have a Virtual Private Cloud network that meets the following requirements:\n - The VPC network doesn't have any [peering restrictions](/vpc/docs/vpc-peering#restrictions).\n - It's the same network where your source database is peered. For more information, see the requirements section in [Private connectivity with VPC peering](/database-migration/docs/oracle-to-postgresql/networking-methods-source#private-connectivity-for-source).\n - The VPC network has an available IP range with a minimum CIDR block of `/29`. Database Migration Service uses this IP range to create a subnet so that it can communicate with the source database.\n2. Enable the Database Migration Service and Compute Engine APIs. [Enable the APIs](https://console.cloud.google.com/flows/enableapi?apiid=compute.googleapis.com,datamigration.googleapis.com)\n\n### Required roles\n\nTo get the permissions that you need to create a private connectivity\nconfiguration, ask your administrator to grant you the\nrequired IAM roles on your project:\n\n- [Database Migration Admin](/iam/docs/roles-permissions/datamigration#datamigration.admin) (`roles/datamigration.admin`)\n- [Compute Network Viewer](/iam/docs/roles-permissions/compute#compute.networkViewer) (`roles/compute.networkViewer`)\n\nFor more information about granting roles, see\n[Manage access](/iam/docs/granting-changing-revoking-access) in the Identity and Access Management documentation.\n\nThese predefined roles contain the permissions required to create a\nprivate connectivity configuration in Database Migration Service. To see the exact\npermissions that are required, expand the\n**Required permissions** section: \n\n#### Required permissions\n\nThe following permissions are required to perform heterogeneous Oracle\nmigrations with Database Migration Service:\n\n- `datamigration.* `\n- `compute.networks.list`\n\nYou might also be able to get these permissions with\n[custom roles](/iam/docs/creating-custom-roles) or other\n[predefined roles](/iam/docs/roles-permissions).\n\nCreate the configuration\n------------------------\n\nTo create a private connectivity configuration, follow these steps:\n\n1. In the Google Cloud console, go to the **Private connectivity configurations** page.\n\n [Go to Private connectivity configurations](https://console.cloud.google.com/dbmigration/private-connections)\n2. Click **Create configuration**.\n3. In the **Configure private connectivity** section, enter the display\n name for the configuration and select the region.\n\n Make sure you use the same region where your project Virtual Private Cloud\n network resides. It must be the same region where you intend to create\n the migration job and connection profiles. Database Migration Service is a\n fully-regional product, meaning all entities\n related to your migration (source and destination connection profiles,\n migration jobs, destination databases, conversion workspaces) must be saved in a\n single region.\n4. From the **Authorized VPC network** drop-down menu, select the VPC that you want Database Migration Service to have private connectivity access. This VPC needs to be the network where your source Oracle has a private IP assigned.\n5. In the **Allocate an IP range** field, enter an IP range with a\n minimum CIDR block of `/29`. For example:\n `10.72.149.40/29`.\n\n Database Migration Service creates a subnet based on that IP range in your\n selected VPC. We recommend that you consult your network administrator\n to acquire a suitable IP range.\n\n For testing purposes, you can also try to generate an IP range with\n Virtual Private Cloud private services access interface. Note that this automatic\n allocation isn't intended for Database Migration Service private connectivity\n configurations. You need to release the automatically allocated range\n before you use it in Database Migration Service. Expand the following section\n for more information. \n\n #### Example: generate an IP range with private services access\n\n You can generate an unoccupied IP range in your VPC network\n when you create a private services access setup. You can later\n release this range in the VPC configuration and use it for the\n Database Migration Service private connectivity configuration.\n\n To generate an unoccupied IP range, follow these steps:\n 1. In the Google Cloud console, go to the **VPC networks** page.\n\n [Go to VPC networks](https://console.cloud.google.com/networking/networks/list)\n 2. From the list of networks in your project, select the one where your source Oracle database has a private IP assigned.\n 3. Go to the **Private services access** tab and click **Allocate IP range**.\n 4. In the **Allocate an internal IP range** window, enter the following:\n 1. A display name in the **Name** field.\n 2. Select the **Automatic** option and enter `29` for the prefix\n 3. length.\n\n **Result**: Your VPC network allocates an empty IP range for\n private services access in your project.\n 5. Check the **Internal IP range** value of the new allocated range. Note it down for later use in Database Migration Service.\n 6. Select your new IP range from the list, and click **Release**.\n 7. The generated IP range is now free for use in another subnet. Enter the range you noted down in the **Allocate an IP range** field when you create the private connectivity configuration in Database Migration Service.\n6. Click **Create**.\n\nThe private connectivity configuration is now ready for use with a\n[source connection profile](/database-migration/docs/oracle-to-postgresql/create-source-connection-profile).\n\nWhat's next\n-----------\n\n- Learn about destination database connectivity. See\n [Destination database connectivity overview](/database-migration/docs/oracle-to-postgresql/networking-methods-destination).\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)."]]
