AWS - Everything You Need to Know

please star the repo tanjiro :)

Table of Contents	Link
☁️ Cloud Computing	Cloud Computing
🌐 Networking	Networking
🔄 Route 53	Route 53
⚙️ Compute	Compute
📦 Containers	Containers
💾 Storage	Storage
🗄️ Database	Database
🏗️ Cloud Architecture	Cloud Architecture
📈 Automatic Scaling & Monitoring	Automatic Scaling & Monitoring

What is Cloud Computing?

Cloud computing is the on-demand delivery of computing power, database storage, applications, and other IT resources via the internet with a pay-as-you-go pricing model. It enables you to shift from thinking of infrastructure as hardware to thinking of it as software.

Cloud Service Models

IaaS (Infrastructure as a Service)
PaaS (Platform as a Service)
SaaS (Software as a Service)

Why Cloud Computing Came into Existence

Before cloud computing, organizations managed their own racks and servers on-premises. This approach had several challenges:

Underutilization of Resources: Resources were often not fully utilized.
Scalability Issues: Scaling instantly was challenging and required guessing future usage.
High Maintenance Costs: Managing hardware and software infrastructure was a costly and time-consuming task.

Cloud computing was developed to address these issues, offering a more flexible, scalable, and cost-effective solution.

Cloud Service Models

Infrastructure as a Service (IaaS)

Provides access to networking features, computers (virtual or dedicated hardware), and data storage space. It offers the highest level of control over IT resources.

Example: Using Amazon EC2.

Platform as a Service (PaaS)

Removes the need to manage the underlying infrastructure (usually hardware and operating systems). Focuses on the deployment and management of your applications.

Example: Using Elastic Beanstalk.

Software as a Service (SaaS)

End-user applications are delivered over the internet.

Example: Slack, Gmail.

Six Advantages of Cloud Computing

Pay-as-you-go: Pay only for the amount you consume, reducing hardware and maintenance costs.
Eliminate Guessing Capacity: Scale on demand, avoiding over-provisioning.
Increased Speed: Access resources quickly and efficiently.
Stop Spending on Racks and Stacks: No need to maintain data centers.
Go Global in Minutes: Deploy your application in multiple regions worldwide.
Massive Economies of Scale: The shared infrastructure model reduces costs for everyone.

What is a Web Service?

A web service is any piece of software that is available over the internet and uses standardized formats like JSON or XML for request and response between applications.

EC2: Complete control over AWS resources.
Lambda: Run code without managing servers.
Elastic Beanstalk: Deploy, manage, and scale web apps.
Lightsail: Lightweight cloud platform for simple web apps.
Batch: Process hundreds of thousands of batch workloads.
Outposts: Extend AWS infrastructure to on-premises data centers.
Fargate: Implement containers or microservices architecture.

AWS Pricing Model

Compute: Charged per second, varying by instance type.
Storage: Typically charged per GB/hour.
Data Transfer:
- Outbound data is aggregated and charged per GB.
- Inbound data transfer has no charge.

Traditional Infrastructure vs. Cloud Computing

Traditional Infrastructure	Cloud Computing
Equipment	No upfront expense
Resources and administration	Pay for what you use
Contracts	Improve time to market
Costs	Scale up and down

VPC

An isolated section of the AWS cloud where you can launch AWS resources in a virtual network that you define.

Total Cost Ownership (TCO)

A comparison between on-premises infrastructure vs. cloud infrastructure, including costs like server storage and IT labor.

AWS Billing Dashboard

Includes AWS Budgets, cost and usage reports, cost explorer, forecast, and AWS pricing calculator.

AWS Global Infrastructure

AWS regions are geographical areas.
- Data replication across regions is controlled by you.
- Communication between regions uses AWS backbone infrastructure.
A region typically consists of two or more availability zones.
Selecting a region:
- Data governance & legal requirements
- Proximity to customers (latency)
- Services available in the region
- Costs (vary by region)

Each region has multiple availability zones.
Each availability zone is a fully isolated partition.
- 69 availability zones
- Availability zones consist of discrete data centers
- Designed for fault tolerance and isolation
- Interconnected with other availability zones by network
- AWS recommends replicating data and resources across availability zones for resiliency

Data Centers

Designed for security
Where data resides and data processing occurs
Each data center has redundant power, networking, and connectivity, housed in a separate facility
Each data center has 50k to 80k physical servers
Point of Presence:
- Route 53 to reduce latency
- AWS CloudFront is a content delivery network to end users, reducing latency

Elasticity and Scalability

Dynamic adaptation of capacity
Scalable infrastructure adapts to accommodate growth
Fault tolerance: Operates even in failure
High availability: Minimize downtime, ensure performance
No human intervention and backup generators

Example: An EC2 Linux instance in the US East (Ohio) region costs $0.0416 per hour, while in Tokyo, it costs $0.0544 per hour.

AWS Shared Responsibility Model

Customer Responsibilities (In the Cloud)

Customer data
Platform, applications, IAM
OS, network, firewall configuration, EC2 instance
Client-side and server-side data encryption
Network traffic protection
Data integrity and authentication

AWS Responsibilities (Of the Cloud)

Software
Compute, storage, database, networking
Hardware infrastructure
Regions, edge locations, availability zones

AWS Services

Compute
Storage
Database
Networking

Infrastructure

AWS Responsibilities

Physical data centers security
Intrusion detection: Network infrastructure
Virtualization infrastructure: Instance isolation
Hardware and software infrastructure: OS, auditing, etc.
- Example: EC2 instances isolated from other customers

Customer Responsibilities

EC2 instance OS
Security group configuration
OS host-based firewalls
Network configurations
Account management
Passwords, role-based access

IaaS (Infrastructure as a Service)

Examples: EC2, VPC, Elastic Block Store
More flexibility
Configuration and networking

PaaS (Platform as a Service)

Examples: Elastic Beanstalk, RDS, Lambda Functions
No need to manage infrastructure
AWS handles OS, database, patching, firewall configuration
Focus on code
Disaster recovery

AWS Identity & Access Management (IAM)

Example: Think of it like a school database access where the principal has the highest authority access of all resources, and the least is given to students.
Use IAM to manage access to AWS resources, e.g., EC2 instance/S3 bucket -> resources.
A resource is an entity that you can work with.
- Control who can terminate EC2 instances.
- Who can access the resources.
- Which resources can be accessed, and what can the user do to the resource?
- How resources can be accessed?
IAM Components:
- IAM User
- IAM Group: DBA, auditors, developers
- IAM Policy: Document that defines which resources can be accessed and the level of access
- IAM Roles: Grant permissions

Note

Follow the principle of least privilege (minimal set of permissions required).

Example: S3 bucket IAM policy example:

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "Allow Akua to list objects in the bucket",
            "Effect": "Allow",
            "Principal": {
                "AWS": "arn:aws:iam::12345678901:user/Akua"
            },
            "Action": [
            "s3:ListBucket"
            ],
            "Resource": "arn:aws:s3:::amzn-s3-demo-bucket"
        }
    ]
}

Example: An application that runs on EC2 needs access to S3.

Solution:

Define an IAM policy that grants access to S3.
Attach the policy to a role.
Allow EC2 instance to assume the role.

Data Security in AWS

Encryption encodes data with a secret key, making it unreadable.
- AWS KMS can manage your secret keys.
- AES-256 encryption algorithm.
Encryption of Data in Transit:
- Data moving across a network.
- TLS (Transport Layer Security) -> SSL -> AES-256.
- AWS Certificate Manager provides a new way to manage and renew TLS/SSL certificates.
Secure HTTP(S) creates a secret tunnel.
Use SSL/TLS for bidirectional exchange of data.
SSL/TLS:
- Secure network communications and establish the identity of websites over the internet.
- Web traffic over HTTP is not secure.
- HTTPS is protected from man-in-the-middle attacks and eavesdropping due to bidirectional communication and encryption by SSL.

Networking Basics

A computer network is formed when two or more client machines are connected to share resources.
- A network can be partitioned into subnets and requires a networking device such as a router or switch.

Each client machine has a unique IP address.
- Example:
  - 192 = 11000000, 0 = 00000000, 2 = 00000010, 0 = 00000000
- IPv4 (32 bits): 192.0.2.0
- IPv6 (128 bits): 2600:1f18:22ba:8c00:ba86

CIDR (Classless Inter-Domain Routing)

Classless Inter-Domain Routing (CIDR) is a method of IP address allocation and routing that allows for more efficient use of IP addresses. CIDR is based on the idea that IP addresses can be allocated and routed based on their network prefix rather than their class, which was the traditional way of IP address allocation. A CIDR address is expressed as an IP address and is the first address of the network.

Advantages of CIDR

Efficient use of IP addresses: CIDR allows for more efficient use of IP addresses, which is essential as the pool of available IPv4 addresses continues to shrink.
Flexibility: CIDR offers more flexible allocation of IP addresses, which is beneficial for organizations with complex network requirements.
Better routing: CIDR enables more efficient routing of IP traffic, leading to improved network performance.
Reduced administrative overhead: CIDR simplifies the management of IP addresses and routing, reducing administrative overhead.

Example: 192.0.2.0/24
The last number (24) indicates that the first 24 bits must be fixed, and the last 8 bits are flexible, giving 2^8 = 256 IP addresses.

Range: 192.0.2.0 to 192.0.2.255.
Special Cases:
- Fixed: 192.0.2.0/24
- Flexible: 0.0.0.0/0

OSI Model

The OSI Model explains how data travels over a network.

Layer	Number	Function	Protocol
Application	7	Provides means for applications to access the network	HTTPS, FTP, LDAP, DHCP
Presentation	6	Handles encryption and ensures that the application layer reads data correctly	ASCII, ICA
Session	5	Manages orderly data exchange	NETBIOS, RPC
Transport	4	Supports host-to-host communication	TCP, UDP
Network	3	Manages routing and packet forwarding (routers)	IP
Data Link	2	Ensures reliable data transfer across the physical link	ARP
Physical	1	Transmits the raw bit stream (hubs)	Ethernet, FDDI

Example: When a web browser sends a request to www.google.com, the following sequence occurs:

Application layer -> Presentation layer -> Session layer -> Transport layer (TCP/IP) -> Network layer (IP) -> Data link layer (MAC) -> Physical layer (Ethernet).

The OSI model ensures seamless data transmission from one network to another.

VPC (Virtual Private Cloud)

Definition:
A VPC enables you to provision a logically isolated section of the AWS Cloud where you can launch AWS resources in a virtual network that you define.
Control Over Networking Resources:
VPC provides control over your virtual networking resources, including:
- Selection of IP address ranges (IPv4, IPv6)
- Creation of subnets
- Configuration of network gateways and route tables
Customization:
You can customize the network configuration for your VPC and use multiple layers of security.
Example Use Case:
- Create a public subnet for web servers to access the public internet.
- Use RDS in a private subnet to restrict public internet access.
Security:
VPC allows the use of security groups and network access control lists (Network ACLs) to help control access to EC2 instances in each subnet.
Key Points:
- VPCs are logically isolated and dedicated to your account.
- Subnets are ranges of IP addresses within a VPC.
- A VPC belongs to a single AWS region and contains subnets that belong to a single availability zone.
- Subnets can be public or private.

Subnets

Definition:
A range of IP addresses in a VPC. Public subnets have direct access to the internet, while private subnets do not.
Reserved IP Addresses Example:
- A VPC with an IPv4 CIDR of 10.0.0.0/16 has 65,536 total IP addresses.
- If divided into 4 equal-sized subnets, only 251 IP addresses are available per subnet as 5 are reserved.
Example:
- CIDR (10.0.0.0/24) | Reserved for:
  - 10.0.0.0 | Network address
  - 10.0.0.1 | Internal communication
  - 10.0.0.2 | DNS
  - 10.0.0.3 | Future use
  - 10.0.0.255 | Network broadcast address
Elastic IP Address:
Allocate and remap Elastic IPs at any time.
Route Tables:
Control traffic for a subnet.

Internet Gateway

Definition:
An Internet Gateway allows communication between EC2 instances in your VPC and the internet.
Route Table Example:
- Destination | Target
  - 10.0.0.0/16 | Local
  - 0.0.0.0/0 | Internet Gateway ID

NAT Gateway (Network Address Translation Gateway)

Definition:
Allows instances in private subnets to connect to the internet or AWS services while preventing the internet from initiating a connection to them.
VPC Sharing:
Share a subnet with other AWS accounts within the same organization, enabling services like EC2, RDS, Lambda, and Redshift.
VPC Peering:
A VPC-to-VPC connection.
AWS Direct Connect:
Connects a VPC to a remote network.

Security Groups

Definition:
Acts as a virtual firewall for your instances, controlling inbound and outbound traffic.
Characteristics:
- Operates at the instance level, not the subnet level.
- Default Security Group: Denies all inbound traffic and allows all outbound traffic.

Type	Source/Destination	Protocol	Port Range	Description
Outbound	0.0.0.0/0	All	All	IPv4 IP
Outbound	::/0	All	All	IPv6 IP
Custom Rules	0.0.0.0/0	TCP	80	HTTP (IPv4)
Custom Rules	::/0	TCP	443	HTTPS (IPv4)

Example:
Incoming web traffic is distributed among a group of web servers located in different Availability Zones to ensure no single server is overwhelmed.

SGs vs. ACLs (Security Groups vs. Network Access Control Lists)

Scope: Instance level | Subnet level
Rules: Allow rules only | Allow and deny rules
State: Stateful (return traffic allowed) | Stateless
Order of Rules: All rules are evaluated before a decision is made to allow traffic.

Example VPC Design for an AI Anime Website

Create a VPC with CIDR: 10.0.0.0/24.
Public Subnet: 10.0.0.0/25 - For the web server.
Private Subnet: 10.0.0.128/25 - For the database server.
Attach an Internet Gateway.
Routing:
- Public subnet -> Internet Gateway.
- Private subnet -> NAT Gateway.
Security Groups:
- Allow HTTP & HTTPS traffic.
Deploy EC2 Instances:
- Web server in the public subnet.
- Database server in the private subnet.
Use Multiple Availability Zones & Elastic Load Balancing.
Firewall Protection:
- NACLS and Security Groups to secure the VPC.

Route 53

Definition:
A highly available and scalable domain name system (DNS) service.
Functionality:
Route end users to internet applications by translating names like www.nicevibes.co into numeric IP addresses like 192.0.2.1 that computers use to connect with each other.
Supports:
- IPv4 and IPv6

DNS Overview

DNS as a Phonebook:
IP addresses of websites are stored as domain names, similar to how a phonebook stores names and numbers.

Note

Interview Question: Explain what happens when you hit a URL.

Routing Policies

Simple Routing:
Round-robin for single server environments or small portions of traffic to a server.
Weighted Round Robin:
Assign weights to resource record sets to specify frequency. Example: A/B testing with 90% traffic to the main website and 10% to a test website.
Latency Routing:
Improve global application performance by routing based on latency.
Geolocation Routing:
Route traffic based on user location.
Geoproximity Routing:
Route traffic based on your resources.
Failover Routing:
Failover to a backup site if your primary site becomes unreachable.

DNS Failover Example:

High Availability:
1. Create two DNS records (CNAME) with failover routing.
2. Primary routing policy: Load balancer for web application.
3. Secondary policy: S3 static website.
4. Health checks ensure the primary site works correctly. If it fails, the web application stack fails over to the static backup site.

Amazon CloudFront

Content Delivery and Network Latency

Challenge of Network Communication:
Network performance can be impacted by latency, especially depending on the geographical location of the user.

Amazon CloudFront

Overview:
Amazon CloudFront is a fast, global, and secure Content Delivery Network (CDN) service.
Features:
- Global Network:
  Utilizes a global network of edge locations and regional edge caches.
- Self-Service Model:
  Allows users to manage and deploy CDN services easily.
- Pay-as-You-Go Pricing:
  Flexible pricing model based on usage.

Infrastructure

How it Works:
- When a customer makes a request, CloudFront responds with the IP address of the edge location closest to the customer.
- CloudFront obtains the requested data and caches it at the edge location to serve it quickly in subsequent requests.

Edge Locations

Definition:
Edge locations are data centers that CloudFront uses to deliver popular content quickly to users.
Regional Edge Cache:
- Acts as an intermediary between the origin server and global edge locations.
- Stores content that isn't popular enough to remain at the edge location but may still be requested.
- When data becomes stale, it is removed from the edge location's cache.

Which AWS networking service enables a company to create a virtual network within AWS?

Answer: Amazon VPC (Virtual Private Cloud)
A VPC allows you to provision a logically isolated section of the AWS Cloud where you can launch AWS resources in a virtual network that you define.

EC2 Instance (Elastic Compute Cloud)

Background Context

Running servers on-premise can be:

Expensive: Purchase, data centers, maintenance, staff.
Hardware Management: Managing peak workloads; server capacity sits idle.

EC2 Provides:

Virtual Machines to host the same applications as on-premise servers.
Example Uses: Application server, web server, game server, database server.
Full Control over the guest operating system (Linux/Windows).
Control Traffic to and from instances using security groups.

Key EC2 Components:

AMI: Linux/Windows (template)
Instance Type: The type of instance you want to launch.
Network Settings: Configure VPC, subnets, and public IP settings.
IAM Role: Attach a role to allow the instance to interact with AWS services.
User Data: Script that runs on the first start to customize the instance.
Storage Options: Configure the root volume and additional volumes.
Tags: Labels to categorize and organize resources.
Security Groups: Firewall rules that control traffic to the instance.
Key Pair: Used for secure access to your instances.

1. Amazon Machine Image (AMI)

Definition: A template used to create an EC2 instance.
Content: Windows or Linux OS, often with pre-installed software.

AMI Choices:

Quick Start: Linux and Windows AMIs provided by AWS.
My AMIs: Any AMIs that you created.
AWS Marketplace: Pre-configured templates from third parties.
Community AMIs: AMIs shared by others; use at your own risk.

AMI Flowchart:

Launch Instance (Unmodified Instance)
Connect to Instance and run a script (e.g., install Python)
Capture as a new AMI
Copy New AMI to any other regions

2. Instance Type

Memory (RAM)
Processing Power
Disk Storage and Space
Network Performance

Instance Types Table:

Instance Types	Name	vCPU	GB
General Purpose	t3.nano	2	0.5
Compute Optimized	t3.micro	2	1
Memory Optimized	t3.small	2	2
Storage Optimized	t3.medium	2	4
Accelerated Computing	t3.large	2	8
	t3.xlarge	4	16
	t3.2xlarge	8	32

3. Specify the Instance Deployment under VPC

Deployment Location: Identify the VPC and optionally the subnet.
Public IP Assignment: To make it internet-accessible.

4. Attach IAM Role (Optional)

Purpose: Allows the EC2 instance to interact with other AWS services.
IAM Role: An AWS Identity and Access Management role attached to an EC2 instance within an instance profile.

Example:

Grant a role to S3, allowing an application on the instance to access an S3 bucket.

5. User Data Script (Optional)

Customization: Customize the runtime environment of your instance.
Execution: Script executes the first time the instance starts.
Strategic Use: Reduce the number of custom AMIs you need to build and maintain.

6. Specify Storage

Root Volume: Where the guest OS is installed.
Additional Volumes: Optionally attach more storage volumes.

Volume Configuration:

Size of the Disk: In GB.
Volume Type: Different types of SSDs and HDDs.
Retention: If the volume will be deleted when the instance is terminated.
Encryption: Should encryption be used?

Amazon EC2 Storage Options:

Amazon Elastic Block Store (Amazon EBS): Durable, block-level storage volumes.
Amazon Elastic File System (Amazon EFS): Mount a file system.
Amazon S3: Connect to Simple Storage Service.

Instance Characteristics:

Instance 1: Amazon EBS root volume type for the OS.
- OS volume survives after stopping and starting.
- Data in ephemeral volume 1 is lost.
Instance 2: Instance Store root volume type for the OS.
- All data stored in ephemeral volume 2 is lost, including the OS.

7. Add Tags

Tagging: Assign labels (key-value pairs) to AWS resources.
Benefits: Filtering, automation, cost allocation, and access control.

8. Security Group Settings

Firewall Rules: Control traffic to the instance outside the guest OS.
Rule Creation: Specify source, port number, protocol, and allowed source.

9. Identify the Key Pair

Key Pair: Consists of a public key (stored by AWS) and a private key file (stored by you).
Windows AMIs: Use the private key to obtain the administrator password.
Linux AMIs: Use the private key to SSH into your instance securely.

Another Option: Launch an EC2 Instance with the AWS CLI

AWS CLI Command Example:

aws ec2 run-instances --image0id ami-1a2b3c4d --count 1 --instance-type c3.large \
--key-name MyKeyPair --security-groups MySecurityGroup --region us-east-1

This command assumes that the key pair and security group already exist.

Amazon EC2 Instance Lifecycle

Elastic IP Address Consideration

Rebooting: Will not change IP addresses or DNS hostnames.
Stopping and Starting: Public IPv4 address and external DNS hostname will change, private IPv4 address and internal DNS hostname do not.
Persistent Public IP: Associate an Elastic IP address.

EC2 Instance Metadata

Data Retrieval: View instance data while connected.
- Browser: http://169.254.169.254/latest/meta-data/
- Terminal: curl http://169.254.169.254/latest/meta-data/

Example Retrievable Values:

Public IP address, private IP address, public hostname, instance ID, security groups, Region, Availability Zone.

Amazon CloudWatch for Monitoring

Monitoring EC2 Instances: Provides near-real-time metrics, charts, and historical data (15 months).
Basic Monitoring: Default, no additional cost, metric data sent every 5 minutes.
Detailed Monitoring: Fixed monthly rate, metric data delivered every 1 minute.

Amazon EC2 Cost Optimization

Amazon EC2 Pricing Models

On-Demand Instances

Pay: By the hour
Commitment: No long-term commitments
Eligibility: Eligible for the AWS Free Tier

Dedicated Hosts

Definition: A physical server with EC2 instance capacity fully dedicated to your use

Dedicated Instances

Definition: Instances that run in a VPC on hardware dedicated to a single customer

Reserved Instances

Payment Options: Full, partial, or no upfront payment for instances you reserve
Discount: Discount on hourly charge for that instance
Term: 1-year or 3-year term

Scheduled Reserved Instances

Definition: Purchase a capacity reservation that is always available on a recurring schedule you specify
Term: 1-year term

Spot Instances

Pricing: Instances run as long as they are available and your bid is above the Spot Instance price
Interruption: Can be interrupted by AWS with a 2-minute notification; options include terminated, stopped, or hibernated
Cost: Prices can be significantly less expensive compared to On-Demand Instances
Best For: Good choice when you have flexibility in when your applications can run

Benefits

	On-Demand Instances	Spot Instances	Reserved Instances	Dedicated Hosts
Cost & Flexibility	Low cost and flexibility	Large scale, dynamic workload	Predictability ensures compute capacity is available when needed	Save money on licensing costs Help meet compliance and regulatory requirements

Use Cases

The 4 Pillars of Cost Optimization

Pillar 1: Right Size

Provision Instances: Match the instances to your actual needs in terms of CPU, memory, storage, and network throughput.
Instance Types: Select the appropriate instance types for your use case.
Monitoring: Use Amazon CloudWatch metrics to assess instance utilization and identify idle instances.
Optimization: Downsize instances as needed.
Best Practice: Right-size instances before considering Reserved Instances.

Pillar 2: Increase Elasticity

Stop or Hibernate: For Amazon EBS-backed instances that are not actively in use, such as non-production development or test instances.
Automatic Scaling: Use scaling policies to adjust capacity based on usage.
Elasticity Types:
- Automated scaling
- Time-based scaling

Pillar 3: Optimal Pricing Model

Pricing Models: Choose the right pricing model based on your usage patterns.
Optimization:
- On-Demand and Spot Instances: For variable workloads.
- Reserved Instances: For predictable workloads.
- Serverless Solutions: Consider AWS Lambda for certain use cases.

Pillar 4: Optimize Storage Choices

Cost Reduction: Reduce costs while maintaining storage performance and availability.
EBS Volume Management:
- Resize EBS volumes as needed.
- Change EBS volume types if appropriate.
- Evaluate if performance requirements can be met with less expensive storage.
Examples: Amazon EBS Throughput Optimized HDD (st1) storage is typically cheaper than General Purpose SSD (gp2).
Cleanup: Delete unnecessary EBS snapshots.
Data Storage: Determine the most suitable storage destination.
- Consider Amazon S3 storage options with lifecycle policies to reduce costs.

Measure, Monitor, and Improve

Ongoing Process: Cost optimization should be continuous.
Recommendations:
- Define and enforce cost allocation tagging.
- Define metrics, set targets, and review regularly.
- Encourage cost-effective architecture designs.
- Assign responsibility for optimization to an individual or team.

Container Services

Container Basics

Definition: Containers are a method of operating system virtualization.
Benefits:
- Repeatable: Consistent environments across different stages (development, test, production).
- Self-Contained: Environments encapsulate everything needed to run the software.
- Efficiency: Faster to launch, stop, or terminate compared to virtual machines.

Note

Containers are smaller than virtual machines (VMs) and do not have a complete operating system. Instead, they use a virtualized OS and run as resource-isolated processes.

Feel free to adjust or expand as needed!

What is Docker?

Definition: Docker is a software platform that facilitates building, testing, and deploying applications quickly.
Containers: Run on Docker and are created from images (templates).
- Components: Containers include all the dependencies required for the application to run.

Containers vs VMs

Containers:
- Share the host OS kernel.
- More lightweight and faster to start.
Virtual Machines (VMs):
- Include a full OS along with the application.
- Generally more resource-intensive.

Amazon Elastic Container Service (Amazon ECS)

A highly scalable, fast, container management service.

Key Benefits

Orchestrates the running of Docker containers
Maintains and scales the fleet of nodes that run your containers
Removes the complexity of standing up the infrastructure
Integrated with features that are familiar to Amazon EC2 service users:
- Elastic Load Balancing
- Amazon EC2 security groups
- Amazon EBS volumes
- IAM roles

Amazon ECS orchestrates containers.

Amazon ECS Cluster Options

Do you want to manage the Amazon ECS cluster that runs the containers?

Yes: Create an Amazon ECS cluster backed by Amazon EC2
- Provides more granular control over infrastructure
No: Create an Amazon ECS cluster backed by AWS Fargate
- Easier to maintain, focus on your app

What is Kubernetes?

Comment: Kubernetes is open-source software for container orchestration. It deploys and manages containerized apps at scale. The same toolset can be used on-premises and in the cloud.

Complements Docker:
- Docker enables you to run multiple containers on a single OS host.
- Kubernetes orchestrates multiple Docker hosts (nodes).
Automates:
- Container provisioning
- Networking
- Load distribution
- Scaling

Amazon Elastic Kubernetes Service (Amazon EKS)

EKS: Enables you to run Kubernetes on AWS
Certified Kubernetes conformant
Supports Linux and Windows containers
Compatible with Kubernetes community tools and add-ons
Use Amazon EKS to:
- Manage clusters of Amazon EC2 instances
- Run containers that are orchestrated by Kubernetes on those instances

Amazon Elastic Container Registry (Amazon ECR)

Amazon ECR is a fully managed Docker container registry that makes it easy for developers to store, manage, and deploy Docker container images.

Supports:

Team collaboration
Access control
Third-party integration
Possible to use with Amazon EKS

Section 7: Introduction to AWS Lambda

AWS Lambda: Run code without servers. AWS Lambda is a serverless compute service.

Benefits of Lambda

Supports multiple programming languages
Completely automated administration
Built-in fault tolerance
Supports orchestration of multiple functions
Pay-per-use pricing

AWS Lambda Event Sources

AWS Lambda Function Configuration

Create lambda function: Give a name
Runtime environment:
- Python
- Node.js
Execution role to grant IAM permission to the function to interact with other services
Configure the function:
- Adding a trigger
- Add function code
- Specify the memory in megabytes (up to 3008 MB)
- Specify environment variables

Examples:

Schedule-based Lambda Function: Start and stop EC2 instances
Event-based Lambda Function: Create thumbnail images

AWS Lambda Limits

Soft limits per Region:
- Concurrent executions = 1,000
- Function and layer storage = 75 GB
Hard limits for individual function:
- Max function memory allocation = 3,008 MB
- Function timeout = 15 min
- Deployment package size = 250 MB unzipped, including layers

Section 8: Introduction to AWS Elastic Beanstalk

AWS Elastic Beanstalk: An easy way to get a web app up and running. A managed service that automatically handles:

Infrastructure provisioning and configuration
Deployment
Load balancing
Automatic scaling
Health monitoring
Analysis and debugging
Logging

No additional charge for Elastic Beanstalk. Pay only for the underlying resources that are used.

AWS Elastic Beanstalk Deployments

Supports web apps written for common platforms:
- Java, .NET, PHP, Node.js, Python, Ruby, Go, and Docker
You upload your code
Elastic Beanstalk automatically handles the deployment
Deploys on servers such as Apache, NGINX, Passenger, Puma, and Microsoft Internet Information Services (IIS)

Benefits of Elastic Beanstalk

Wrap-up

Which AWS service helps developers quickly deploy resources which can make use of different programming languages, such as .NET and Java?

Select your answer

AWS CloudFormation
AWS SQS
AWS Elastic Beanstalk
Amazon Elastic Compute Cloud (Amazon EC2)

Answer: AWS Elastic Beanstalk

Keywords:

Developers quickly deploy resources
Different programming languages

Module 7: Storage

Section 1: Amazon Elastic Block Store (Amazon EBS)

Storage

Provides persistent block storage volumes with Amazon EC2 instances
Called non-volatile storage
Replicated within AZ
AWS Storage options: block storage vs object storage
What if you want to change one character in a 1-GB file?

Amazon EBS

[!NOTE] Amazon EBS enables you to create individual storage volumes and attach them to an Amazon EC2 instance

Amazon EBS offers block-level storage
Volumes are automatically replicated within its AZ
Can be backed up automatically to Amazon S3 through snapshots

Uses include:

Boot volumes and storage for Amazon Elastic Compute Cloud (Amazon EC2) instance
Data storage with a file system
Database hosts
Enterprise app

Amazon EBS Volume Types

Snapshots

Point-in-time snapshots
Recreate a new volume at any time

Encryption

Encrypted Amazon EBS volumes
No additional cost

Elasticity

Increase capacity
Change to different types

Volumes, IOPS and Pricing

Volumes: Amazon EBS volumes persist independently from the instance
- All volume types are charged by the amount that is provisioned per month
IOPS:
- General Purpose SSD: Charged by the amount that you provision in GB per month until storage is released
- Magnetic: Charged by the number of requests to the volume
- Provisioned IOPS SSD: Charged by the amount that you provision in IOPS (multiplied by the percentage of days that you provision for the month)
Snapshots: Added cost of Amazon EBS snapshots to Amazon S3 is per GB-month of data stored
Data Transfer:
- Inbound data transfer is free
- Outbound data transfer across Regions incurs charges

Section 2: Amazon Simple Storage Service (Amazon S3)

Storage

Note

Amazon S3 is object-level storage

If you want to change part of a file, you must do the change and re-upload the entire file

Amazon S3 Overview

Data stored as objects in buckets
Virtually unlimited storage
Single object is limited to 5 TB
Designed for 11 9s of durability
Granular access to bucket and objects
Data private by default
Can set up notification:
- When object is added
- When object is deleted

Amazon S3 Storage Classes

Amazon S3 Standard: High availability, high durability, performance, frequently accessed data
Amazon S3 Intelligent-Tiering: Optimize cost by moving data to the most cost-effective access tier, long-lived data with unpredictable access pattern
Amazon S3 Standard-Infrequent Access (Amazon S3 Standard-IA): Data accessed less frequently, long-term storage
Amazon S3 One Zone-Infrequent Access (Amazon S3 One Zone-IA): Data accessed less frequently, stores data in a single availability zone
Amazon S3 Glacier: Secure, durable, low cost, data archiving, three retrieval options (minutes to hours)
Amazon S3 Glacier Deep Archive: Lowest cost, long-term retention, retrieved once or twice a year

Amazon S3 Bucket URLs (Two Styles)

Bucket Path-Style URL Endpoint: https://s3.ap-northeast-1.amazonaws.com/bucket-name
Bucket Virtual-Hosted-Style URL Endpoint: https://bucket-name.s3-ap-northeast-1.amazonaws.com
Data is redundantly stored in the Region
Designed for seamless scaling
Amazon S3:
- Automatically manage the storage
- Scales to handle high volume of requests
- Billed for what you use
Access the data anywhere:
- AWS CLI
- AWS Management Console
- SDK

Warning

Bucket names must be globally unique and DNS compliant: all lowercase, only letters, numbers, and dashes

Amazon S3 Common Scenarios

Backup and storage
Application hosting
Media hosting
Software

Amazon S3 Pricing

Pay for what you use:
- GBs per month
- Transfer OUT to other Regions
- PUT, COPY, POST, LIST, and GET requests
You do not pay for:
- Transfers IN to Amazon S3
- Transfers OUT from Amazon S3 to Amazon CloudFront or Amazon EC2 in the same region

Amazon S3: Storage Pricing

To estimate Amazon S3 costs:
- Types of storage classes
- Standard storage is for:
  - 11 9s of durability
  - 4 9s of availability
- S3 Standard-Infrequent Access (S-IA) is for:
  - 11 9s of durability
  - 3 9s of availability
- Amount of storage
- The number and size of objects
- Requests:
  - Number of requests (GET, PUT, COPY)
  - Type of requests
  - Different rates for GET requests
- Data transfer:
  - Pricing based on the amount of data transferred out of Amazon S3 Region
  - Data transfer in is free, but incur charges for data transferred out

Section 3: Amazon Elastic File System (Amazon EFS)

Storage

Note

Implements storage for EC2 instances

Features

File storage in the AWS Cloud
Works well for big data and analytics, media processing workflows, content management, web serving, and home directories
Petabyte-scale, low-latency file system
Shared storage
Elastic capacity:
- Gigabytes to petabytes of data
Supports Network File System (NFS) versions 4.0 and 4.1 (NFSv4)
Compatible with all Linux-based AMIs for Amazon EC2
Pay for what you use

Amazon EFS Architecture

Create your Amazon EC2 resources and launch your instance
Create your Amazon EFS file system
Create your mount targets in the appropriate subnets
Connect your Amazon EC2 instances to the mount targets
Verify the resources and protection of your AWS account

Amazon EFS Resources

Mount Target:
- Subnet ID
- Security groups
- One or more per file system
- Create in a VPC subnet
- One per AZ
- Must be in the same VPC
Tags:
- Key-value pairs

Section 4: Amazon S3 Glacier

Storage

Note

Secure, durable, and extremely low-cost data archiving

Amazon S3 Glacier Review

Designed to provide 11 9s of durability for objects
Supports encryption of data in transit/at rest through Secure Sockets Layer (SSL) or Transport Layer Security (TLS)
Vault lock: enforces compliance through a policy
Extremely low-cost for long-term archiving
Three options: expedited, standard, or bulk
- Retrieval times from a few minutes to hours

Amazon S3 Glacier Use Cases

Media asset archiving
Healthcare info archiving
Regulatory and compliance archiving
Scientific data archiving
Digital preservation
Magnetic tape replacement

Using Amazon S3 Glacier

RESTful web services
Java or .NET SDKs
Amazon S3 with lifecycle policies

Lifecycle Policies

Amazon S3 lifecycle policies enable you to delete or move objects based on age

AWS Storage Classes

Storage Comparison

Server-side Encryption

Server-side Encryption (SSE)

SSE-S3:
- Each object has a unique key
- AES 256
SSE-C:
- Own encryption keys
- AWS Key Management Service
- Scaled for the cloud
- Customer master keys
- IAM Console or API
- Access keys
- How keys can be used

Security with Amazon S3 Glacier

Control access with IAM
Amazon S3 Glacier encrypts your data with AES-256
Amazon S3 Glacier manages your keys for you

Wrap-up

A company wants to store data that is not frequently accessed. What is the best and cost-effective solution that should be considered?

Select your answer

Amazon S3 Storage Gateway
Amazon S3 Glacier
Amazon EBS
Amazon S3

Answer: Amazon S3 Glacier

Keywords:

Not frequently accessed
Cost-effective solution

Module 8: Databases

Section 1: Amazon Relational Database Service (RDS)

Unmanaged vs Managed Services

Unmanaged:
- Managed by you
- Includes scaling, fault tolerance, availability
- Provides more fine-tuned control
Managed:
- Built-in service
- Includes scaling, fault tolerance, availability
- Requires less configuration

Challenges of Relational Databases

Server maintenance and energy footprint
Software installation and patches
Database backups and high availability
Limits on scalability
Data security
OS installation and patches

Amazon RDS

Important

Amazon RDS provides a managed service for setting up and operating a relational database in the cloud.

Managed Services Responsibilities:
- You manage: Application optimization
- AWS manages:
  - OS installation and patches
  - Database software installation and patches
  - Database backups
  - High availability
  - Scaling
  - Power, racking, and stacking servers
  - Server maintenance

Amazon RDS DB Instances

In a VPC:
- Select IP address range
- Subnets
- Configure routing and access control lists
- High availability with Multi-AZ deployment:
- - Automatically generates a standby copy in another AZ within the same VPC

Warning

If the main database instance fails, Amazon RDS automatically brings the standby instance online

Amazon RDS Read Replicas

Features:
- Asynchronous replication
- Can be promoted to master if needed
Functionality:
- Use for read-heavy database workloads
- Offload read queries
Use Cases:

When to Use	Do Not Use When
- Complex transactions or complex queries	- Massive read/write rates
- Medium to high query or write rate (up to 30,000 IOPS)	- Sharding due to high data size or throughput demands
- No more than a single worker node or shard	- Simple GET or PUT requests and queries that a NoSQL database can handle
- High durability	- Relational database management (RDBMS) customization

Amazon RDS: Clock-Hour Billing and DB Characteristics

Clock-Hour Billing:
- Resources incur charges when running
Database Characteristics:
- Physical capacity
- Engine
- Size
- Memory class

Amazon RDS: DB Purchase Type and Multiple DB Instances

DB Purchase Type:
- On-Demand Instances: Compute capacity by the hour
- Reserved Instances: Low, one-time, upfront payment for DB instances reserved with a 1-year or 3-year term
Number of DB Instances:
- Provision multiple DB instances to handle peak loads

Amazon RDS Storage

Provisioned Storage:
- No charge
- Backup storage up to 100% of DB storage for an active DB
Charges:
- Backup storage for terminated DB instances
- Additional storage (GB/month)
- Backup storage in addition to provisioned storage

Amazon RDS: Deployment Type and Data Transfer

Requests:
- The number of input and output requests made to the DB
Deployment Type:
- Storage and I/O vary depending on whether you deploy to Single AZ or Multiple AZ
Data Transfer:
- No charge for inbound data transfer
- Tiered charges for outbound data transfer

Section 2: Amazon DynamoDB

Relational vs Non-Relational DB

Amazon DynamoDB:

[!NOTE] Fast and flexible NoSQL DB service for any scale

NoSQL DB tables can be scaled
Create tables and add items
Global tables automatically replicate across AWS regions
Virtually unlimited storage
Items can have differing attributes
No need to migrate schema
Low-latency queries
Scalable read/write throughput
Fault-tolerant architecture
Stored in SSDs
Encrypt data at rest
Set time to live
Automatically partitions data

Amazon DynamoDB Core Components

Tables, Items, and Attributes:
- Supports 2 types of primary keys:
  - Partition key
  - Sort key
- Items in a table must have a key

Section 3: Amazon Redshift

Introduction to Amazon Redshift

Features:

Note

Fast, fully managed data warehouse, simple and cost-effective to analyze data using SQL and business intelligence tools.

Pay for what you use
Complex analytics queries
Parallel processing
Only seconds for query execution
Architecture:
- Parallel processing
Automation and Scaling:
- Automate management, monitoring, and scaling
[!WARNING] Security is built-in with encryption of data
Compatibility:
- Supports standard SQL
- Connect with SQL clients, Java connectivity, Open DB connectivity
- Interact directly with AWS CLI or management console

Amazon Redshift Use Cases

Enterprise Data Warehouse (EDW):
- Migrate at a comfortable pace
- Experiment without large upfront cost or commitment
- Respond faster to business needs
Big Data:
- Low price point for small customers
- Managed service for ease of deployment and maintenance
- Focus more on data and less on database management
SaaS:
- Scale the data warehouse capacity as demand grows
- Add analytic functionality to app
- Reduce hardware and software costs

Section 4: Amazon Aurora

Amazon Aurora

Features:

[!NOTE] MySQL and PostgreSQL compatible relational DB built for the cloud
- Enterprise-class relational DB
- Automates time-consuming tasks (e.g., provisioning, patching, backup, recovery, failure detection, repair)
- Can reduce DB costs

Amazon Aurora Service Benefits

Performance and Availability:
- Fast and available
- Managed service
- Simple
- Pay-as-you-go
Compatibility and Resilience:
- Compatible with MySQL or PostgreSQL
- High availability with data stored in multiple AZs
- Data backed up to Amazon S3
- Up to 15 read replicas
- Instant crash recovery
- Removes buffer cache from DB process
- No need to replay the redo log

Wrap-up

Which of the following is a fully managed NoSQL DB service?

Amazon RDS
Amazon DynamoDB
Amazon Aurora
Amazon Redshift

Select your answer

**Answer**: Amazon DynamoDB

Module 9: Cloud Architecture

Section 1: AWS Well-Architected Framework

Architecture

Note

Architecture is the art and science of designing and building large structures.

It involves managing size and complexity, identifying business goals, and aligning tech deliverables with those goals while working with the delivery team.

What is the AWS Well-Architected Framework?

The AWS Well-Architected Framework provides a guide for designing infrastructures that are:

Secure
High-performing
Resilient
Efficient

It offers a consistent approach to evaluating and implementing cloud architectures, and provides best practices developed through lessons learned by reviewing customer architectures.

Pillars of the AWS Well-Architected Framework

Pillar: Identity and Access Management

Question Text: How do you manage credentials and authentication?

Credential and authentication mechanisms include passwords, tokens, and keys granting access directly or indirectly in your workload. Protect credentials with appropriate mechanisms to help reduce the risk of accidental or malicious use.

Best Practices:

Define requirements of identity and access management
Secure AWS account root user
Enforce use of multi-factor authentication
Automate enforcement of access controls
Integrate with centralized federation provider
Enforce password requirements
Rotate credentials regularly
Audit credentials periodically

Pillar: Operational Excellence

Focus: Run and monitor systems to deliver business value, and continually improve supporting processes and procedures.

Key Topics:

Managing and automating changes
Responding to events
Defining standards to successfully manage daily operations

Operational Excellence Design Principles:

Perform operations as code
Define entire workload (app and infra)
Limit human error
Consistent responses to events
Annotate documentation
Automate the creation of annotated documentation
Make frequent, small, reversible changes
Refine operations procedures frequently
Anticipate failure
Learn from all operational events and failures

Operational Excellence Questions:

Prepare:

How do you determine what your priorities are?
How do you design your workload to understand its state?
How do you reduce defects, ease remediation, and improve flow into production?
How do you mitigate deployment risks?
How do you know that you are ready to support a workload?

Operate:

How do you understand the health of the workload?
How do you manage workload and operation events?

Evolve:

How do you evolve operations?

Pillar: Security

Focus: Protect information, systems, and assets while delivering business value through risk assessments and mitigation strategies.

Key Topics:

Identifying and managing who can do what
Establishing controls to detect security events
Protecting systems and services
Protecting confidentiality and integrity of data

Security Design Principles:

Implement a strong identity foundation
- Principle of least privileges
- Separation of duties
Enable traceability
- Monitor, alert, and audit actions
- Integrate logs and metrics to automatically respond and take action
Apply security to all layers
- Defense-in-depth
Automate security best practices
- Improve ability to securely scale more rapidly and cost-effectively
Protect data in transit and at rest
- Classify data into sensitivity levels
- Use mechanisms such as encryption, tokenization, and access control
Keep people away from data
- Reduce risk of loss or modification of sensitive data due to human error
- Create tools to reduce manual processing of data
Prepare for security events
- Incident management process

Security Questions:

Identity and Access Management:

How do you manage credentials and authentication?
How do you control human access?
How do you control programmatic access?

Detective Controls:

How do you detect and investigate security events?
How do you defend against emerging security threats?

Infrastructure Protection:

How do you protect your networks?
How do you protect your compute resources?

Data Protection:

How do you classify your data?
How do you protect your data at rest?
How do you protect your data in transit?

Incident Response:

How do you respond to an incident?

Pillar: Reliability

Focus: Prevent and quickly recover from failures to meet business and customer demand.

Key Topics:

Setting up
Cross-project requirements
Recovery planning
Handling change

Reliability Design Principles:

Test recovery procedures
- Test how your system fails
- Validate recovery procedures
Automatically recover from failure
- Monitor systems for key performance indicators
- Configure system to trigger automated recovery when a threshold is breached
Scale horizontally to increase aggregate system availability
- Replace one large resource with multiple smaller ones
Stop guessing capacity
- Monitor demand and system usage
- Automate the addition or removal of resources to maintain the optimal level
Manage change in automation
- Use automation to make changes to infrastructure

Reliability Questions:

Foundations:

How do you manage service limits?
How do you manage your network topology?

Change Management:

How does your system adapt to changes in demand?
How do you monitor your resources?
How do you implement change?

Failure Management:

How do you back up data?
How does your system withstand component failure?
How do you test resilience?
How do you plan for disaster recovery?

Pillar: Performance Efficiency

Focus: Use IT and computing resources efficiently to meet system requirements and maintain efficiency as demand changes and technologies evolve.

Key Topics:

Selecting the right resource types and sizes based on workload requirements
Monitoring performance
Making informed decisions to maintain efficiency as business needs evolve

Performance Efficiency Design Principles:

Democratize advanced technologies
- Consume tech as a service
- Focus on product development
Go global in minutes
- Deploy systems in multiple AZs
Use serverless architectures
- Remove operational burden of maintaining servers
- Reduce costs
Experiment more often
- Comparative testing
Have mechanical sympathy
- Use tech approaches aligning best with what you want to achieve

Performance Efficiency Questions:

Selection:

How do you select the best performing architecture?
How do you select your compute solution?
How do you select your storage solution?
How do you select your database solution?
How do you select your networking solution?

Review:

How do you evolve your workload to take advantage of new releases?

Monitoring:

How do you monitor your resources to ensure they are performing as expected?

Tradeoffs:

How do you use tradeoffs to improve performance?

Pillar: Cost Optimization

Focus: Run systems to deliver business value at the lowest price point.

Key Topics:

Understanding and controlling when money is being spent
Selecting the most appropriate and right number of resource types
Analyzing spending over time
Scaling to meet business needs without overspending

Cost Optimization Design Principles:

Adopt a consumption model
- Pay only for the computing resources required
Measure overall efficiency
- Measure business output and associated costs
- Measure the gain you are making
Stop spending money on data center operations
- AWS does the heavy-lifting
Analyze and attribute expenditure
- Accurately identify system usage and cost
Use managed and application-level services to reduce the cost of ownership
- Lower cost per transaction

Cost Optimization Questions:

Expenditure Awareness:

How do you govern usage?
How do you monitor usage and cost?
How do you decommission resources?

Cost-Effective Resources:

How do you evaluate cost when selecting services?
How do you meet cost targets when selecting resource type and size?
How do you use pricing models to reduce cost?
How do you plan for data transfer changes?

Matching Supply and Demand:

How do you match the supply of resources with demand?

Optimizing Over Time:

How do you evaluate new services?

Reliability and Availability

Tip

"Everything fails, all the time" - Werner Vogels, CTO, Amazon.com

Reliability:

A measure of your system's ability to provide functionality when desired by the user.
Includes hardware, software, and firmware.
Mean time between failures (MTBF): Total time in service / Number of failures

Availability:

Normal operation time / Total time
A percentage of uptime (e.g., 99.9%) over time (e.g., 1 year)
Number of 9s: 5 9s means 99.999% availability

High Availability:

System can withstand some measure of degradation while still remaining available.
Downtime is minimized.
Minimal human intervention is required.

Factors Influencing Availability:

Fault Tolerance: Built-in redundancy of app components and their ability to remain operational.
Scalability: Ability of an app to accommodate increases in capacity needs without changing design.
Recoverability: Process, policies, and procedures related to restoring service after a catastrophic event.

AWS Trusted Advisor

An online tool that provides real-time guidance to help you provision your resources following AWS best practices. It looks at your entire AWS environment and gives real-time recommendations in:

Cost Optimization:
- Eliminating unused resources
- Commitment to reserve capacity
Performance:
- Checking service limits
- Service throughput
Security:
- Improving security of the app by identifying gaps
- Permissions
- Increasing availability and redundancy
Fault Tolerance:
- Service usage more than 80% of the service limit

Wrap-up Question: A SysOps engineer working at a company wants to protect their data in transit and at rest. What service could they use to protect their data?

Elastic Load Balancing
Amazon Elastic Block Store (Amazon EBS)
Amazon Simple Storage Service (Amazon S3)
All of the above

Select your answer

All of the above

Module 10: Automatic Scaling and Monitoring

Section 1: Load Balancing

Distributes incoming app or network traffic across multiple targets in a single or multiple Availability Zones (AZs). It scales your load balancer as traffic to your app changes over time.

Types of Load Balancers

How Elastic Load Balancing Works:

Application Load Balancers and Network Load Balancers: Register targets in traffic to the target groups.
Classic Load Balancers: Register instances with the load balancer.
Load balancer performs health checks to monitor the health of registered targets.

Elastic Load Balancing Use Cases:

High availability and fault-tolerant app
Containerized app
Elasticity and scalability
VPC
Hybrid environments
Invoke Lambda functions over HTTP(S)

Load Balancer Monitoring:

Amazon CloudWatch metrics: Used to verify system performance and create alarms if metrics go outside an acceptable range.
Access logs: Capture detailed information about requests sent to your load balancer.
AWS CloudTrail logs: Capture the who, what, when, and where of API interactions in AWS services.

Section 2: Amazon CloudWatch

Monitoring AWS Resources: To use AWS efficiently, you need insight into your AWS resources:

How do you know when you should launch more Amazon EC2 instances?
Is your app's performance or availability being affected by a lack of sufficient capacity?
How much of your infrastructure is actually being used?

Amazon CloudWatch:

Monitors:
- AWS resources
- Apps that run on AWS
Collects and Tracks:
- Standard metrics
- Custom metrics
Alarms:
- Send notifications to an Amazon SNS topic
- Perform Amazon EC2 Auto Scaling or Amazon EC2 actions
Events:
- Define rules to match changes in AWS environment and route these events to one or more target functions or streams for processing.

CloudWatch Alarms:

Create alarms based on:
- Static threshold
- Anomaly detection
- Metric math expression
Specify:
- Namespace
- Metric
- Statistic
- Period
- Conditions
Additional configuration and actions

Section 3: Amazon EC2 Auto Scaling

Why is Scaling Important?

Note

Scaling is the ability to increase or decrease the compute capacity of your app.

First graph: Unused capacity on most days of the week, not cost-optimized
Second graph: Under capacity on certain days

Warning

Automatic capacity scaling is necessary to support the fluctuating demands for service.

Amazon EC2 Auto Scaling:

Helps you maintain app performance
Enables you to automatically add or remove EC2 instances according to conditions that you define.
Detects impaired EC2 instances and unhealthy apps, and replaces the instances without your intervention.
Provides several scaling options:
- Manual
- Scheduled
- Dynamic (on-demand)
- Predictive

Typical Weekly Traffic at Amazon.com

November Traffic to Amazon.com

Auto Scaling Groups:

An Auto Scaling group is a collection of EC2 instances that are treated as a logical grouping for automatic scaling and management.

Scaling Out vs Scaling In

How Amazon EC2 Auto Scaling Works

Implementing Dynamic Scaling

AWS Auto Scaling:

Monitors your app and automatically adjusts capacity to maintain steady, predictable performance at the lowest possible cost.
Provides a simple, powerful user interface that enables you to build scaling plans for resources, including:
- Amazon EC2 instances and Spot Fleet
- Amazon Elastic Container Service (Amazon ECS) Tasks
- Amazon DynamoDB tables and indexes
- Amazon Aurora Replicas

Wrap-Up

Which service would you use to send alerts based on Amazon CloudWatch alarms?

Amazon Simple Notification Service
AWS CloudTrail
AWS Trusted Advisor
Amazon Route 53

Anwer

Amazon Simple Notification Service

Files

README.md

Latest commit

History

README.md

File metadata and controls

AWS - Everything You Need to Know

Table of Contents

What is Cloud Computing?

Cloud Service Models

Why Cloud Computing Came into Existence

Cloud Service Models

Infrastructure as a Service (IaaS)

Platform as a Service (PaaS)

Software as a Service (SaaS)

Six Advantages of Cloud Computing

What is a Web Service?

AWS Pricing Model

Traditional Infrastructure vs. Cloud Computing

VPC

Total Cost Ownership (TCO)

AWS Billing Dashboard

AWS Global Infrastructure

Data Centers

Elasticity and Scalability

AWS Shared Responsibility Model

Customer Responsibilities (In the Cloud)

AWS Responsibilities (Of the Cloud)

AWS Services

Infrastructure

AWS Responsibilities

Customer Responsibilities

IaaS (Infrastructure as a Service)

PaaS (Platform as a Service)

AWS Identity & Access Management (IAM)

Data Security in AWS

Networking Basics

CIDR (Classless Inter-Domain Routing)

Advantages of CIDR

OSI Model

VPC (Virtual Private Cloud)

Subnets

Internet Gateway

NAT Gateway (Network Address Translation Gateway)

Security Groups

SGs vs. ACLs (Security Groups vs. Network Access Control Lists)

Example VPC Design for an AI Anime Website

Route 53

DNS Overview

Routing Policies

DNS Failover Example:

Amazon CloudFront

Content Delivery and Network Latency

Amazon CloudFront

Infrastructure

Edge Locations

EC2 Instance (Elastic Compute Cloud)

Background Context

EC2 Provides:

Key EC2 Components:

1. Amazon Machine Image (AMI)

AMI Choices:

AMI Flowchart:

2. Instance Type

Instance Types Table:

3. Specify the Instance Deployment under VPC

4. Attach IAM Role (Optional)

Example:

5. User Data Script (Optional)

6. Specify Storage

Volume Configuration:

Amazon EC2 Storage Options:

Instance Characteristics:

7. Add Tags

8. Security Group Settings

9. Identify the Key Pair

Another Option: Launch an EC2 Instance with the AWS CLI

This command assumes that the key pair and security group already exist.

Amazon EC2 Instance Lifecycle

Elastic IP Address Consideration