Configura la conectividad de red a las fuentes de Amazon RDS for Oracle
Organiza tus páginas con colecciones
Guarda y categoriza el contenido según tus preferencias.
En esta página, se describe cómo configurar la conectividad de red a las fuentes de Amazon RDS para Oracle para las migraciones heterogéneas de Oracle a Cloud SQL para PostgreSQL con Database Migration Service.
Existen tres métodos diferentes que puedes usar para configurar la conectividad de red necesaria para las migraciones desde fuentes de Amazon RDS para Oracle:
En la sección Define connection details, usa el nombre del extremo de tu instancia para la IP de la base de datos de origen.
En la sección Definir método de conectividad, selecciona
Lista de IP permitidas.
Configura la conectividad a través de un túnel SSH de reenvío
Para conectarte a tu base de datos de origen con un túnel de Secure Shell (SSH), sigue estos pasos:
Inicia una instancia de Amazon EC2 para que funcione como un túnel SSH de reenvío dedicado.
Asegúrate de configurarlo en la misma VPC de Amazon en la que tienes tu Amazon RDS para Oracle de origen.
Crea una cuenta de usuario independiente y dedicada para que Database Migration Service se conecte como:
adduserTUNNEL_ACCOUNT_USERNAME
Restringe el acceso a la shell para la cuenta de Database Migration Service y, así, mejora la seguridad:
usermod-s/usr/sbin/nologinTUNNEL_ACCOUNT_USERNAME
Decide qué método de autenticación quieres que use Database Migration Service cuando se conecte al túnel.
Puedes usar una contraseña simple o generar claves SSH en el formato PEM que puedes subir más tarde a Database Migration Service cuando crees el perfil de conexión de origen.
Si quieres usar una contraseña, no necesitas configurar nada más. Recuerda la contraseña que creaste para la cuenta de TUNNEL_ACCOUNT_USERNAME.
Si deseas usar la autenticación basada en claves, debes generar un par de claves pública y privada. Por ejemplo, puedes usar la utilidad ssh-keygen:
Genera el par de claves:
ssh-keygen-mPEM-fYOUR_KEY_NAME
Copia la clave pública (YOUR_KEY_NAME.pub) en el directorio ~/.ssh/ de tu servidor de túnel.
Guarda la clave privada. Deberás subirlo más adelante a Database Migration Service
cuando crees el perfil de conexión de origen.
Edita el archivo /etc/ssh/sshd_config para configurar el túnel SSH de reenvío de modo que coincida con los requisitos de tu organización.
Te recomendamos que uses los siguientes parámetros de configuración:
# Only allow the Database Migration Service user to connect.
AllowUsersTUNNEL_ACCOUNT_USERNAME# Send keep-alive packets every 60 seconds to ensure that# the tunnel doesn't close during the migrationServerAliveInterval=60# Optional: Force key-based authentication
PasswordAuthenticationno
# Enables Database Migration Service to connect from a different host
PermitTunnelyes
GatewayPortsyes
Ejecuta el comando ssh para iniciar el túnel.
Antes de usar cualquiera de los datos de comando a continuación, haz los siguientes reemplazos:
TUNNEL_SERVER_SSH_PORT con el número de puerto
en el que tu servidor escucha las conexiones SSH.
SOURCE_DATABASE_PRIVATE_IP por la dirección IP privada de tu base de datos de origen El servidor SSH debe poder acceder a esa IP.
SOURCE_DATABASE_PORT con el número de puerto en el que tu base de datos de origen escucha las conexiones. El número de puerto predeterminado para las conexiones TCP en Oracle es 1433.
USERNAME con el nombre de la cuenta de usuario que ejecutará el túnel. Esta es una cuenta independiente de TUNNEL_ACCOUNT_USERNAME.
TUNNEL_SERVER_PUBLIC_IP con la IP pública de tu servidor de túnel SSH
En la sección Define connection details, usa el nombre del extremo de tu instancia para la IP de la base de datos de origen.
En la sección Define connectivity method, selecciona Forward-SSH tunnel.
Proporciona la dirección IP pública o el nombre de host de tu servidor SSH.
Proporciona el puerto que designaste para las conexiones SSH en
el servidor de túnel.
Ingresa el nombre de usuario que creaste para que Database Migration Service se conecte como (es decir, el valor de TUNNEL_ACCOUNT_USERNAME).
En el menú desplegable Método de autenticación, selecciona el método de autenticación que deseas usar con TUNNEL_ACCOUNT_USERNAME:
Si deseas usar la contraseña del usuario, selecciona Contraseña y, luego, ingresa la contraseña TUNNEL_ACCOUNT_USERNAME en el formulario.
Si configuraste tu servidor SSH para que use la autenticación basada en claves, selecciona Par de claves pública/privada y sube la clave privada
que generaste con el comando ssh-keygen.
Configura la conectividad privada con el intercambio de tráfico entre VPC
Para usar la conectividad privada con fuentes de Amazon RDS para Oracle, debes tener configurado Cloud VPN o Cloud Interconnect en la misma red de VPC en la que deseas crear la configuración de conectividad privada para Database Migration Service. Si no puedes crear la configuración de conectividad privada en la red de VPC en la que tienes tu Cloud VPN o Cloud Interconnect, también necesitarás una máquina virtual (VM) de proxy inverso en Compute Engine para establecer la conexión.
[[["Fácil de comprender","easyToUnderstand","thumb-up"],["Resolvió mi problema","solvedMyProblem","thumb-up"],["Otro","otherUp","thumb-up"]],[["Difícil de entender","hardToUnderstand","thumb-down"],["Información o código de muestra incorrectos","incorrectInformationOrSampleCode","thumb-down"],["Faltan la información o los ejemplos que necesito","missingTheInformationSamplesINeed","thumb-down"],["Problema de traducción","translationIssue","thumb-down"],["Otro","otherDown","thumb-down"]],["Última actualización: 2025-09-05 (UTC)"],[],[],null,["# Configure network connectivity to Amazon RDS for Oracle sources\n\nThis page describes how to configure network connectivity to Amazon RDS for\nOracle sources for heterogeneous Oracle to\nCloud SQL for PostgreSQL migrations with Database Migration Service.\n\nThere are three different methods you can use to configure the necessary\nnetwork connectivity for migrations from Amazon RDS for Oracle\nsources:\n\n- [Public IP allowlist](#ip-allowlist#)\n- [Forward-SSH tunnel](#forward-ssh)\n- Requires Cloud VPN or Cloud Interconnect: [Private IP connectivity with Virtual Private Cloud peering](#private-vpc-peering)\n\nTo learn more about source database network connectivity, see\n[Source networking methods overview](/database-migration/docs/oracle-to-postgresql/networking-methods-source).\n\nConfigure IP allowlist connectivity\n-----------------------------------\n\nTo use the public IP allowlist connectivity method, follow these steps:\n\n1. In the AWS Management Console, perform the following steps:\n 1. Ensure that your source Amazon RDS database is configured for public IP connections.\n 2. Identify the endpoint name and port number. You need to enter these values when you create the connection profile.\n\n For more information about preparing your Amazon RDS for Oracle\n instance, see\n [Connecting to your Oracle DB instance](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_ConnectToOracleInstance.html) in the Amazon RDS\n documentation.\n2. Create a security group that allows traffic from Database Migration Service\n to your Amazon RDS VPC. See\n [Provide access to your DB instance in your VPC by creating a security group](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/CHAP_SettingUp.html#CHAP_SettingUp.SecurityGroup).\n\n Make sure you allow all [Database Migration Service public IP addresses](/database-migration/docs/oracle-to-postgresql/ip-allowlists-and-regions) for the region where you\n create the migration job.\n3. At a later stage, when you [create the source connection profile](/database-migration/docs/oracle-to-postgresql/create-source-connection-profile), do the following:\n 1. In the **Define connection details** section, use your instance's endpoint name for the source database IP.\n 2. In the **Define connectivity method** section, select **IP allowlist**.\n\nConfigure connectivity over a forward-SSH tunnel\n------------------------------------------------\n\nTo connect to your source database with a Secure Shell (SSH) tunnel,\nfollow these steps:\n\n1. Launch an Amazon EC2 instance to serve as a dedicated forward-SSH tunnel.\n Make sure you configure it in the same Amazon VPC where you\n have your source Amazon RDS for Oracle.\n\n For more information, see\n [Get started with Amazon EC2](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EC2_GetStarted.html) in the Amazon documentation.\n2. [Connect to your EC2 instance](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EC2_GetStarted.html#ec2-connect-to-instance) and set up the SSH tunnel. Follow these steps:\n 1. Create a separate, dedicated user account for Database Migration Service to connect as: \n\n ```bash\n adduser TUNNEL_ACCOUNT_USERNAME\n ```\n 2. Restrict shell access for the Database Migration Service account to enhance security: \n\n ```bash\n usermod -s /usr/sbin/nologin TUNNEL_ACCOUNT_USERNAME\n ```\n 3. Decide what authentication method you want Database Migration Service to use\n when connecting to the tunnel.\n\n You can use a simple password, or generate SSH keys in the\n `PEM` format that you can later upload to Database Migration Service\n when you create the source connection profile.\n - If you want to use a password, you don't need to configure anything additional. Remember what password you created for the \u003cvar translate=\"no\"\u003eTUNNEL_ACCOUNT_USERNAME\u003c/var\u003e account.\n - If you want to use key-based authentication, you need to generate a private-public key pair. For example, you can use the `ssh-keygen` utility:\n 1. Generate the key pair: \n\n ```bash\n ssh-keygen -m PEM -f YOUR_KEY_NAME\n \n ```\n 2. Copy the public key (\u003cvar translate=\"no\"\u003eYOUR_KEY_NAME\u003c/var\u003e`.pub`) to the `~/.ssh/` directory on your tunnel server.\n 3. Save the private key. You need to upload it later to Database Migration Service when you create the source connection profile.\n 4. Edit the `/etc/ssh/sshd_config` file to configure the forward-SSH tunnel to match your organization's requirements. We recommend using the following settings: \n\n ```bash\n # Only allow the Database Migration Service user to connect.\n AllowUsers TUNNEL_ACCOUNT_USERNAME\n\n # Send keep-alive packets every 60 seconds to ensure that\n # the tunnel doesn't close during the migration\n ServerAliveInterval=60\n\n # Optional: Force key-based authentication\n PasswordAuthentication no\n\n # Enables Database Migration Service to connect from a different host\n PermitTunnel yes\n GatewayPorts yes\n ```\n 5. Run the `ssh` command to start the tunnel.\n\n Before using any of the command data below, make the following replacements:\n - \u003cvar class=\"edit\" scope=\"TUNNEL_SERVER_SSH_PORT\" translate=\"no\"\u003eTUNNEL_SERVER_SSH_PORT\u003c/var\u003e with the port number where your server is listening for SSH connections.\n - \u003cvar class=\"edit\" scope=\"SOURCE_DATABASE_PRIVATE_IP\" translate=\"no\"\u003eSOURCE_DATABASE_PRIVATE_IP\u003c/var\u003e with the private IP address of your source database. The SSH server needs to be able to reach that IP.\n - \u003cvar class=\"edit\" scope=\"SOURCE_DATABASE_PORT\" translate=\"no\"\u003eSOURCE_DATABASE_PORT\u003c/var\u003e with the port number where your source database is listening for connections. The default port number for TCP connections on Oracle is `1433`.\n - \u003cvar class=\"edit\" scope=\"USERNAME\" translate=\"no\"\u003eUSERNAME\u003c/var\u003e with the name of the user account that will be running the tunnel. This is a separate account from \u003cvar translate=\"no\"\u003eTUNNEL_ACCOUNT_USERNAME\u003c/var\u003e.\n - \u003cvar class=\"edit\" scope=\"TUNNEL_SERVER_PUBLIC_IP\" translate=\"no\"\u003eTUNNEL_SERVER_PUBLIC_IP\u003c/var\u003e with the public IP of your SSH tunnel server.\n\n ```bash\n ssh -N -L \\\n TUNNEL_SERVER_SSH_PORT:SOURCE_DATABASE_PRIVATE_IP:SOURCE_DATABASE_PORT \\\n USERNAME@TUNNEL_SERVER_PUBLIC_IP\n ```\n3. At a later stage, when you [create the source connection profile](/database-migration/docs/oracle-to-postgresql/create-source-connection-profile), do the following:\n 1. In the **Define connection details** section, use your instance's endpoint name for the source database IP.\n 2. In the **Define connectivity method** section, select **Forward-SSH tunnel**.\n 3. Provide the public IP address or hostname of your SSH server.\n 4. Provide the port that you designated for the SSH connections on the tunnel server.\n 5. Enter the username for the user you created for Database Migration Service to connect as (that is, the value of \u003cvar translate=\"no\"\u003eTUNNEL_ACCOUNT_USERNAME\u003c/var\u003e).\n 6. From the **Authentication method** drop-down menu, select the authentication method you want to use with \u003cvar translate=\"no\"\u003eTUNNEL_ACCOUNT_USERNAME\u003c/var\u003e:\n - If you want to use the user password, select **Password** and enter \u003cvar translate=\"no\"\u003eTUNNEL_ACCOUNT_USERNAME\u003c/var\u003e password in the form.\n - If you configured your SSH server to use key-based authentication, select **Private/Public key pair** and upload the **private key** [you generated in with the `ssh-keygen` command](#generate-ssh-keys-step).\n\nConfigure private connectivity with VPC peering\n-----------------------------------------------\n\nTo use private connectivity with Amazon RDS for Oracle sources,\nyou need to have a Cloud VPN or Cloud Interconnect configured in the same\nVPC network where you intend to create the private connectivity configuration\nfor Database Migration Service. If you can't create the private connectivity configuration\nin the VPC network where you have your Cloud VPN or Cloud Interconnect,\nthen you also need a reverse proxy Virtual Machine (VM) on Compute Engine to\nestablish the connection.\n\nIf you can't use Cloud VPN or Cloud Interconnect, we recommend\nthat you use the\n[forward-SSH tunnel](#forward-ssh-tunnel) or the\n[IP allowlist](#ip-allowlist)\nconnectivity methods instead.\n\nTo use private connectivity with VPC peering and Cloud VPN,\nfollow these steps:\n\n1. Set up direct connectivity with Cloud VPN to your Amazon RDS for\n PostgreSQL instance.\n\n For more information, see\n [Create HA VPN connections between Google Cloud and AWS](/network-connectivity/docs/vpn/tutorials/create-ha-vpn-connections-google-cloud-aws)\n in the Cloud VPN documentation.\n2. Optional: If you can't create the private connectivity configuration in the same VPC network where you have the Cloud VPN, create [a reverse proxy Virtual Machine (VM) on Compute Engine](/database-migration/docs/oracle-to-postgresql/configure-src-connection-reverse-proxy) to forward the connections between VPCs.\n3. In Database Migration Service, [create a private connectivity configuration](/database-migration/docs/oracle-to-postgresql/create-private-connectivity-configuration) to peer with the VPC network where you have your Cloud VPN.\n4. At a later stage, when you [create the source connection profile](/database-migration/docs/oracle-to-postgresql/create-source-connection-profile), do the following:\n 1. In the **Define connection details** section, enter the private IP of your source Amazon RDS instance.\n 2. In the **Define connectivity method** section, select **Private connectivity (VPC peering)**.\n 3. From the drop-down menu, select the private connectivity configuration you created in the previous step."]]