Database Migration Service は、移行先インスタンスのパブリック IP アドレスまたはプライベート IP アドレスに接続できます。このページでは、使用可能な各移行先データベース接続方法の概要と、移行に適したソリューションを選択するのに役立つ推奨事項のセクションについて説明します。
Database Migration Service は、
Private Service Connect を使用して、プライベート IP アドレスを使用して移行先の Cloud SQL インスタンスに接続します。Private Service Connect を使用すると、宛先データベースを安全な受信接続に公開し、データベースにアクセスできるユーザーを制御できます。この接続は Database Migration Service によって暗号化されます。
PSC 対応の Cloud SQL インスタンスを移行先データベースとして使用できない場合でも、プライベート IP 接続を使用できます。この構成は、Database Migration Service と宛先のプライベート IP 間のトラフィックを転送するために、ネットワークに追加の要塞仮想マシン（VM）が必要になるため、より複雑になります。
図 3. 移行ネットワーキングの例: パブリック IP ソース接続。（クリックして拡大）
PSC 対応でないインスタンスの要件
PSC が有効になっていない Cloud SQL インスタンスのプライベート IP 接続には、次のものが必要です。
[[["わかりやすい","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。"],[],[],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)."]]
