AWS Case Study

Elastic Load Balancing

Use this page as a service-specific case-study starter for architecture, simulation, and optimization scenarios in pinpole.cloud.

Why this service matters

ELB distributes traffic across targets (EC2, containers, IPs, Lambda).

Power:
- ALB (L7): content-based routing, host/path-based rules, native HTTP/2 & WebSocket
- NLB (L4): ultra-low latency, static IP/Elastic IP, millions of requests per second
- GLB (L3): third-party virtual appliances (firewalls, IDS, deep packet inspection)
- Cross-zone load balancing for even traffic distribution
- Sticky sessions for stateful applications

Important workflows

  • Register Target - Register a new target (instance, IP, or Lambda) with a target group
  • Create Listener - Add a new listener rule to the load balancer
  • View Health - Check the health status of registered targets

Configuration sections

  • Load Balancer Type
  • Scheme
  • Network Configuration
  • Listeners
  • Target Groups
  • Health Check Settings
  • Load Balancer Attributes
  • Access Logging

Key configuration points

PointDefault / ValueCategory
VPCConfigurableNetwork Configuration
IP Address Typeipv4Network Configuration
Health Check ProtocolHTTPHealth Check Settings
Health Check Path/Health Check Settings
Health Check Porttraffic-portHealth Check Settings
Interval (seconds)30Health Check Settings
Timeout (seconds)5Health Check Settings
Healthy Threshold5Health Check Settings
Unhealthy Threshold2Health Check Settings
Idle Timeout (seconds)60Load Balancer Attributes
Deletion ProtectionfalseLoad Balancer Attributes
Cross-Zone Load BalancingtrueLoad Balancer Attributes
Back to pinpole.cloud landing page