Configuring an HTTP Load Balancer with Google Cloud Armor

Overview Google Cloud HTTP(S) load balancing is implemented at the edge of Google's network in Google's points of presence (POP) around the world. User traffic directed to an HTTP(S) load balancer enters the POP closest to the user and is then load-balanced over Google's global network to the closest backend that has sufficient capacity available. Google Cloud Armor IP deny/allow rules enable you to restrict or allow access to your HTTP(S) load balancer at the edge of the Google Cloud, as close as possible to the user and to malicious traffic. This prevents malicious users or traffic from consuming resources or entering your virtual private cloud (VPC) networks. In this lab, you will configure an HTTP load balancer with global backends, as shown in the diagram below. Then you stress test the load balancer and deny the stress test IP with Google Cloud Armor. Objectives In this lab, you will learn how to perform the following tasks: - Create a health check firewall rule - Create two regional NAT configurations using Cloud Router - Configure two instance templates - Create two managed instance groups - Configure an HTTP load balancer with IPv4 and IPv6 - Stress test an HTTP load balancer - Deny an IP address to restrict access to an HTTP load balancer #gcp #googlecloud #qwiklabs #learntoearn