Cloud Computing

Cloud Characteristics (NIST)

 Broad Network Access (Internet)
 Resource Pooling
 On-Demand Access
 Elasticity (Scalable)
 Must be measured

Cloud Types
 Private
 Public
 Hybrid

Cloud Models
 SaaS: End user (Google Email)
 PaaS: Developer
 IaaS:

Cloud Providers
 Amazon: Amazon Web Services (AWS)
 Rackspace
 Microsoft Azure
 Google Compute Engine

AWS
 Amazon Web Service
 Cloud Provider
 Requirements
o Amazon account with Debit card or Credit card
o Use https://aws.amazon.com/ to open/configure account
 Terminologies
o AWS Console
 Dashboard using which new infrastructure can be configured
o AWS Region
 Collection of availability zones
o Availability zone
 Server farm which holds the infrastructure
 Services
o Compute
 Provides a virtual machine
 vCPU
 RAM
 Storage
 Operating System
 EC2
 Elastic Compute Cloud
 Elastic Beanstalk
 Readymade EC2 instance with required platform installed
o Storage
 S3
 Simple Storage Service
 Used to provide a storage mechanism
 EFS
 Elastic File System
o EBS: Elastic Block Service
o Database
 RDS
 Relational Database Service
 With MySQL, Oracle, IBM DB2, PosGres and MS SQL-SERVER
 DynamoDB
 Amazon’s NoSQL DB
o Networking
 VPC
 Virtual Private Cloud
 A network which contains AWS resources connected together
 Owned by a single owner
 Route 53
 Used for configuring DNS records and Domain Registrations

EC2 instance
 Create an instance with
o Type: t2.micro
o vCPU: 1
o RAM: 1 GiB
o OS: Red Hat 7.4
 To protect the pem file
chmod 400 <pem file path>

 To connect to the EC2 instance

ssh –i <pem file path> <user>@<public ip address>

 To upload the file(s) to EC2 instance

scp –i <pem file path> <source file path> <user>@<public ip

address>:<destination path>
Auto Scaling
 Process of scaling in and scaling out the resources (ec2 instance)
 Requirements
o Launch Configuration
 Configuration of an instance which will be cloned automatically
 Configuration of
 Instance type: t2.micro
 AMI: Amazon Machine Image
o Auto-scaling Group
 Launch configuration
 Scaling policies
 Min count:
 Max count:
 Watch condition
o Increment
 CPU % > 30
 Add 1 instance per 300 seconds
o Decrement
 CPU % < 20
 Remove 1 instance per 300 seconds