username

aws_access_key_id

aws_secret_access_key

aws_region

Github_Token

domain

Git_username

Become an AWS pro with insights from a seasoned Amazon engineer. Get hands-on with essential AWS services like DynamoDB, S3, and EC2. No setup, no cleanup, no hassle.

local.tar.gz

NodeHelloWorld

NodePackageChange

NodeGithub

InfrastructureAsCode

ADCodebuildGithub

AutomaticDeployments1

AutomaticDeployments2

LoadBalancing1

Scaling1

Production1

CustomDomain1

Https1

NetworkSecurity1

NodeGithub-copy

AutomaticDeployments1-copy

Production1-copy

CustomDomain1-copy

Https1-copy

NetworkSecurity1-copy

This is not your typical AWS reference course. You won’t find most of the knowledge that's shared here in the AWS docs. The goal here is to help you realize which AWS features you’d be foolish not to use — features that have passed the test of time by being at the backbone of most things on the Internet.

In this course, you'll learn a technique used to help make reliable technical choices without getting paralyzed in the face of so many options. You’ll start by going through the most fundamental services AWS offers such as DynamoDB, S3, EC2. Each section breaks down how it’s used, the pros and cons, why you should (or shouldn't) be using it, and more.

This course was written by a former Amazon engineer with 15 years of experience working on AWS.

The Good Parts of AWS: Cutting Through the Clutter

# Objective
- Run our application on more than one EC2 instance.

# Steps

- Add an Application Load Balancer.

---

# Adding the load balancer

 Until now, we have been relying on EC2's default network configuration, but by adding a load balancer we're going to have to explicitly define a VPC setup in our CloudFormation template.

We're also going to make sure that our two instances will be running in separate availability zones. This is a fundamental requirement for ensuring high availability when using EC2. We recommend James Hamilton's video [Failures at Scale and How to Ignore Them](https://www.youtube.com/watch?v=cwPZ6EkwUzs) from 2012 as a good introduction to how AWS thinks about availability zones and high availability.

The VPC and subnets will require IP address allocations, for which we need to use CIDR (Classless inter-domain routing) notation. A full discussion of CIDR concepts is beyond the scope of this book, but AWS has some documentation about this topic in [VPC sizing](https://docs.aws.amazon.com/vpc/latest/userguide/VPC_Subnets.html) and [VPC design](https://aws.amazon.com/answers/networking/aws-single-vpc-design/). For our purposes, we will be allocating our VPC addresses from one of the [RFC 1918](https://tools.ietf.org/html/rfc1918) private address ranges: `10.0.0.0 - 10.255.255.255`.

The CIDR notation for that whole address range is `10.0.0.0/8`. VPC allows us to allocate up to half of that range with a notation of `10.0.0.0/16`, which corresponds to 65,536 unique IP addresses. We'll split it evenly into 4 subnets of 16,382 addresses each: `10.0.0.0/18`, `10.0.64.0/18`, `10.0.128.0/18`, and `10.0.192.0/18`. We're going to use two blocks of addresses right now, and the other two when we get to the topic of network security.

The following might look very complicated, but it's mostly boilerplate configuration. You will rarely need to change any of these settings.

So, let's start by adding our VPC and two subnets to our CloudFormation template.

Load Balancing: Add an Application Load Balancer

Before Getting Started

Part 1: The Good Parts

Part 2: The Bootstrap Guide

Host Our Application on EC2 Instance

Infrastructure as Code

Automatic Deployments: Create a CI/CD Pipeline

Load Balancing: Add an Application Load Balancer

Scaling: Add an Auto Scaling Group

Conclusion

Load Balancing: Add an Application Load Balancer

Objective

Steps

Adding the load balancer