AWS Cloud Foundations
LinkedIn
  • Intro
  • Module 1
  • Module 2
  • Module 3
  • Module 4
  • Module 5
  • Module 6
  • Module 7
  • Module 8
  • Module 9
  • Module 10
Powered by GitBook
On this page
  • Exam
  • Elastic Load Balancing
  • Types of Load Balancers
  • How Elastic Load Balancing Operates
  • Auto Scaling Group
  • QUIZ ANSWERS

Module 10

PreviousModule 9

Last updated 11 months ago

Exam

  • Target group

  • Types of load balancers

    • Application Load Balancer

    • Network Load Balancer

    • Classic Load Balancer

Elastic Load Balancing

  • Put servers in target group

  • Target group determines which servers are healthy via the HTTP headers being sent to / (root)

  • Users can send their requests to the Elastic Load Balancers public IP

  • The load balancer will distribute the traffic amongst the HEALTHY servers

  • Distributes incoming application or network traffic across multiple targets in a single Availability Zone or across multiple Availability Zones

  • Scales your load balancer as traffic to your application changes over time.

A target group is like a container of servers that are monitored for health

  • When the load balancer detects an unhealthy target, it stops routing traffic to that target. It then resumes routing traffic to that target when it detects that the target is healthy again

  • With Application Load Balancers and Network Load Balancers, you register targets in target groups, and route traffic to the target groups. With Classic Load Balancers, you register instances with the load balancer

Types of Load Balancers

  • Gateway Load balancers are used for third party devices like Cisco routers or Checkpoint firewalls

How Elastic Load Balancing Operates

  • With Application Load Balancers and Network Load Balancers, you register targets in target groups and route traffic to the target groups

  • With Classic Load Balancers, you register instances with the load balancer

Load balancer performs health checks to monitor the health of registered targets

The Front-End will have a public-facing load balancer (public IP) and the Back-End will have an internal load balancer (private IP)

Use Cases

  • Highly available and fault-tolerant applications

  • Containerized applications

  • Elasticity and scalability

  • VPC's

  • Hybrid environments

  • Invoke Lambda functions over HTTP(S)

Amazon CloudWatch, CloudTrail and Access logs can be used to monitor the load balancer

Auto Scaling Group

An Auto Scaling group is a collection of EC2 instances that are treated as a logical grouping for the purposes of automatic scaling and management.

  1. Create a Launch Template object

    1. Choose an image/AMI to use (website, template, etc.)

  2. Create Auto Scaling Group (ASG)

    1. This will talk to the load balancer

    2. It will dynamically create instances based on the health nodes and other metrics (CPU)

    3. The minimum and maximum amount of instances can be made

    4. Dynamic auto scaling can be configured to trigger a new instance if the cpu (based on Cloud Watch)

      1. Simple

      2. Steps

Multiple metrics and actions can be configured

There is also an option to not use Cloudwatch. It will use the target tracking policy instead

QUIZ ANSWERS