hierarchical firewall policies

Related topics

• hierarchical firewall policies secures resource hierarchy From the official documentation: “These examples help you understand how hierarchical firewall policies work and how to use them to provide consistent security across your Google Cloud resource hierarchy.”
• hierarchical firewall policies works with Shared VPC From the official documentation: “In [Shared VPC](/vpc/docs/shared-vpc) scenarios, a VM interface connected to a host project network is governed by the hierarchical firewall policy rules of the host project, not the service project.”
• hierarchical firewall policies works with VPC Network Peering From the official documentation: “In [VPC Network Peering](/vpc/docs/vpc-peering) scenarios, the VM interface associated to each of the VPC networks inherits the policies in the hierarchy in the respective VPC networks.”
• Cloud Interconnect is an alternative to Cloud VPN From the official documentation: “Accessible by using hybrid connectivity (Cloud Interconnect or Cloud VPN).”
• 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.”
• 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 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).”
• 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.”
• 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).”
• 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.”
• Network Connectivity Center works with Private Service Connect From the official documentation: “Private Service Connect consumer access points are reachable over Network Connectivity Center.”
• 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”
• 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.”
• 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 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 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.”
• 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.”
• Private Service Connect works with Shared VPC From the official documentation: “Private Service Connect resources can be deployed in standalone VPC networks or Shared VPC networks.”
• Private Service Connect is part of Virtual Private Cloud From the official documentation: “VPC includes VPC Network Peering, Private Service Connect, private services access, and Shared VPC.”
• Private Service Connect works with Virtual Private Cloud From the official documentation: “[Private Service Connect](https://cloud.google.com/private-service-connect) | Create a private and secure connection from your VPCs to Google, third parties, or your own services.”
• VPC Network Peering is part of Virtual Private Cloud From the official documentation: “VPC includes VPC Network Peering, Private Service Connect, private services access, and Shared VPC.”