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

## A linked list in the cloud

You can think of a Kinesis stream as a highly-durable linked list in the cloud. The use cases for Kinesis are often similar to those of SQS—you would typically use either Kinesis or SQS when you want to enqueue records for asynchronous processing. 

# Kinesis vs SQS

The main difference between the two services is:
- SQS can only have one consumer, while Kinesis can have many. 
- Once an SQS message gets consumed, it gets deleted from the queue. But Kinesis records get added to a list in a stable order, and any number of consumers can read a copy of the stream by keeping a cursor over this never-ending list. 
- Multiple consumers don’t affect each other, and if one falls behind, it doesn’t slow down the other consumers. 
- Whenever consumers read data out of Kinesis, they will always get their records in the same order.

# Cheaper/cost effective

In addition to supporting multiple consumers, another benefit of Kinesis over SQS is that it can be a lot cheaper. For example:
- Putting 1 KB messages in SQS at an average rate of 500 messages per second will cost you $34.56 per day. A Kinesis stream with 50% capacity headroom can handle that same volume for just $0.96 per day. So there can be about a massive difference in cost.

> **Let's do a fun exercise:** Use the below widget to calculate the cost of putting a certain size (KB) message at an average rate of certain number of messages per second per day to a Kinesis stream. $0.02 is the cost of putting a million messages to a Kinesis stream per day. You just have to put the *number* of **messages** per second, and the size of each message in KB. It will automatically generate the cost per day in the next cell.   



Kinesis: A linked list in the cloud and it's pros and cons will be discussed in this lesson.

Media Service: Kinesis

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

Media Service: Kinesis

A linked list in the cloud

Kinesis vs SQS