AWS Service

Elastic Load Balancing

ELB distributes traffic across targets. ALB handles Layer 7 HTTP features; NLB handles Layer 4 high-performance TCP/UDP/TLS.

What This Service Solves

ELB distributes traffic across targets. ALB handles Layer 7 HTTP features; NLB handles Layer 4 high-performance TCP/UDP/TLS.

  • Use ALB for HTTP routing, path/host rules, containers, and web apps.
  • Use NLB for static IP, ultra-low latency, TCP/UDP, or preserving source IP behavior.

When You Should Not Use It

  • Do not use a load balancer as a substitute for application health, autoscaling, or database failover.

What AWS Manages and What You Manage

AWS manages load balancer infrastructure. You manage listeners, rules, target groups, health checks, TLS, and security controls.

Security Implications

Use HTTPS listeners, ACM certificates, security groups where supported, WAF with ALB, and private/internal load balancers.

Availability and Scaling

Deploy across multiple AZs and ensure targets exist in each AZ.

Load balancers scale, but target health and backend capacity still matter.

Cost Behavior

Hourly load balancer cost and LCU/NLCU usage, cross-zone traffic, and data transfer are relevant.

Common Integrations

  • EC2
  • ECS
  • Auto Scaling
  • ACM
  • WAF
  • CloudWatch

How AWS Might Present It

Certification-Specific Depth

Sources and Review Metadata

This independent training application is not affiliated with or endorsed by Amazon Web Services. AWS, Amazon Web Services, and AWS certification names are trademarks of Amazon.com, Inc. or its affiliates.