menu
arrow_back

HTTP Load Balancer with Cloud Armor

—/100

Checkpoints

arrow_forward

Configure HTTP and health check firewall rules

Configure instance templates and instance group

Configure the HTTP Load Balancer

Blacklist the siege-vm

HTTP Load Balancer with Cloud Armor

1시간 크레딧 7개

GSP215

Google Cloud Self-Paced Labs

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.

Cloud Armor IP allowlist/denylist 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 configure an HTTP Load Balancer with global backends, as shown in the diagram below. Then, you stress test the Load Balancer and denylist the stress test IP with Cloud Armor.

network_diagram.png

Objectives

In this lab, you learn how to perform the following tasks:

  • Create HTTP and health check firewall rules

  • Configure two instance templates

  • Create two managed instance groups

  • Configure an HTTP Load Balancer with IPv4 and IPv6

  • Stress test an HTTP Load Balancer

  • Denylist an IP address to restrict access to an HTTP Load Balancer

이 실습의 나머지 부분과 기타 사항에 대해 알아보려면 Qwiklabs에 가입하세요.

  • Google Cloud Console에 대한 임시 액세스 권한을 얻습니다.
  • 초급부터 고급 수준까지 200여 개의 실습이 준비되어 있습니다.
  • 자신의 학습 속도에 맞춰 학습할 수 있도록 적은 분량으로 나누어져 있습니다.
이 실습을 시작하려면 가입하세요