データベースの移行中、移行先の Cloud SQL データベースは移行元データベースに接続する必要があります。Database Migration Service には、この接続を構成する方法がいくつか用意されています。選択する接続方法は、移行元データベースの種類と、それがオンプレミスや Google Cloud、または別のクラウド プロバイダのどこにあるかによって異なります。
[[["わかりやすい","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 the destination Cloud SQL database to connect to the source database.\u003c/p\u003e\n"],["\u003cp\u003eThe chosen connectivity method depends on the source database's type and location (on-premises, Google Cloud, or another cloud provider).\u003c/p\u003e\n"],["\u003cp\u003eThere are three connectivity methods available: IP allowlists for public connectivity, reverse SSH tunnel for secure connectivity without a reachable VPC, and VPC peering for private connectivity when a reachable VPC is available.\u003c/p\u003e\n"],["\u003cp\u003eVPC peering is a connectivity option if a VPN or Cloud Interconnect connection is set up in Google Cloud.\u003c/p\u003e\n"]]],[],null,["# Configure connectivity\n\n\u003cbr /\u003e\n\n[MySQL](/database-migration/docs/mysql/configure-connectivity \"View this page for the MySQL version of Database Migration Service.\") \\| PostgreSQL \\| [PostgreSQL to AlloyDB](/database-migration/docs/postgresql-to-alloydb/configure-connectivity \"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\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\nDuring database migration, the destination database needs to connect\nto the source database. Database Migration Service provides several ways to configure\nthis connectivity. The connectivity method you choose depends on the type of\nsource database, and whether it resides on-premises, in Google Cloud, or in another\ncloud provider.\n\nYou can configure the following connectivity methods:\n\n- [IP allowlists](/database-migration/docs/postgres/configure-connectivity-ip-allowlists): Choose this method if you want to use public connectivity.\n- [Reverse SSH tunnel using a cloud-hosted VM](/database-migration/docs/postgres/configure-connectivity-reverse-ssh-tunnel): Choose this method if you want to use secure connectivity, and when you don't have a virtual private cloud (VPC) network in Google Cloud from which you can reach the source database.\n- Private connectivity: Choose this method if you want the destination database to connect to the private IP of your source. There are two types of private connectivity available:\n - [Private Service Connect interfaces](/database-migration/docs/postgres/configure-connectivity-vpc-peering#psc-interfaces): This connectivity method lets your destination database initiate connections to the private IP of your source database without consuming peering quota. Instead, Private Service Connect interfaces use network attachments you create in your VPC.\n - [VPC peering](/database-migration/docs/postgres/configure-connectivity-vpc-peering#vpc-peering): This method requires that you have a VPC network in Google Cloud from which you can reach the source database. Use VPC peering if you have a [VPN](/database-migration/docs/postgres/configure-connectivity-vpns) or Cloud Interconnect connection set up in Google Cloud.\n\nWhat's next\n-----------\n\n- Learn more about [private services access](/vpc/docs/private-services-access).\n- Learn more about [Private Service Connect interfaces](/vpc/docs/about-private-service-connect-interfaces).\n- Learn more about [using VPC peering](/vpc/docs/using-vpc-peering)."]]