Please enable JavaScript.
Coggle requires JavaScript to display documents.
Elastic Load Balancing - Coggle Diagram
Elastic Load Balancing
-
Network Load Balancers
components
load balancer
-
-
-
enable one or more AZs for NLB when you create it, can add but not remove AZs later
idle timeout value for TCP flows = 350 seconds, cannot be modified, clients use TCP keepalive packets to reset timeout
UDP is connectionless but NLB maintains UDP flow state ensuring packets in same flow are sent to same target, idle timeout value for UDP flows = 120 seconds
listener
allowed protocols and ports; TCP, TLS, UDP, TCP_UDP, 1 - 65535
-
-
-
-
-
target group
if target = ip then up to 55000 simultaneous connections to each unique target (if more then increasing chance of port allocation errors)
-
attributes
-
-
preserve_client_ip.enabled (default = disabled if target group type is ip and protocol is TCP or TLS, otherwise default = enabled, cannot be disabled for UDP and TCP_UDP)
-
-
-
-
-
-
-
-
-
-
Gateway Load Balancers
= deploy, scale, and manage virtual appliances, such as firewalls, intrusion detection and prevention systems, and deep packet inspection systems
-
listens for all IP packets across all ports and forwards traffic to the target group specified in the listener rule
maintains stickiness of flows to a specific target appliance using 5-tuple (for TCP/UDP flows) or 3-tuple (for non-TCP/UDP flows)
-
-
must create the GLB endpoint and the application servers in different subnets. This enables to configure the GLB endpoint as the next hop in the route table for the application subnet.
-
-
-
-
-
HTTP Headers
ALB and CLB
-
-
-
-
when they receive Expect header: respond to the client immediately with an HTTP 100 Continue without testing the content length header, remove the Expect header, and then route the request
Scheme
-
-
both internet-facing and internal load balancers route requests to targets using private IP addresses