Shared VPC network

Related topics

• Network Connectivity Center works with Shared VPC network From the official documentation: “Be aware that if you need to work with NCC in a Shared VPC network, you must have all needed permissions *in the host project*.”
• Shared VPC network is part of host project From the official documentation: “After resources have been provisioned, configure firewall rules for the Shared VPC network in the host project.”
• Shared VPC network is part of Shared VPC From the official documentation: “The VPC networks in the host project are called *Shared VPC networks*.”
• Cloud VPN is an alternative to VPC Network Peering From the official documentation: “As a variation to the design, you can use Cloud VPN instead of VPC Network Peering.”
• Shared VPC is an alternative to VPC Network Peering From the official documentation: “We recommend using Shared VPC over using VPC Network Peering because Shared VPC is easier to configure and scale.”
• Shared VPC works with VPC Service Controls From the official documentation: “If you use both Shared VPC and VPC Service Controls, the host project that contains the network and the service project that contains the Managed Lustre instance must both be inside the same perimeter.”
• Cloud VPN works with Shared VPC From the official documentation: “The Shared VPC network is connected by using [Cloud VPN](/network-connectivity/docs/vpn/concepts/overview) to an on-premises network.”
• host project is part of Shared VPC From the official documentation: “When you use Shared VPC, you designate a project as a *Shared VPC host project* and attach one or more *service projects* to it.”
• internal passthrough Network Load Balancer works with Network Connectivity Center From the official documentation: “NCC supports a next hop internal passthrough Network Load Balancer in a VPC spoke subject to [NCC requirements for connectivity](/network-connectivity/docs/network-connectivity-center/concepts/static-routes-overview).”
• Network Connectivity Center is an alternative to VPC Network Peering From the official documentation: “This document presents three architectural options for setting up a hub-and-spoke network topology in Google Cloud. The first option uses Network Connectivity Center, the second uses VPC Network Peering, and the third uses Cloud VPN.”
• service project is part of Shared VPC From the official documentation: “When you use Shared VPC, you designate a project as a *Shared VPC host project* and attach one or more *service projects* to it.”
• Shared VPC is part of host project From the official documentation: “The Shared VPC host project is the project which contains the Shared VPC network.”
• Shared VPC depends on host project From the official documentation: “Each Shared VPC network is defined and owned by a centralized *host project*, and can be used by one or more *service projects*.”
• Shared VPC works with VPC Network Peering From the official documentation: “You can use Shared VPC with clusters based on VPC Network Peering.”
• Cloud VPN works with internal passthrough Network Load Balancer From the official documentation: “Clients that are internal or are connected through Cloud VPN tunnels and Cloud Interconnect VLAN attachments can access internal passthrough Network Load Balancers.”
• Cloud VPN is an alternative to Network Connectivity Center From the official documentation: “This document presents three architectural options for setting up a hub-and-spoke network topology in Google Cloud. The first option uses Network Connectivity Center, the second uses VPC Network Peering, and the third uses Cloud VPN.”
• Cloud VPN works with VPC Service Controls From the official documentation: “VPC Service Controls works with either Cloud Interconnect or Cloud VPN to provide additional security for your clusters.”
• host project works with service project From the official documentation: “You can use a single VPC network in a host project to connect resources from multiple service projects.”
• host project is an alternative to service project From the official documentation: “If your organization uses Shared VPC, you can set up a Serverless VPC Access connector in either the service project or the host project.”
• internal passthrough Network Load Balancer works with Shared VPC From the official documentation: “The following table summarizes the component requirements for internal passthrough Network Load Balancers used with Shared VPC networks.”
• internal passthrough Network Load Balancer depends on VPC network From the official documentation: “By default, an internal passthrough Network Load Balancer is available only from within the VPC network that hosts it.”
• Network Connectivity Center is an alternative to Shared VPC From the official documentation: “Hub-and-spoke [Shared VPC](/vpc/docs/shared-vpc) topology or [Network Connectivity Center](/network-connectivity/docs/network-connectivity-center) architectures that minimize public exposure”
• Network Connectivity Center works with VPC network From the official documentation: “You can use Network Connectivity Center (NCC) to connect VPC networks by using a hub and spoke connectivity model.”
• Shared VPC depends on service project From the official documentation: “Shared VPC requires that you designate a *host project* to which networks and subnetworks belong and a *service project*, which is attached to the host project.”
• Shared VPC is an alternative to VPC network From the official documentation: “The VLAN attachment or Cloud VPN tunnel must terminate in the same VPC network (or Shared VPC network) as the endpoint.”
• VPC network is part of host project From the official documentation: “The host project contains two VPC networks `VPC1` and `VPC2`.”
• VPC network works with VPC Service Controls From the official documentation: “You can configure the VPC network to restrict Private Google Access with respect to a service perimeter.”
• VPC Service Controls secures Network Connectivity Center From the official documentation: “To secure your Network Connectivity Center (NCC) configuration, use VPC Service Controls.”