A load balancer receives some incoming traffic from customers and then routes various requests to its listed targets (like EC2 instances) within the Availability Zones. The load balancer even governs the status of the listed targets and then assures that it will route the traffic solely to robust targets. Once the load balancer notices any weak target, it pauses the routing traffic to the particular target, and later reopens the routing traffic to the concerned target once it finds that the particular target is robust once again.
Customers set up their load balancer to receive incoming traffic by notifying various listeners. A listener is typically a procedure which verifies for connection requests. It is designed with some protocol along with port number for various connections from customers to the load balancer as well as a protocol with port number from the load balancer to their targets.
Elastic Load Balancing sustains three kinds of tech, named Application, Network, and Classic Load Balancers. There exist a major difference within their way of setting up those load balancers. With Application Load Balancers along with Network Load Balancers, customers will list targets under target groups, and then route traffic to the respective target groups. With the usage of Classic Load Balancers, customers records various instances with the load balancer.