Curriculum Overview: Identifying the Purposes of Load Balancers

This curriculum provides a deep dive into the fundamental networking concept of Load Balancing within the AWS ecosystem. It is designed to prepare learners for the AWS Certified Cloud Practitioner (CLF-C02) exam by focusing on how Elastic Load Balancing (ELB) enhances application availability and fault tolerance.

Prerequisites

To successfully master this module, learners should have a basic understanding of the following:

• Cloud Concepts: Basic knowledge of high availability, elasticity, and scalability.
• AWS Global Infrastructure: Understanding of Regions and Availability Zones (AZs).
• Compute Services: Familiarity with Amazon EC2 instances and their basic configuration.
• Networking Basics: A high-level understanding of IP addresses, ports (HTTP/HTTPS), and Virtual Private Clouds (VPC).

Module Breakdown

Learning Objectives per Module

Module 1: Core Purpose of ELB

• Define Elastic Load Balancing (ELB) as a service that automatically distributes incoming application traffic across multiple targets.
• Explain how ELB acts as a single point of contact for clients, simplifying the infrastructure interface.

Module 2: Health Checks & Routing

• Describe the Round-robin algorithm used to distribute traffic evenly without regard for instance load.
• Explain the role of Health Checks in identifying failed instances and rerouting traffic to healthy ones.

Module 3: Types of Load Balancers

• Differentiate between the four main types of AWS load balancers:
  1. Application Load Balancer (ALB): Layer 7 (HTTP/HTTPS) routing.
  2. Network Load Balancer (NLB): Layer 4 (TCP/UDP) for high performance.
  3. Gateway Load Balancer (GWLB): For third-party virtual appliances.
  4. Classic Load Balancer (CLB): Legacy support for previous-generation EC2 instances.

Module 4: Security & Integration

• Understand the relationship between ELB and Auto Scaling (ELB detects failure; Auto Scaling replaces the instance).
• Configure Security Groups for listeners to allow specific traffic (e.g., Port 80 for HTTP).

Visual Anchors

Logic Flow: Traffic Distribution

Architectural Concept: High Availability

Success Metrics

To demonstrate mastery, the learner must be able to:

• Correctly identify that an ELB distributes traffic while Auto Scaling provisions new resources.
• Explain that an ALB uses Round-robin routing and does not typically cache content.
• Successfully describe the difference between an Internet-facing and Internal scheme.
• Match a specific use-case (e.g., ultra-low latency) to the correct load balancer type (e.g., NLB).

Real-World Application

• E-Commerce Flash Sales: When a website experiences a massive surge in users, the Load Balancer ensures that no single server is overwhelmed, maintaining a smooth user experience.
• Fault Tolerance: If a hardware failure occurs in one data center (Availability Zone), the Load Balancer automatically shifts traffic to a different data center without the user noticing a service interruption.
• Cost Efficiency: By deleting unused load balancers, organizations can significantly reduce unnecessary AWS expenditure.

Examples Section

[!TIP] Scenario 1: The Modern Web App A company hosts a microservices-based website. They use an Application Load Balancer (ALB) because it can route requests to different "Target Groups" based on the URL path (e.g., /api goes to one group, while /images goes to another).

[!IMPORTANT] Scenario 2: The High-Performance Gaming Server A gaming company requires millions of requests per second with ultra-low latency. They choose the Network Load Balancer (NLB) because it operates at the connection level (Layer 4) and is capable of handling volatile traffic patterns that Layer 7 balancers might struggle with.

▶Click to expand: Comparison of ALB vs NLB

Feature	Application Load Balancer (ALB)	Network Load Balancer (NLB)
Layer	Layer 7 (Application)	Layer 4 (Transport)
Protocols	HTTP, HTTPS, gRPC	TCP, UDP, TLS
Best For	Web applications, Microservices	High performance, Static IPs
Routing	Path-based, Host-based	IP protocol data