Mantenha tudo organizado com as coleções
Salve e categorize o conteúdo com base nas suas preferências.
Os detalhes da conexão que você precisa fornecer podem variar dependendo da conectividade de destino que você usa. Nesta página, descrevemos como criar perfis de conexão de destino para cada método de conectividade disponível:
Antes de criar um perfil de conexão de destino, faça o seguinte:
Considere em qual região você quer criar o perfil de conexão de destino.
O Database Migration Service é um produto totalmente regional. Isso significa que todas as entidades relacionadas à sua migração (perfis de conexão de origem e destino, jobs de migração, bancos de dados de destino, espaços de trabalho de conversão) precisam ser salvas em uma única região.
As conexões de banco de dados de destino são sempre criptografadas pelo Database Migration Service.
Não é necessário configurar outros certificados para essas conexões.
Na página Criar um perfil de conexão, na lista Função do perfil, selecione Destino.
Na lista Mecanismo de banco de dados, selecione AlloyDB para PostgreSQL.
Na seção Definir configurações de conexão, informe o nome, o identificador e a região do perfil de conexão.
Na seção Detalhes da conexão, faça o seguinte:
No menu suspenso ID do cluster, selecione o identificador do cluster de destino do AlloyDB para PostgreSQL.
Use o campo Nome de host e IP para inserir um dos seguintes
valores:
Para clusters ativados para PSC: use o
nome DNS configurado para seu cluster.
Se o cluster tiver apenas um IP particular configurado,
o campo Nome do host e IP será preenchido automaticamente com
o nome de DNS necessário. Se o cluster tiver os endereços IP público e privado atribuídos, clique no campo Nome do host e IP e selecione o registro DNS no menu.
Para clusters não ativados para PSC: insira o IP particular atribuído ao cluster de destino.
Nos campos restantes, insira o número da porta e os detalhes de login
da conta de usuário de migração dedicada (nome e senha).
Na seção Definir método de conectividade, faça o seguinte:
No menu suspenso Método de conectividade, selecione IP privado.
[[["Fácil de entender","easyToUnderstand","thumb-up"],["Meu problema foi resolvido","solvedMyProblem","thumb-up"],["Outro","otherUp","thumb-up"]],[["Difícil de entender","hardToUnderstand","thumb-down"],["Informações incorretas ou exemplo de código","incorrectInformationOrSampleCode","thumb-down"],["Não contém as informações/amostras de que eu preciso","missingTheInformationSamplesINeed","thumb-down"],["Problema na tradução","translationIssue","thumb-down"],["Outro","otherDown","thumb-down"]],["Última atualização 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."]]