Network Connectivity Center

Related topics

• Router appliance is part of Network Connectivity Center From the official documentation: “Router appliance within Network Connectivity Center”
• hub is part of Network Connectivity Center From the official documentation: “Quotas that apply to network routes for Cloud Router also apply to routes for NCC hubs and spokes.”
• Network Connectivity Center works with Private NAT From the official documentation: “Private NAT lets you create a Cloud NAT gateway that works in conjunction with Network Connectivity Center spokes to perform network address translation (NAT) between the following networks:”
• Network Connectivity Center is an alternative to VPC Network Peering From the official documentation: “Connectivity between the load balancer's VPC network and the backend VPC network can be configured using either VPC Network Peering, Cloud VPN tunnels, Cloud Interconnect VLAN attachments, or a Network Connectivity Center framework.”
• VPC Service Controls secures Network Connectivity Center From the official documentation: “To further secure your NCC resources, use VPC Service Controls.”
• VPC spoke is part of Network Connectivity Center From the official documentation: “To create a Network Connectivity Center (NCC) VPC spoke, enable the `networkconnectivity` API:”
• 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 works with Private Service Connect From the official documentation: “Private Service Connect consumer access points are reachable over Network Connectivity Center.”
• Site-to-site data transfer is part of Network Connectivity Center From the official documentation: “Network Connectivity Center (NCC) lets you use Google's network as part of a wide area network (WAN) that includes your external sites. This feature is known as *site-to-site data transfer*.”
• spoke is part of Network Connectivity Center From the official documentation: “Then you create a NCC *spoke* to represent each connectivity resource.”
• 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.”
• Cross-Cloud Interconnect works with Network Connectivity Center From the official documentation: “You can connect using Cross-Cloud Interconnect by itself or you can set up Cross-Cloud Interconnect as a [Network Connectivity Center](https://cloud.google.com/network-connectivity-center) hybrid spoke.”
• Network Connectivity Center works with Router appliance From the official documentation: “Router appliance is an alternative way of enabling connectivity between sites outside of Google Cloud through a NCC hub.”
• 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 Virtual Private Cloud From the official documentation: “NCC lets you connect multiple Virtual Private Cloud (VPC) networks and on-premises locations.”
• Router appliance depends on Network Connectivity Center From the official documentation: “*Router appliance requires NCC to operate.*”
• Cloud Interconnect is an alternative to Cloud VPN From the official documentation: “Accessible by using hybrid connectivity (Cloud Interconnect or Cloud VPN).”
• Cloud Monitoring works with Cloud Service Mesh From the official documentation: “Mesh telemetry is no longer automatically ingested into Cloud Monitoring.”
• Cloud Router works with Router appliance From the official documentation: “Each router appliance instance maintains BGP sessions with the same Cloud Router.”
• Cloud Service Mesh works with VPC Service Controls From the official documentation: “You can now use VPC Service Controls with Cloud Service Mesh.”
• Cloud Interconnect works with Cloud Router From the official documentation: “6. Delete the encrypted Cloud Router used for Cloud Interconnect.”
• Cloud Interconnect works with Cloud VPN From the official documentation: “You must enable high-availability (HA) VPN functionality when using Cloud Interconnect<br>with Cloud VPN.”
• 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 Service Mesh works with VPC Network Peering From the official documentation: “Cloud Service Mesh supports [VPC Network Peering](/vpc/docs/vpc-peering) with the [service routing APIs](/service-mesh/docs/service-routing/service-routing-overview).”
• Cloud VPN works with Virtual Private Cloud From the official documentation: “If you are connecting to a Virtual Private Cloud (VPC) network by using Cloud VPN, the Pod and Service CIDR blocks must not conflict with any CIDR blocks on your VPC network.”
• Cloud Interconnect is an alternative to Cross-Cloud Interconnect From the official documentation: “For long-term hybrid or multicloud setups with high outbound data transfer volumes, consider Cloud Interconnect or Cross-Cloud Interconnect.”
• Cloud Interconnect works with Virtual Private Cloud From the official documentation: “By default, any VPC network can use Cloud Interconnect.”
• Cloud Service Mesh works with Shared VPC From the official documentation: “For a detailed explanation of how Shared VPC is supported with Cloud Service Mesh, see [Limitations](/service-mesh/v1.25/docs/service-routing/limitations).”
• Cross-Cloud Interconnect depends on Cloud Router From the official documentation: “To configure Cross-Cloud Interconnect, you need a Cloud Router.”
• Private Service Connect depends on Cloud VPN From the official documentation: “Optional: [Configure Private Service Connect to let your Pods access Google Cloud APIs and services by using Cloud VPN](/vpc/docs/private-service-connect).”
• Private Service Connect works with VPC Service Controls From the official documentation: “VPC Service Controls that use Private Service Connect”
• Cloud Router works with Cloud VPN From the official documentation: “For Cloud Router used with Cloud VPN, set up a dashboard for `network/received_packets_count` and `network/sent_packets_count` to monitor any loss in connectivity.”
• Cloud Service Mesh depends on Cloud Monitoring From the official documentation: “Cloud Service Mesh uses Cloud Monitoring to provide automatic telemetry and logs.”
• Cloud Service Mesh works with Private Service Connect From the official documentation: “Published service backends let you configure regional Cloud Service Mesh to route traffic to published services through Private Service Connect.”
• 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.”
• Cross-Cloud Interconnect is part of Cloud Interconnect From the official documentation: “Cloud Interconnect offers three options for connecting to Google Cloud: Dedicated Interconnect, Partner Interconnect, and Cross-Cloud Interconnect.”
• 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.”
• Private Service Connect is an alternative to VPC Network Peering From the official documentation: “Use VPC Network Peering if you need to insert NVAs or if your application doesn't support Private Service Connect”
• Router appliance depends on Cloud Router From the official documentation: “Router appliance uses a Cloud Router to exchange routes with your VPC network.”
• Shared VPC is an alternative to Virtual Private Cloud From the official documentation: “From the **Network** drop-down, select a VPC or a Shared VPC network.”
• Shared VPC works with VPC Network Peering From the official documentation: “You can use Shared VPC with clusters based on VPC Network Peering.”
• spoke is part of hub From the official documentation: “Create spokes and add the spokes to the hub.”
• Cloud Interconnect works with Private NAT From the official documentation: “Private NAT translates traffic between private networks—specifically, between VPC networks that are connected through a Network Connectivity Center hub or between VPC networks and on-premises or other cloud provider networks that are connected through Cloud Interconnect or…”
• Cloud Interconnect works with Private Service Connect From the official documentation: “Clients in networks that are connected to Google Cloud with VLAN attachments for Cloud Interconnect or Cloud VPN tunnels can reach Private Service Connect endpoints.”
• Cloud Interconnect works with Shared VPC From the official documentation: “You can extend one or more of your existing security zones to Google Cloud by provisioning Shared VPC on Google Cloud and connecting it to the existing zone by using Cloud VPN or Cloud Interconnect.”
• Cloud Interconnect is an alternative to VPC Network Peering From the official documentation: “Connectivity between the load balancer's VPC network and the backend VPC network can be configured using either VPC Network Peering, Cloud VPN tunnels, Cloud Interconnect VLAN attachments, or a Network Connectivity Center framework.”
• Cloud Interconnect 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.”
• Cloud Monitoring works with Cloud Router From the official documentation: “Cloud Router sends logging information to Cloud Logging and sends monitoring metrics to Cloud Monitoring.”
• Cloud Monitoring works with Cloud VPN From the official documentation: “Cloud VPN gateways send logging information to Cloud Logging, and Cloud VPN tunnels send monitoring metrics to Cloud Monitoring.”
• Cloud Monitoring works with internal passthrough Network Load Balancer From the official documentation: “To gain operational insights into your internal passthrough Network Load Balancers, you can integrate [Cloud Logging](/logging) and [Cloud Monitoring](/monitoring).”
• Cloud Monitoring works with Private Service Connect From the official documentation: “Private Service Connect exposes key metrics to Cloud Monitoring that give you insights into your Private Service Connect connections.”
• Cloud Monitoring works with VPC Service Controls From the official documentation: “Cloud Monitoring performs the VPC perimeter check when a project is *added* to a metrics scope:”
• Cloud Router works with Private NAT From the official documentation: “Each Cloud NAT gateway for Private NAT is associated with a single VPC network, region, and Cloud Router.”
• Cloud VPN works with Private NAT From the official documentation: “Private NAT translates traffic between private networks—specifically, between VPC networks that are connected through a Network Connectivity Center hub or between VPC networks and on-premises or other cloud provider networks that are connected through Cloud Interconnect or…”
• Cloud VPN works with Private Service Connect From the official documentation: “Clients in networks that are connected to Google Cloud with VLAN attachments for Cloud Interconnect or Cloud VPN tunnels can reach Private Service Connect endpoints.”
• Cloud VPN secures Virtual Private Cloud From the official documentation: “Cloud VPN is a FedRAMP High authorized service that encrypts your data in transit between your VPC network and your on-premises network.”
• 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.”
• Cross-Cloud Interconnect works with Virtual Private Cloud From the official documentation: “Cross-Cloud Interconnect uses Border Gateway Protocol (BGP) to exchange routes between your Virtual Private Cloud (VPC) network and your Azure network.”