[データベース エンジン] リストから [AlloyDB for PostgreSQL] を選択します。
[接続設定の定義] セクションで、接続プロファイルの名前、ID、リージョンを指定します。
[接続の詳細] セクションで、次の操作を行います。
[クラスタ ID] プルダウン メニューから、AlloyDB for PostgreSQL の移行先クラスタ ID を選択します。
[Hostname and IP] フィールドに次のいずれかの値を入力します。
PSC 対応クラスタの場合:
クラスタ用に構成された DNS 名を使用します。クラスタにプライベート IP のみが構成されている場合、[Hostname and IP] フィールドには必要な DNS 名が自動的に入力されます。クラスタにパブリック IP アドレスとプライベート IP アドレスの両方が割り当てられている場合は、[ホスト名と IP] フィールドをクリックし、メニューから DNS レコードを選択します。
[[["わかりやすい","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,["# Create a destination connection profile\n\nThe connection details you need to provide can differ depending on what destination\nconnectivity you use. This page describes how to create destination connection profiles\nfor each available connectivity method:\n\n- [Destination connection profile for public IP connectivity](#public-ip-connectivity)\n\n- [Destination connection profile for private IP connectivity](#private-ip-connectivity)\n\nBefore you begin\n----------------\n\nBefore you create a destination connection profile, make sure you do the following:\n\n1. Consider in which region you want to create the destination connection profile.\n\n Database Migration Service is a 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\n saved in a single region.\n2. [Configure your destination database and create a dedicated migration user account](/database-migration/docs/oracle-to-alloydb/configure-your-destination-postgresql-database).\n\n3. [Choose and configure the destination connectivity method](/database-migration/docs/oracle-to-alloydb/networking-methods-destination).\n\n Destination database connections are always encrypted by Database Migration Service.\n You don't need to configure additional certificates for those connections.\n\nFor public IP connectivity\n--------------------------\n\nTo create a destination connection profile that uses the\n[public IP connectivity method](/database-migration/docs/oracle-to-alloydb/networking-methods-destination#public-ip), follow these steps:\n\n1. In the Google Cloud console, go to the **Connection profiles** page.\n\n [Go to Connection profiles](https://console.cloud.google.com/dbmigration/connection-profiles)\n2. Click **Create profile**.\n3. On the **Create a connection profile** page, from the **Profile role** list, select **Destination**.\n4. From the **Database engine** list, select **AlloyDB for PostgreSQL**.\n5. In the **Specify connection profile details** section, provide the connection profile name, identifier, and region.\n6. In the **Connection details** section, do the following:\n 1. From the **Cluster ID** drop-down menu, select your AlloyDB for PostgreSQL destination cluster identifier.\n 2. In the **Hostname and IP** field, enter your destination instance's public IP address.\n 3. In the remaining fields, enter the port number and the login details for the dedicated migration user account (name and password).\n7. In the **Define connectivity method** section, from the **Connectivity method** drop-down menu, select **Public IP**.\n8. (Optional) In the **Test connection profile** section, click **Run test** .\n\n Database Migration Service performs a quick check to verify that\n the connection details you supplied are sufficient to reach\n your data.\n9. Click **Create** at the bottom of the page.\n\n The **Connection profiles** page appears, and the newly\n created connection profile is displayed.\n\nFor private IP connectivity\n---------------------------\n\nTo create a destination connection profile that uses the\n[private IP with Private Service Connect connectivity method](/database-migration/docs/oracle-to-alloydb/networking-methods-destination#private-ip),\nfollow these steps:\n\n1. In the Google Cloud console, go to the **Connection profiles** page.\n\n [Go to Connection profiles](https://console.cloud.google.com/dbmigration/connection-profiles)\n2. Click **Create profile**.\n3. On the **Create a connection profile** page, from the **Profile role** list, select **Destination**.\n4. From the **Database engine** list, select **AlloyDB for PostgreSQL**.\n5. In the **Define connection settings** section, provide the connection profile name, identifier, and region.\n6. In the **Connection details** section, do the following:\n 1. From the **Cluster ID** drop-down menu, select your AlloyDB for PostgreSQL destination cluster identifier.\n 2. Use the **Hostname and IP** field to enter one of the following values:\n - **For psc-enabled clusters** : Use the [DNS name configured for your cluster](/alloydb/docs/about-private-service-connect#dns_names_and_records). If your cluster only has a private IP configured, the **Hostname and IP** field is automatically populated with the required DNS name. If your cluster has both the public and private IP addresses assigned, click the **Hostname and IP** field and select the DNS record from the menu.\n - **For non-psc-enabled clusters**: Enter the private IP assigned for your destination cluster.\n 3. In the remaining fields, enter the port number and the login details for the dedicated migration user account (name and password).\n7. In the **Define connectivity method** section, do the following:\n 1. From the **Connectivity method** drop-down menu, select **Private IP**.\n 2. **For non-psc-enabled clusters** : From the **Service attachment\n name** select the service attachment [you created for the destination cluster Private Service Connect connection](/database-migration/docs/oracle-to-alloydb/configure-dst-connection-private-ip#non-psc).\n8. (Optional) In the **Test connection profile** section, click **Run test** .\n\n Database Migration Service performs a quick check to verify that\n the connection details you supplied are sufficient to reach\n your data.\n9. Click **Create** at the bottom of the page.\n\n The **Connection profiles** page appears, and the newly\n created connection profile is displayed."]]
