[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC)：2025-09-03。"],[],[],null,["Looker (Google Cloud core) instances that use [private services access](/looker/docs/looker-core-create-private-ip) and are configured with private connections or hybrid connections may require additional configuration to connect to services or resources outside of the instance's VPC network. The following sections describe additional configuration options.\n\n\nConnect to other VPCs using private services access\n\nTo use internal IPs to connect to services in other VPCs that are hosted by either Google or third parties, you can use [private services access](/vpc/docs/private-services-access).\n\nDuring Looker (Google Cloud core) [instance creation](/looker/docs/looker-core-create-private-ip#before_you_create_a_instance), you created a private services access connection to connect your VPC to the Looker (Google Cloud core) service. You can also [update the IP allocation](/vpc/docs/configure-private-services-access#modifying-connection) of an existing private services access connection without disrupting traffic.\n\nTo set up a private services access connection:\n\n1. [Allocate an internal IP range](/vpc/docs/configure-private-services-access#allocating-range) in your VPC network.\n2. [Set up the private connection](/vpc/docs/configure-private-services-access#creating-connection) between your VPC network and service producer's network, using the allocated IP range. This private connection establishes a [VPC Network Peering](/vpc/docs/vpc-peering) connection between your VPC and the other network.\n\nPrivate connections are a one-to-one relationship between your VPC network and a service producer. If a single service producer offers multiple services, you only need one private connection for all of the producer's services.\n\nConnect to on-premises resources or third-party services using private services access\n\nIf your instance was created to use private services access, with either private connections or hybrid connections, you can use either of the following two options to connect Looker (Google Cloud core) instances to on-premises resources or third-party services:\n\n- [Cloud Interconnect](/network-connectivity/docs/interconnect/concepts/overview) and [Cloud Router](/network-connectivity/docs/router/concepts/overview)\n- [Cloud VPN](/network-connectivity/docs/vpn/concepts/overview), specifically HA VPN, and [Cloud Router](/network-connectivity/docs/router/concepts/overview)\n\nWith either method, you will need to do the following:\n\n- Configure a [dynamic route](/vpc/docs/routes#dynamic_routes) in your Looker (Google Cloud core) VPC for each on-premises resource.\n- Set up a [custom advertised route](/network-connectivity/docs/router/concepts/advertised-routes) of the Looker (Google Cloud core) [private services access subnet](/vpc/docs/configure-private-services-access#about_the_service_producers_subnet) on all Cloud Routers that are deployed in the Looker (Google Cloud core) VPC.\n- Update your on-premises firewalls to allow traffic with the Looker (Google Cloud core) subnet.\n- Configure [DNS forwarding](/dns/docs/overview#dns-forwarding-methods), which will let Looker (Google Cloud core) connect to any on-premises resources.\n- Configure [DNS Peering](/sdk/gcloud/reference/services/peered-dns-domains) with the Service Networking Google Managed VPC for the Looker (Google Cloud core) instance to resolve the private hostnames.\n\nCloud Interconnect and Cloud Router\n\nThe following network diagram shows how Cloud Interconnect and Cloud Router interact with the Looker (Google Cloud core) service to connect to an on-premises network:\n\n1. Private services access connects the Looker (Google Cloud core) service with the VPC over internal IP addresses using VPC peering.\n2. Cloud Router uses Border Gateway Protocol (BGP) to advertise the IP prefixes and program dynamic routes based on the BGP advertisements it receives from a peer. Cloud Interconnect is used to connect to the on-premises network.\n\nCloud VPN and Cloud Router\n\nFor a walkthrough of how to create a private and public IP Looker (Google Cloud core) instance and connect it to an on-premises database using Cloud VPN and Cloud Router, see the [Connect Looker Cloud over hybrid networking](https://codelabs.developers.google.com/codelabs/looker-hybrid-networking) codelab.\n\nWhat's next?\n\n- [Connect Looker Cloud over hybrid networking](https://codelabs.developers.google.com/codelabs/looker-hybrid-networking)\n- [Connecting Looker (Google Cloud core) to your database](/looker/docs/looker-core-dialects)\n- [Prepare your Looker (Google Cloud core) instance for users](/looker/docs/looker-core-instance-setup)\n- For an example of how to manually install [Looker Marketplace](/looker/docs/marketplace) content, see the Looker Community article, [Installing the Looker API Explorer on a Looker (Google Cloud core) instance on a private IP network](https://www.googlecloudcommunity.com/gc/Technical-Tips-Tricks/Installing-the-Looker-API-Explorer-on-a-Looker-Google-Cloud-core/ta-p/722671)."]]
