C2 - Part III - Load Balancer

This page describes the Part III of the Challenge 2

Create and deploy a Web Load Balancer

AWS Official doc

Step 1: Create a Target Group

Setting	Value
Basic config	Target type: instances Target group name: LB-TB-CLDGRP[XX]
Health checks	HTTP Port 8080 Health check path: "/drupal"
Register targets	Choose your instance and include it as pending Create target group

Step 2: Create a Loadbalancer

Setting	Value
Type of Loadbalancer	Application Load Balancer
Configure Load Balancer	Name: LB-CLDGRP[XX] Scheme : Internal IP address type: ipv4
Network mapping	VPC: VPC-CLD-LABO02 SUBNETS: 10.0.[XX].0/28 -> A 10.0.[XX[.128/28 - B
Configure Security Groups	Port range: 8080 Protocol: TCP Source: Reverse Proxy
Configure Listeners and routing	HTTP:8080

• Put the Loadbalancer FQDN in Teams and tag Rémi Poulard

  • sample:

• Wait for a response from Rémi

• Test your infra by using cldgrpXX.cld.education in a browser

Step 3: Add an instance

• Using the custom virtual machine image you created earlier launch a second instance.

• Add this instance to the Loadbalancer target group

Conceptual aspects

• Question 1 - Why does AWS need multiple AZ for Elasticity?

  • Official Doc

• Question 2 - How to prove the correct operation of the load balancer?

Debug

• How to debug Load Balancer?

• Update Time out config on Load Balancer?

• Check the security group... the Load Balancer is hosted in the same private subnets as your drupal instance...

• If your web app drupal does not run under "/drupal" but directly as the root path "/", please inform the assistant (impact on the reverse proxy setting)