Organiza tus páginas con colecciones
Guarda y categoriza el contenido según tus preferencias.
Para conectarte a un recurso en una red externa (una red local o
otra red de nube privada virtual [VPC]), la red externa y
la instancia de Cloud Data Fusion deben estar conectadas a través de la misma
red de VPC.
Para conectar una red externa a la red de VPC de Cloud Data Fusion con túneles de Cloud VPN con enrutamiento de protocolo de puerta de enlace de frontera (BGP) o adjuntos de VLAN, haz lo siguiente:
Asegúrate de que las sesiones de BGP en el Cloud Router que administran tus
túneles de Cloud VPN o adjuntos de VLAN hayan recibido prefijos
específicos (destinos) de tu red externa. Las rutas predeterminadas (destino 0.0.0.0/0) no se pueden importar a la red de VPC de Cloud Data Fusion porque esa red tiene su propia ruta predeterminada local. Siempre se usan las rutas locales para un destino, aunque el intercambio de tráfico de Cloud Data Fusion esté configurado para importar rutas personalizadas desde tu red de VPC.
Identifica las conexiones de intercambio de tráfico que produce la conexión privada a los servicios. Según el servicio, la conexión a servicios privados puede crear una o más de las siguientes conexiones de intercambio de tráfico, pero no necesariamente todas:
[[["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-04 (UTC)"],[[["\u003cp\u003eCloud Data Fusion instances must be connected through the same VPC network as the external network they are accessing.\u003c/p\u003e\n"],["\u003cp\u003eConnecting an external network requires using Cloud VPN tunnels or VLAN attachments, with the VPC network connected to the external network via these methods.\u003c/p\u003e\n"],["\u003cp\u003eBGP sessions managing Cloud VPN tunnels or VLAN attachments must receive specific prefixes from the external network, and default routes are not allowed.\u003c/p\u003e\n"],["\u003cp\u003ePeering connections generated by the private services connection must be identified and updated to allow the export of custom routes.\u003c/p\u003e\n"],["\u003cp\u003eA Cloud Router custom advertised route must be created for the allocated IP range on the Cloud Routers managing BGP sessions.\u003c/p\u003e\n"]]],[],null,["# Connect to an external network\n\nTo connect to a resource in an external network (an on-premises network or\nanother Virtual Private Cloud (VPC) network), the external network and\nCloud Data Fusion instance must be connected through the same\nVPC network.\n\nTo connect an external network to the Cloud Data Fusion VPC\nnetwork using Cloud VPN tunnels with border gateway protocol (BGP) routing or\nVLAN attachments, do the following:\n\n- Ensure your VPC network is connected to the external network using a [Cloud VPN tunnel](/network-connectivity/docs/vpn/concepts/overview) or a VLAN attachment for [Dedicated Interconnect](/network-connectivity/docs/interconnect/how-to/dedicated/provisioning-overview) or [Partner Interconnect](/network-connectivity/docs/interconnect/how-to/partner/provisioning-overview).\n- Ensure the BGP sessions on the Cloud Router managing your Cloud VPN tunnels or VLAN attachments have received specific prefixes (destinations) from your external network. Default routes (destination 0.0.0.0/0) cannot be imported into the Cloud Data Fusion VPC network because that network has its own local default route. Local routes for a destination are always used, even though the Cloud Data Fusion peering is configured to import custom routes from your VPC network.\n- [Identify the peering connections](/vpc/docs/configure-private-services-access#listing-connections) produced by the private services connection. Depending on the service, the private services connection might create one or more of the following peering connections, but not necessarily all of them:\n - `datafusion-googleapis-com`\n - `servicenetworking-googleapis-com`\n- [Update all of the peering connections](/vpc/docs/using-vpc-peering#update-peer-connection) to enable Export custom routes.\n- [Identify the allocated range](/vpc/docs/configure-private-services-access#listing_allocated_ip_address_ranges) used by the private services connection.\n- [Create a Cloud Router custom advertised route](/network-connectivity/docs/router/how-to/advertising-custom-ip) for the allocated range on the Cloud Routers managing BGP sessions for your Cloud VPN tunnels or VLAN attachments.\n\nWhat's next\n-----------\n\n- Learn how to [create a private instance in Cloud Data Fusion](/data-fusion/docs/how-to/create-private-ip)."]]
