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

When using AWS, you almost always want to use some CloudFormation (or a similar tool). It lets you create and update the things you have in AWS without having to click around on the console or write fragile scripts. It takes a while to get the hang of it, but the time savings pay off the initial investment almost immediately. Even for development, the ability to tear down everything cleanly and recreate your AWS set up in one click is extremely valuable



# Defining AWS resources with CloudFormation

With CloudFormation; 
- You define your AWS resources as a YAML script (or JSON, but we find YAML to be much easier to read and modify). 
- Then you point CloudFormation to your AWS account, and it creates all the resources you defined. 
- If you run the script again without making any changes, CloudFormation won’t do anything (it’s idempotent). 
- If you make a change to one resource, it will change only that resource, plus any other resources that depend on the modified one (if necessary). 
- If you change your mind about an update, you can safely tell CloudFormation to roll it back. 
- You can also tell CloudFormation to tear down everything it created, and it will give you your AWS account back in the original state (with a few exceptions).



Defining AWS resources with CloudFormation service and our rule of thumb of what services to manage by Cloudformation and what services should be avoided is going to be discussed in this lesson. 

Management & Governance: CloudFormation

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

Management & Governance: CloudFormation

Defining AWS resources with CloudFormation