HA Architecture Flashcards
What is a Load Balancer
Physical/Virtual device designed to help you balance the network load across multiple webservers
3 types of Load Balancers
- Application Load Balancer
- Network Load Balancer
- Classic Load Balancer
Application Load Balancers
- best suited for load balancing of HTTP and HTTPS traffic.
- Operate at Layer 7 and are application aware
- Intelligent and you can create advanced request routing, sending specified requests to specific web server
Network Load Balancers
- Best suited for load balancing of TCP traffic where extreme performance is required
- Operating at the connection level (Layer4)
- Capable of handling millions of requests per second while maintaining ultra low latencies
Classic Load Balancers
- Legacy elastic load balancers
- HTTP/HTTPS applications and use layer 7 specific features such as X forwarded and sticky sessions
- You can also use strict Layer 4 Load balancing for applications that rely purely on the TCP protocol
Error 504 for Classic Load Balancer means
application is having issues - either at the Web Server layer or at the DB layer
X-Forwarded-For-Header
way to get the IP4 address of the end user
Instances monitored by ELB are reported as
InService or OutofService
How are health checks done
checks the instance health by talking to it
Load Balancers are given an IP address instead of a DNS name - True or False
False; LBs have their own DNS name
Launch configuration
an instance configuration template that an Auto Scaling group uses to launch EC2 instances
You can specify your launch configuration with multiple Auto scaling groups - true or false
true
How many launch configurations can you specify for an auto scaling group at a time?
1
Can you modify a launch configuration after you’ve created it?
No
When you create an Auto Scaling group using an EC2 instance, Amazon EC2 Auto Scaling automatically creates a launch configuration for you and associates it with the Auto Scaling group - true or false
true
Sticky session
allows you to bind a user’s session to a specific Ec2 instance. This ensures that all requests from the user during the session are sent to the same instance.
Sticky sessions can also be enabled for Application Load Balancers but the traffic will be sent to
Target Group Level
If you notice that there are no traffic going to the second EC2 instance, then what will you have to do
Disable sticky sessions
If you have EC2 instances that are writing to a local disc, then you will have to
Enable stick session
Cross Zone Load Balancing
enables you to load balance across multiple AZs
Path Based Routing/Path Patterns
allows you to direct traffic to different EC2 instances based on the URL contained in the request
Example of Path Based routing
You can route general requests to one target group and requests to render images to another target group
When you design the architecture, always design for
failure
When designing an HA, use multiple AZs and multiple regions wherever you can - true or false
true