Book Image

AWS for Solutions Architects

By : Alberto Artasanchez
3 (1)
Book Image

AWS for Solutions Architects

3 (1)
By: Alberto Artasanchez

Overview of this book

One of the most popular cloud platforms in the world, Amazon Web Services (AWS) offers hundreds of services with thousands of features to help you build scalable cloud solutions; however, it can be overwhelming to navigate the vast number of services and decide which ones best suit your requirements. Whether you are an application architect, enterprise architect, developer, or operations engineer, this book will take you through AWS architectural patterns and guide you in selecting the most appropriate services for your projects. AWS for Solutions Architects is a comprehensive guide that covers the essential concepts that you need to know for designing well-architected AWS solutions that solve the challenges organizations face daily. You'll get to grips with AWS architectural principles and patterns by implementing best practices and recommended techniques for real-world use cases. The book will show you how to enhance operational efficiency, security, reliability, performance, and cost-effectiveness using real-world examples. By the end of this AWS book, you'll have gained a clear understanding of how to design AWS architectures using the most appropriate services to meet your organization's technological and business requirements.
Table of Contents (20 chapters)
1
Section 1: Exploring AWS
4
Section 2: AWS Service Offerings and Use Cases
11
Section 3: Applying Architectural Patterns and Reference Architectures
17
Section 4: Hands-On Labs

Elastic load balancer types

In August 2016, AWS launched a new service called ALB. ALB allowed users of the service to direct traffic at the application level.

The old ELB service offering can still be used and it was renamed Classic Load Balancer. As if things were not confusing enough, a third type of ELB was later launched, named the network load balancer. In this section, we will try to understand the differences between all of them and when to use one versus the others.

Classic Load Balancers

A Classic Load Balancer (CLB) can route traffic using the transport layer (Layer 6, TCP/SSL) or the application layer (Layer 7, HTTP/HTTPS). CLBs currently have a requirement where the load balancer needs a fixed relationship between the instance port of the container and the load balancer port. As an example, you can map the load balancer using port 8080 to a container instance using port 3131 and to the CLB using port 4040. However, you cannot map port 8080 of the CLB to port...