You're reading from AWS for System Administrators Build, automate, and manage your infrastructure on the most popular cloud platform – AWS

Product type Paperback

Published in Feb 2021

Publisher Packt

ISBN-13 9781800201538

Length 388 pages

Edition 1st Edition

Tools

AWS

Concepts

System Administration

Author (1):

Prashant Lakhera

View More author details

Table of Contents (18) Chapters

Preface

1. Section 1: AWS Services and Tools

2. Chapter 1: Setting Up the AWS Environment FREE CHAPTER

3. Chapter 2: Protecting Your AWS Account Using IAM

4. Section 2: Building the Infrastructure

5. Chapter 3: Creating a Data Center in the Cloud Using VPC

6. Chapter 4: Scalable Compute Capacity in the Cloud via EC2

7. Section 3: Adding Scalability and Elasticity to the Infrastructure

8. Chapter 5: Increasing an Application's Fault Tolerance with Elastic Load Balancing

9. Chapter 6: Increasing Application Performance Using AWS Auto Scaling

10. Chapter 7: Creating a Relational Database in the Cloud using AWS Relational Database Service (RDS)

11. Section 4: The Monitoring, Metrics, and Backup Layers

12. Chapter 8: Monitoring AWS Services Using CloudWatch and SNS

13. Chapter 9: Centralizing Logs for Analysis

14. Chapter 10: Centralizing Cloud Backup Solution

15. Chapter 11: AWS Disaster Recovery Solutions

16. Chapter 12: AWS Tips and Tricks

17. Other Books You May Enjoy

Leave a review - let other readers know what you think

Different load balancers offered by AWS

Before discussing various load balancer offerings by AWS, let's first try to understand what a load balancer is. A load balancer is a device that distributes network and application traffic across multiple servers.

AWS offers three types of load balancers, and they all fulfill a slightly different set of objectives:

Classic load balancer: (Previous generation and now deprecated.) This was initially designed to load balance traffic to multiple EC2 instances. It supports protocols such as HTTP, HTTPS, TCP, and SSL. A common misconception about it is that it acts as a layer 7 (application layer) device, but even if it is a layer 7 device, it doesn't support routing rules based on specific paths (for example, /test). This limitation is overcome in the application load balancer.
Application load balancer: This works on layer 7 and supports the HTTP and HTTPS protocols. It allows users to configure and route incoming end user...