Pre-requirements

cloud definition
explanation

cloud characteristics
cloud services
cloud models

Cloud Chracteristics are of 5 Types

NIST - National Institute of Standards and Technology

On-Demand Self Service

Broad network access

DATA CENTERS - GLOBALLY

server - location
another location

internet connectivity

elasticity -cloud

resource pooling

metered services
Pay as u Go

OS - Operating System
Application Software
Hardware

Server - Providing the Service

Virtualization - Gives the control the user

Virtulization Software --- HyperVisor (Imp Concept )

Cloud Services

1) IaaS - Infrastructure as a Services

2) PaaS - Platform
3) SaaS - Software

1) IaaS & 2) PaaS & 3) SaaS

Application
OS
Hardware ( cpu , mem, storage, network )
CLOUD DEPLOYMENT MODELS

PRIVATE CLOUD - Physical Machine --Transition--> Virtual Machine -- >Data Center

PUBLIC CLOUD - AWS , AZURE , GCLOUD , ORACLE etc.....
COMMUNITY -
HYBRID CLOUD

AWS GLOBAL INFRASTRUCTURES

AWS REGIONS
AWS AVAILABILITY ZONES (AZ)
AWS DATA CENTRES

1 Region --- 3 Az's --- 2 DataCentres for each Az

high bandwidth
low latency
highly available

fiber optic cables

EC2 - ECC - Elastic Compute Cloud

.ppk

.pem

for connecting the server in cmd

ssh -i pswdfilename username@ipaddress

Home-Work Complete Within ( 25-08-2023 )

OnDemand Instances
Reserved Instances
Spot Instances
Dedicated Hosts
Dedicated Instances

Benefits , UseCase , Differences

What Is An Instance?
An AWS EC2 Instance is nothing but a server in the cloud. Just like your physical
server, it comes with varying specs for compute, memory, networking, and storage.
There are a total of 11 instance types for all types of workloads. Choosing between
these instance types is a topic for another post.
Here, we’ll cover something even more basic—understanding how to strike the right
balance between performance and price of AWS instances.

Types of AWS Instances

AWS Instances: EC2 Types
REGULAR EC2 INSTANCE
These are the default AWS instances that most applications use. They are instances
in the cloud that are shared between multiple AWS customers.
AWS provides isolation between each user’s data. However, multi-tenancy normally
comes with the “noisy neighbor” issue, where neighboring instances could affect the
performance of your app if they hog up resources on the same host as you.
To counter this problem, you have a couple of options.

SPOT INSTANCE

With a Spot instance, you can save money by purchasing the hourly compute power of
someone else’s unused EC2 instance.
The “Spot Price” is what you’ll pay. Spot instances are useful for running tasks
that aren’t critical, and can also be interrupted without disruption (AWS calls
these “fault-tolerant” workloads).
Think batch jobs, compute-intensive analysis, temporary auto-scaling to meet a
short-term spike, or another similar usage.

OPTIMIZED EC2 INSTANCE

Compute, memory, and storage optimized EC2 instances are also available. These
instances are designed to deliver an optimized service level for a specific area
(storage, memory, or compute). For example, optimized compute instances offer
dedicated CPUs of specific varieties and speeds, along with standard network
bandwidth and storage options. Storage optimized instances provide optimized
access to local storage access (i.e. on the same host) – options include NVMe SSDs
or HDDs combined with standard selections for vCPU and memory.

DEDICATED INSTANCE
These are virtual private cloud (VPC) instances that are blocked for use by a
single customer. They are Isolated at the host level, so all instances running on
the host would be reserved for a single customer. But there’s another option if you
want even more isolation and control over your infrastructure.

DEDICATED HOST
Dedicated Hosts enable the same level of isolation as Dedicated Instances, but
additionally, they give you visibility into the physical host. This is required if
your applications use libraries and frameworks with licensing terms that restrict
them to a single server. Or some applications may need to be hosted on a dedicated
server for compliance purposes. In these cases, a Dedicated Instance is your only
option.

Dedicated Instances are billed by the number of instances, whereas Dedicated Hosts
are billed by the host, irrespective of the number of instances you run on each
host. With that in mind, we’re ready to move to the next important section,
understanding the various pricing options for AWS instances.

How much does it cost to run an EC2 instance?

The kind of pricing you choose will greatly decide your TCO.

ON-DEMAND PRICING
With on-demand pricing, you pay by the hour for usage of an AWS instance. This is
the benchmark pricing for AWS instances—meaning that you compare other pricing
models with this one when deciding which is best for you. The benefit of on-demand
pricing is that you don’t have to plan in advance how many instances you need. This
gives you maximum flexibility. However, it comes at a cost. On-demand pricing is
the highest of the lot.

SPOT INSTANCES
With Spot Instances, users bid for the price of spare EC2 Instances. There’s a
market price for spare instances, and only if this market price meets your instance
will you be allotted the instance. Similarly, when the market price reduces, you’ll
automatically lose your instance so your charge doesn’t shoot up. This model is a
bit more complex than on-demand pricing, but it could save 50-90% of your total
costs.

RESERVED INSTANCES
Finally, if you can reliably predict approximately how much compute resources your
applications need in advance, you should consider Reserved Instances (RIs). In this
model, users lock in.

AWS instances for a span of 1 or 3 years, and get a significant discount as

compared to on-demand prices. Reserved Instances are assigned to specific
Availability Zones, so if you need control over your app’s performance globally,
this may be a drawback.

If your concern is that your compute requirements may change over 3 years, AWS
allows you to choose convertible Reserved Instances, so you can switch between
instance types—for example, from an M3 to a C4. However, you can shift down to a
small instance like a T2.

LINUX INTERFACE

user
shell gnome(gui) , shell , bash
kernel
hardware

MAC INTERFACE

user
shell unix - kshell - korn shell
kernel
hardware

WINDOWS INTERFACE

user
shell GUI, CLI ,POWERSHELL
kernel
hardware

To change from standard user to root acnt ($ to #) ---> sudo su

To create a file name ---> cat > (file name)
To see the file content ---> cat (file name)
To Check the Files ---> ls
To add a New Line to the existing File ---> cat >> (file name)

webserver -website

personal website content

web software
 yum - amazon linux
apt-get - ubuntu

1)Update the OS - yum update -y

2)Install httpd server/software - yum install httpd -y | yum install httpd
3)TO start a service - systemctl start httpd (Manages the services
start /restart / debug() );

Advantages of On-Demand Instances:

1. Flexibility: On-demand instances offer unmatched flexibility, allowing you to

launch and terminate them at will, without any long-term commitments or upfront
contracts.

2. Instant Availability: These instances are readily accessible, providing

immediate access to computing resources without any waiting period.

3. Predictable Billing: With a pay-as-you-go model, on-demand instances ensure

predictable billing, as you are charged only for the hours or minutes you use,
eliminating upfront costs.

4. No Capacity Planning: As there are no upfront commitments, extensive capacity

planning becomes unnecessary. You can easily scale resources up or down based on
your changing needs.

5. Ideal for Short-Term Projects: On-demand instances are perfect for short-term
projects or workloads with fluctuating resource requirements, as you can easily
adjust resources on the fly.

Use Cases for On-Demand Instances:

1. Development and Testing: On-demand instances are widely utilized for development
and testing environments, where resources are needed temporarily and can be shut
down when not in use, optimizing cost efficiency.

2. Bursty Workloads: Workloads experiencing unpredictable spikes in demand benefit

from on-demand instances. You can seamlessly scale resources during high-demand
periods and scale down when demand decreases.

3. Urgent or Unplanned Workloads: When faced with unplanned workloads or requiring

additional resources urgently, on-demand instances provide a quick and convenient
solution.

4. Short-Lived Applications: On-demand instances are cost-effective for running

applications that only need to be active for a short time, such as one-time data
processing tasks.

TO Remove all the directories from the directory use rm -rf * in the current
directory
to remove all the file's from the directory use rm * in the current directory
NETWORK - 3TYPES

END DEVICES -USER

INERMEDIATERY -NETWORK SWITCHED ,ROUTERS , NETWORK HUBS ,FIREWALLS
CONNECTIONS - CABLES, WIFI,

Commands:

ipconfig
ping [name(or)ipaddress]
tracert [name(or)ipaddress]

5 Types of Classes

a ,b, c ,d, e

Class Ranges These Are ClassFul Ranges

a 0 - 127
b 128 - 191
c 192 - 223 Unicasting
d 224 - 239 Multicasting
e 240 - 255 R&D , Special Use

A Class - 0 - 127

N.H.H.H -- > ' N - NETWORK , H - HOST '

B Class - 128 - 191

N.N.H.H -- > ' N - NETWORK , H - HOST '

C Class - 192 - 223

N.N.N.H -- > ' N - NETWORK , H - HOST '

Default Subnet Mask

A - 255.0.0.0 -- > 11111111.00000000.00000000.00000000

B - 255.255.0.0

C - 255.255.255.0

Class A

255.0.0.0
1.255.255.255

192.68.160.75 --- > 192.68.160.

0 - 255 1-255 -- 254

n.n.n.h

255th ip

Network Id -- First Ip in the Network

Broadcast Id -- Last Ip in the Network
Id - Identification , Not Usable Ip

A Class - 127.0.0.0 -- > 127.255.255.255

Complete Range is dedicated for Loop Back

B Class - 169.254.0.0 --> 169.254.255.255

Complete Range - APIPA -- >Automatic Private Ip Addressing

Security Group --- > NACL -- > Network Access Control List

ICMP -- > Internet Control Messaging Protocol

APIPA -- > Automatic Private Ip Addressing --- > 169.254.0.0

DHCP -- > Dynamic Host Configuration Protocol

Private IPv4 Address Space

Class Address Range Network Prefix

A 10.0.0.0 - 10.255.255.255 10.0.0.0/8

B 172.16.0.0 - 172.31.255.255 172.16.0.0/12

C 192.167.0.0 - 192.167.255.255 192.167.0.0/16

Private Ip Address - Intranet

Public Ip Address - Internet

1 - 127

128 - 191

192 - 223

Subnet

Internet GateWay
Routing Table

NAT

Subnetting

Classless Ip Addressing

Matching Bit - 1 - Network

Ignore Bit - 1 - Network

255.0.0.0 /8 Prefix Value

255.255.0.0 /16

255.255.255.0 /24

Host Requirement 30 Servers - ip - 2^n

2^4 - 2^5 - 2^6

2^5 - 2^h - 32 - 2 = 30

New Subnet Mask

Writing range 30 2^h -32

Step 1 : Requirement 60 Hosts

Step 2: Nearest Value 2^6 =64 - 2 = 62

Step 3: 11111111.11111111.11111111.11000000

Step 4: Network - 11 Hosts - 000000

Step 5: 255.255.255.192 /26

Writing range of 60 2^h -64 -2 = 62

192.168.10.0 - 192.168.10.63
192.168.10.64 - 192.168.10.127
192.168.10.128 - 192.168.10.191
192.168.10.192 - 192.168.10.255
Step 1 : Requirement 1000 Hosts

Step 2 : Nearest Value 2^10 = 1024 - 2 = 1022

Step 3 : 11111111.11111111.11111100.00000000

Step 4 : Network - 111111 Hosts - 00 . 00000000

Step 5 : 255.255.252.0 /22

Writing Range of 1024 2^h - 1024 -2 = 1022

162.56.0.0 - 162.56.4.2
162.56.4.3 - 162.56.8.4
162.56.8.5 - 162.56.12.4

172.18.20.48 /28

11111111.11111111.11111111.11110000 Class - B

2^4 = 16

10.0.0.0 /24

10.0.0.0 - 10.0.0.63
10.0.0.64 - 10.0.0.127
10.0.0.128 - 10.0.0.191
10.0.0.192 - 10.0.0.255

Classless Inter Domain ID

Host -- > 65,000

172.18.0.0 /16 ---- > 172.31.0.0 /16

64

255.255.248.0

172.18.8.0
172.18.16.0
172.18.24.0
172.18.32.0
172.18.40.0
ssh -i <keyfile> ec2-user@<private ip>

NAT GATEWAY - FIREWALL

Only Allows Authorized Connections

INTERAN ------ FIREWALL -------- INTERNET

REQUEST GOOGLE ------- GOOGLE.COM

------------ REPLY

create bastion host and ssh to pri-ec2

create NAT Gateway
de-associate private subnet from rt
create new rt dor private subnet
associate private sunet to new rt
add route for NAT Gateway in new rt

AWS EC2- Aws Compute

AWS VPC - Network and Content delivery

DATA IN PROCESS - PROCESS

DATA IN REST - STORAGE
DATA IN TRANSIT -

AWS SECURITY

CSP IS RESPONSIBLE FOR SECURITY OF THE CLOUD

EU IS RESPONSIBLE FOR SECURITY IN THE CLOUD ---> (END USER)

AWS SHARED RESPONSIBILITY MODEL

IAM ----> IDENTITY AND ACCESS MANAGEMENT

AWS Elastic Beanstalk - PaaS

PaaS - Managed Services

1 Server - Ec2

Load Balancing

Auto Scaling
Managed Services -----------> AWS BeanStalk

Module NO- 6 Aws Activity AWS BeanStalk

#!/bin/bash ----> ?? She Bang :)

sudo apt-get update -y ( yum update -y )
sudo apt-get install apache2 -y ( yum install httpd -y )
sudo systemctl start apache2

#!/bin/bash
sudo apt-get update -y
sudo apt-get install apache2 -y
sudo systemctl start apache2

Test Topics

Aws Rds

Iam Role

Aws Lambda

Aws Event Bridge

Aws Elastic Block Storage

Ec2

Vpc

Subnetting

Aws Elastic beanstalk

ssh-keygen -t rsa -b 2048 -C "[email protected]"

/usr/local/apache2/htdocs/