Please enable JavaScript.

Coggle requires JavaScript to display documents.

Elastic Load Balancer (limitations (supported protocols (classic load…

- - - - HTTP
      - HTTPS (Secure HTTP)
      - TCP
      - SSL (Secure TCP)
    - - HTTP
      - HTTPS
      - Websocket
      - HTTP/2
  - - - only EC2 instance
    - - EC2
      - EC2 container service
- - - - it will distribute traffic evenly across multiple backend instances in all AZ. If we don’t check this option while configuring ELB then ELB will consider AZ as one single large instance. It is better practice to select this option while configuring EL
    - - An Application Load Balancer has access to HTTP headers and allows you to route requests to different backend services accordingly. For example, you might want to send requests that include /api in the URL path to one group of servers (we call these target groups) and requests that include /mobile to another. Routing requests in this fashion allows you to build applications that are composed of multiple microservices that can run and be scaled independently
    - - A Layer 4 load balancer works at the network protocol level and does not look inside of the actual network packets, remaining unaware of the specifics of HTTP and HTTPS.
        In other words, it balances the load without necessarily knowing a whole lot about it.
    - - A Layer 7 load balancer is more sophisticated and more powerful. It inspects packets, has access to HTTP and HTTPS headers, and (armed with more information) can do a more intelligent job of spreading the load out to the target.
    - - this term is specific to Application Load Balancer
      - it is logical grouping of listeners
      - each load balancer must have at least one listener
      - it can exist without application load balancer
      - We can not mix targets in target group i.e. we can not have mix of EC2 instance and containers
      - it is specific to region