Target Groups Fundamentals
What you'll learn: How Application Load Balancers use target groups to organize and route traffic to your backend instances.
What is a Target Group?
A target group is a logical container that holds one or more backend targets (like EC2 instances, containers, or IP addresses) that receive traffic from your Application Load Balancer. Think of it like a phone directory for a department—the ALB looks up which "targets" are available in the group and routes incoming requests to them.
When you create an ALB listener rule (as you learned previously), the rule forwards matching traffic to a specific target group, not directly to individual instances.
How Targets Get Registered
You explicitly register targets with a target group. For example, if you have three web server instances, you register all three with your "web-servers" target group. The ALB then knows these are the available backends for handling requests.
Each registered target has:
- A unique identifier (instance ID or IP address)
- A port number where it receives traffic
- A health status (determined by health checks)
Traffic Distribution in Action
When a request arrives at your ALB:
- The listener rule evaluates the request
- The matching rule forwards traffic to its associated target group
- The target group selects a healthy target using the configured load balancing algorithm
- Traffic flows to that specific backend instance
Only targets passing their health checks receive traffic—unhealthy ones are automatically excluded until they recover.
Key Takeaway: Target groups organize your backend instances into logical units, allowing ALBs to distribute traffic intelligently while automatically avoiding unhealthy targets.