Create an Application Load Balancer
The Application Load Balancer is a flavor of the Elastic Load Balancing (ELB) service. It works more or less the same as a Classic Load Balancer, however, it has several additional features and some new concepts you need to understand so this Lab will covers those first.
AWS has great documentation to help you get started, so let’s start by referencing it:
The load balancer serves as the single point of contact for clients. You add one or more listeners to your load balancer.
A listener checks for connection requests from clients, using the protocol and port that you configure, and forwards requests to one or more target groups, based on the rules that you define. Each rule specifies a target group, condition, and priority.
When the condition is met, the traffic is forwarded to the target group. You must define a default rule for each listener, and you can add rules that specify different target groups based on the content of the request (also known as content-based routing).
Each target group routes requests to one or more registered targets, such as EC2 instances, using the protocol and port number that you specify. You can register a target with multiple target groups. You can configure health checks on a per target group basis.
Health checks are performed on all targets registered to a target group that is specified in a listener rule for your load balancer.
The following diagram illustrates the basic components. Notice that each listener contains a default rule, and one listener contains another rule that routes requests to a different target group. One target is registered with two target groups.
Recent Comments