─────────────────────────

───────────────────
CLOUD COMPUTING – UNIT 1

────────────────────────────────────────────

UNIT – 1 : INTRODUCTION TO CLOUD COMPUTING

(Definition, Need, Characteristics, Evolution, Architecture, Services, Parallel vs Distributed,
Elasticity, On-Demand Provisioning)

────────────────────────────────────────────
1. DEFINITION OF CLOUD COMPUTING
────────────────────────────────────────────
Cloud Computing is the **delivery of computing services** such as servers, storage, databases,
networking, software, analytics, and intelligence **over the internet (“the cloud”)**.

Instead of owning hardware, users **rent** these resources and **pay only for what they use**.

Key Points:
• Internet-based computing
• On-demand availability
• Scalable and flexible
• Pay-as-you-go model
• No physical infrastructure required on client site

────────────────────────────────────────────
2. NEED OF CLOUD COMPUTING
────────────────────────────────────────────
Before cloud:
• Companies bought servers, storage, networking devices
• Required physical space, cooling, power
• Required expert staff to maintain systems
• Scaling up was slow and expensive
• Infrastructure was often underutilized

Cloud solves these problems.

**Benefits / Need:**
1. Cost Efficiency
– No need to buy costly hardware
– Pay only for used resources

2. Scalability
– Resources can scale up/down instantly

3. Accessibility
– Access from anywhere using internet

4. Disaster Recovery
– Cloud providers maintain backup and DR systems

5. Security
– Strong encryption, identity management, compliance

────────────────────────────────────────────
3. CHARACTERISTICS OF CLOUD COMPUTING
────────────────────────────────────────────
1. On-Demand Self-Service
– Resources can be provisioned without human intervention.

2. Broad Network Access

– Accessible via laptop, mobile, tablet etc.

3. Resource Pooling
– Shared infrastructure using multi-tenancy model.

4. Rapid Elasticity
– Fast scaling up/down based on demand.

5. Measured Service
– Pay-per-use, metered billing.

6. Automation
– Automatic provisioning, scaling, management.

7. Multi-Tenancy
– Multiple users share hardware securely.

8. Security
 – Encryption, IAM, compliance standards.

────────────────────────────────────────────
4. DISADVANTAGES OF CLOUD COMPUTING
────────────────────────────────────────────
1. Downtime
2. Security & Privacy Risks
3. Limited Control
4. Vendor Lock-In

────────────────────────────────────────────
5. CLOUD SERVICE PROVIDERS
────────────────────────────────────────────
Major providers:
• AWS (Amazon Web Services)
• Microsoft Azure
• Google Cloud Platform (GCP)
• IBM Cloud
• Alibaba Cloud

Major services:
– Compute (EC2, Azure VM, GCE)
– Storage (S3, Azure Blob, GCS)
– Databases (RDS, Cloud SQL, Azure SQL)
– Machine Learning (SageMaker, Azure ML, TensorFlow)

────────────────────────────────────────────
6. EVOLUTION OF CLOUD COMPUTING
────────────────────────────────────────────
Cloud computing evolved through these stages:

1. Distributed Systems
2. Mainframe Computing (1950s)
3. Cluster Computing (1980s)
4. Grid Computing (1990s)
5. Virtualization (1970s, became mainstream in 2000s)
6. Web 2.0 (2004 – interactive web apps)
7. Service Orientation (SOA)
8. Utility Computing (Pay-per-use)
9. Cloud Computing

Each step added:

• Better resource sharing
• Better scalability
• Better accessibility

────────────────────────────────────────────
7. ARCHITECTURE OF CLOUD COMPUTING
────────────────────────────────────────────
The architecture includes **Frontend + Backend** connected via Internet.

A. Frontend
• Client Infrastructure
• Browsers, Mobile Apps
• User Interfaces

B. Backend
• Applications (Cloud-side)
• Services (IaaS, PaaS, SaaS)
• Runtime Cloud
• Storage
• Virtualization
• Physical Infrastructure
• Management Layer

Working:
User sends request → Internet → Backend processes → Response returned.

────────────────────────────────────────────
8. CLOUD SERVICES (IaaS, PaaS, SaaS)
────────────────────────────────────────────
1. IaaS – Infrastructure as a Service
– Provides virtual machines, servers, networks
– Example: AWS EC2, Azure VM, Google Compute Engine

2. PaaS – Platform as a Service

– Provides platform for developers to build & deploy apps
– Example: Google App Engine, Azure App Service, AWS Elastic Beanstalk

3. SaaS – Software as a Service

– Ready-to-use cloud applications
– Example: Gmail, Salesforce, Google Workspace

────────────────────────────────────────────
9. APPLICATIONS OF CLOUD COMPUTING
────────────────────────────────────────────
• Data storage & backup
• SaaS applications
• PaaS / App Development
• Big Data Analytics
• Disaster Recovery
• Virtual Desktops
• IoT backend
• Media streaming

────────────────────────────────────────────
10. PARALLEL COMPUTING
────────────────────────────────────────────
Definition:
Large problems are divided into small tasks executed **simultaneously** using multiple
processors.

Architecture:
• Shared Memory
• Distributed Memory
• Hybrid Memory

Benefits:
• Faster execution
• Handles complex tasks
• High efficiency

Challenges:
• Complex programming
• Synchronization issues

────────────────────────────────────────────
11. DISTRIBUTED COMPUTING
────────────────────────────────────────────
Definition:
A system with multiple computers working together as one system, located at different places.

Advantages:
• Fault tolerance
• Low cost
• Scalable
• Location flexibility

Disadvantages:
• Management complexity
• Network delays
• Security risks

────────────────────────────────────────────
12. PARALLEL vs DISTRIBUTED COMPUTING
────────────────────────────────────────────
Parallel:
• Many processors in one system
• Shared memory
• High speed

Distributed:
• Many systems across locations
• Network communication
• High scalability

────────────────────────────────────────────
13. ELASTICITY IN CLOUD
────────────────────────────────────────────
Elasticity = ability of cloud to **automatically scale** resources up/down based on demand.

Benefits:
• No over-provisioning
• No under-provisioning
• Cost efficient
• High availability

────────────────────────────────────────────
14. ON-DEMAND PROVISIONING
────────────────────────────────────────────
Definition:
Automatic allocation of servers, storage, VMs **exactly when required**.

Example:
During a flash sale, an e-commerce site automatically adds servers to handle high traffic.

Benefits:
• Faster deployment
• Efficient resource usage
• Supports sudden workload spikes

────────────────────────────────────────────
END OF UNIT-1 (FULL NOTES)
────────────────────────────────────────────

─────────────────────────
───────────────────
CLOUD COMPUTING
UNIT – 2 : VIRTUALIZATION
────────────────────────────────────────────

UNIT–2 CONTENTS
• Introduction to Virtualization
• Types of Virtualization
• Hypervisors (Type 1 & Type 2)
• Application Virtualization
• Server, Storage, Network Virtualization
• Benefits & Limitations
• Virtualization vs Cloud Computing

────────────────────────────────────────────
1. INTRODUCTION TO VIRTUALIZATION
────────────────────────────────────────────
Virtualization is a technology that allows creating **virtual versions** of hardware such as
servers, operating systems, storage, or networks.

It enables multiple virtual machines (VMs) to run on **one physical machine** using a
virtualization layer.

**Key Idea:**
Virtualization makes computing more efficient by allowing resource sharing, isolation, and
flexible management.

**Example:**
One physical server → multiple VMs (Windows VM, Linux VM, Database VM, etc.)

Importance in Cloud Computing:

• Foundation of IaaS (AWS EC2, Azure VM)
• Enables scalability, resource pooling, automation
• Reduces hardware costs
────────────────────────────────────────────
2. WHY VIRTUALIZATION IS NEEDED?
────────────────────────────────────────────
• Traditional systems underutilize hardware
• Scaling requires new physical machines
• High operational and maintenance cost
• Limited flexibility

**Virtualization solves these by:**

✓ Running multiple OS on one machine
✓ Reducing hardware cost
✓ Increasing efficiency & availability
✓ Supporting rapid scaling

────────────────────────────────────────────
3. TYPES OF VIRTUALIZATION
────────────────────────────────────────────

A) **Hardware / Server Virtualization**

• Creates multiple virtual servers on a single physical server
• Each VM works independently
• Hypervisor assigns CPU, RAM, Storage to VMs
• Used in cloud platforms (AWS EC2, Azure VM)

B) **Operating System Virtualization**

• A single OS kernel supports multiple isolated containers
• Lightweight and fast
• Examples: Docker, LXC, Kubernetes Pods

C) **Application Virtualization**
• Applications run independently of underlying OS
• Apps are streamed from a server
• Example: Microsoft App-V

D) **Storage Virtualization**
• Combines multiple physical storage devices into a single virtual storage pool
• Improves management and utilization
• Used in SAN and cloud storage systems

E) **Network Virtualization**
• Combines hardware + software network resources into a single virtual network
• Supports VLANs, SDN (Software Defined Networking)
F) **Desktop Virtualization**
• Full desktop OS is hosted on a server
• Users access desktops remotely
• Used in VDI (Virtual Desktop Infrastructure)

────────────────────────────────────────────
4. HYPERVISORS (VERY IMPORTANT)
────────────────────────────────────────────
A **Hypervisor** is virtualization software that manages and runs virtual machines.

There are **two types**:

──────────────────────────────
A) TYPE–1 HYPERVISOR
(“Bare Metal Hypervisor”)
──────────────────────────────
• Installed directly on hardware
• No host OS required
• High performance & secure
• Used in data centers & cloud

Examples:
• VMware ESXi
• Microsoft Hyper-V Server
• Xen
• KVM

Pros:
✓ Fast, efficient, secure
✓ Best for enterprises

Cons:
✗ Requires dedicated hardware

──────────────────────────────
B) TYPE–2 HYPERVISOR
(“Hosted Hypervisor”)
──────────────────────────────
• Installed on top of a host OS
• Easier for personal use
• Lower performance compared to Type-1
Examples:
• VMware Workstation
• Oracle VirtualBox
• Parallels

Pros:
✓ Easy to install
✓ Good for students/testing

Cons:
✗ Slower than Type-1

────────────────────────────────────────────
5. VIRTUALIZATION ARCHITECTURE
────────────────────────────────────────────
The architecture consists of:

• **Host Machine** – physical hardware

• **Host OS** – optional (only in Type-2)
• **Hypervisor** – virtualization layer
• **Guest OS / VMs** – virtual machines
• **Virtual Hardware** – virtual CPU, vRAM, vDisk, vNIC

Flow:
User request → Hypervisor → VM → Virtual Hardware → Physical Hardware

────────────────────────────────────────────
6. ADVANTAGES OF VIRTUALIZATION
────────────────────────────────────────────
✓ Better hardware utilization
✓ Lower hardware & maintenance cost
✓ Easy backup & recovery
✓ Enhanced security through isolation
✓ Scalability and flexibility
✓ Faster deployment of applications
✓ Supports cloud elasticity

────────────────────────────────────────────
7. DISADVANTAGES OF VIRTUALIZATION
────────────────────────────────────────────
✗ Performance overhead
✗ Requires skilled configuration
✗ If host machine fails → all VMs affected
✗ Licensing cost (VMware, Windows Server)

────────────────────────────────────────────
8. VIRTUALIZATION vs CLOUD COMPUTING
────────────────────────────────────────────

| Virtualization | Cloud Computing |

|----------------|-----------------|
| Technology to create VMs | Service delivered over Internet |
| Runs on local hardware | Runs on cloud provider hardware |
| Provides infrastructure | Provides IaaS, PaaS, SaaS |
| Basis for cloud | Uses virtualization |

**Conclusion:**
Virtualization is the **building block**, cloud computing is the **service model** built on top of it.

────────────────────────────────────────────
9. REAL-WORLD APPLICATIONS
────────────────────────────────────────────
• AWS EC2, Azure VM, GCP Compute Engine
• Data Center Management
• VDI (Virtual Desktop Infrastructure)
• Container Orchestration (Docker, Kubernetes)
• Testing environments
• Server consolidation

────────────────────────────────────────────
END OF UNIT-2
─────────────────────────

───────────────────
────────────────────────────────────────────

CLOUD COMPUTING
UNIT – 3 : CLOUD SERVICE MODELS
────────────────────────────────────────────

UNIT–3 CONTENTS
• Cloud Service Models (IaaS, PaaS, SaaS)
• Storage Services
• Compute Services
• Database Services
• Networking & Content Delivery
• Identity & Access
• Messaging Services
• Monitoring & Management
• Comparison of Services (Exam-important)

────────────────────────────────────────────
1. CLOUD SERVICE MODELS OVERVIEW
────────────────────────────────────────────
Cloud service models define *what level of service* the cloud provider delivers.

There are **three main service models**:

1. IaaS – Infrastructure as a Service
2. PaaS – Platform as a Service
3. SaaS – Software as a Service

These differ in how much control the user has over hardware, OS, runtime, and applications.

────────────────────────────────────────────
2. IaaS → INFRASTRUCTURE AS A SERVICE
────────────────────────────────────────────
**Definition:**
IaaS provides **virtualized hardware resources** over the internet such as:
• Virtual Machines (EC2 / Azure VM)
• Storage (S3 / Blob Storage)
• Networks (VPC / VNets)
• Load balancers

**You manage:**
• OS
• Applications
• Data

**Provider manages:**
• Hardware
• Virtualization
• Networking
• Storage infrastructure

**Examples:**
• AWS EC2
• Microsoft Azure Virtual Machines
• Google Compute Engine (GCE)

**Use Cases:**
• Hosting websites
• Running custom applications
• Backup & disaster recovery
• Scalable computing environments

**Benefits:**
✓ High control
✓ Pay-as-you-go
✓ Scalable infrastructure

────────────────────────────────────────────
3. PaaS → PLATFORM AS A SERVICE
────────────────────────────────────────────
**Definition:**
PaaS provides a **development & deployment platform** for developers.

Includes:
• Operating System
• Runtime Environment
• Databases
• Middleware
• Dev tools

**You manage:**
• Only applications & data

**Provider manages:**
• VM, OS, runtime, middleware, scaling
**Examples:**
• Google App Engine
• AWS Elastic Beanstalk
• Microsoft Azure App Service

**Use Cases:**
• Web app development
• API building
• Automated deployment

**Benefits:**
✓ No server management
✓ Faster development
✓ Auto-scaling built-in

────────────────────────────────────────────
4. SaaS → SOFTWARE AS A SERVICE
────────────────────────────────────────────
**Definition:**
SaaS delivers **ready-to-use applications** over the internet.

No installation required; accessed via browser/mobile app.

**Examples:**
• Gmail
• Google Docs
• Salesforce
• Microsoft Office 365

**You manage:** *Nothing*

**Provider manages:** Everything

**Benefits:**
✓ No installation
✓ Accessible anywhere
✓ Automatic updates

────────────────────────────────────────────
5. COMPARISON: IaaS vs PaaS vs SaaS
────────────────────────────────────────────

| Feature | IaaS | PaaS | SaaS |

|--------|------|------|-------|
| Control | High | Medium | Low |
| User Manages | OS, Apps | Apps | Nothing |
| Suitable For | SysAdmins | Developers | End Users |
| Examples | EC2 | App Engine | Gmail |

────────────────────────────────────────────
6. CLOUD STORAGE SERVICES
────────────────────────────────────────────
Cloud Storage provides scalable storage services with replication and backup.

Examples:
• AWS S3 (Simple Storage Service)
• Azure Blob Storage
• Google Cloud Storage

Features:
• Object-based storage
• Versioning
• Replication across regions
• Lifecycle management
• High durability (99.999999999%)

Use Cases:
• Backups
• File hosting
• Big data storage
• Media storage

────────────────────────────────────────────
7. CLOUD COMPUTE SERVICES
────────────────────────────────────────────
Compute services provide virtual CPU & memory to run applications.

Examples:
• AWS EC2
• Google Compute Engine
• Azure Virtual Machines

Features:
• Auto-scaling
• Load balancing
• Multiple OS support
• On-demand and reserved VMs

Use Cases:
• Websites
• ML training
• Batch processing

────────────────────────────────────────────
8. CLOUD DATABASE SERVICES
────────────────────────────────────────────
Types:
A) Relational Database (SQL)
Examples:
• AWS RDS
• Azure SQL Database
• Google Cloud SQL

B) NoSQL Database
Examples:
• AWS DynamoDB
• Google Firestore
• Azure Cosmos DB

Features:
• Automatic patching
• Replication
• Backups
• High availability

────────────────────────────────────────────
9. NETWORK & CONTENT DELIVERY
────────────────────────────────────────────
A) Virtual Networks
• AWS VPC
• Azure Virtual Network
• GCP VPC

B) Load Balancers
• AWS ELB
• Azure Load Balancer

C) CDN (Content Delivery Network)

• AWS CloudFront
• Azure CDN
• Google Cloud CDN

Function:
Delivers content faster by caching it near the user.

────────────────────────────────────────────
10. IDENTITY & ACCESS MANAGEMENT (IAM)
────────────────────────────────────────────
IAM controls **who can access what** in the cloud.

Features:
• Users & groups
• Access policies
• MFA (Multi-factor authentication)
• Role-based access

Examples:
• AWS IAM
• Azure Active Directory
• Google Cloud IAM

────────────────────────────────────────────
11. MESSAGING & QUEUE SERVICES
────────────────────────────────────────────
Used for **decoupling applications** and handling asynchronous communication.

Examples:
• AWS SQS (Queue)
• AWS SNS (Notification)
• Azure Service Bus
• Google Pub/Sub

Use Cases:
• Microservices
• Event-driven apps
• Distributed systems

────────────────────────────────────────────
12. MONITORING & MANAGEMENT
────────────────────────────────────────────
Examples:
• AWS CloudWatch
• Azure Monitor
• Google Operations Suite

Functions:
• Track performance
• Log monitoring
• Alerting
• Autoscaling triggers

────────────────────────────────────────────
13. BENEFITS OF CLOUD SERVICES
────────────────────────────────────────────
✓ Reduced cost
✓ No hardware required
✓ Faster development cycles
✓ Scalability
✓ High availability
✓ Global reach

────────────────────────────────────────────
14. LIMITATIONS OF CLOUD SERVICES
────────────────────────────────────────────
✗ Vendor lock-in
✗ Downtime risk
✗ Limited control
✗ Data security concerns

────────────────────────────────────────────
END OF UNIT–3
────────────────────────────────────────────
─────────────────────────
───────────────────
CLOUD COMPUTING
UNIT – 4 : CLOUD SECURITY
────────────────────────────────────────────

UNIT–4 CONTENTS
• Introduction to Cloud Security
• Security Challenges in Cloud
• Cloud Security Requirements
• Data Security in Cloud
• Identity & Access Management (IAM)
• Virtualization Security
• Security Threats in Cloud
• Best Practices for Cloud Security
• Compliance & Governance

────────────────────────────────────────────
1. INTRODUCTION TO CLOUD SECURITY
────────────────────────────────────────────
Cloud Security refers to the set of **policies, technologies, and controls** that protect:
• Data
• Applications
• Virtual machines
• Networks
• Cloud infrastructure

Cloud resources are accessed over the internet → risk increases → so strong security is
required.

Security is a **shared responsibility**:

• Cloud Provider → Secures infrastructure
• Customer → Secures data, users, configurations

────────────────────────────────────────────
2. SECURITY CHALLENGES IN CLOUD
────────────────────────────────────────────
1. **Data Breaches**
Unauthorized access to sensitive cloud data.

2. **Data Loss**
Caused by deletion, corruption, malware, system failures.

3. **Account Hijacking**
Weak passwords or phishing → attackers take control of accounts.

4. **Insecure APIs**
Poorly designed APIs can leak data or allow unauthorized access.

5. **Denial of Service (DoS) Attacks**

Attackers flood cloud servers → service becomes unavailable.

6. **Malicious Insiders**
Employees or admins misuse access rights.

7. **Misconfiguration**
The most common cloud security incident (e.g., public S3 buckets).

────────────────────────────────────────────
3. CLOUD SECURITY REQUIREMENTS
────────────────────────────────────────────
To secure cloud environments, the following are required:

1. **Confidentiality**
Data should be accessible only to authorized users.
→ Encryption (at rest + in transit)

2. **Integrity**
Data must not be altered or tampered.
→ Hashing, digital signatures

3. **Availability**
Services should be up 24×7.
→ Load balancing, redundancy, backups

4. **Authentication**
User identity validation.
→ Passwords, MFA

5. **Authorization**
 Permission control for user access.
→ IAM roles & policies

6. **Non-repudiation**
Evidence of user actions.
→ Logs, digital signatures

────────────────────────────────────────────
4. DATA SECURITY IN CLOUD
────────────────────────────────────────────
Data in cloud exists in three forms:

1. **Data at Rest**
Data stored in disk, databases, storage services.
→ Encrypt using AES-256
→ Key Management (KMS)

2. **Data in Transit**
Data moving across networks.
→ Protect with TLS/SSL encryption

3. **Data in Use**
Data being processed.
→ Isolation → Tokenization → Secure enclaves

**Techniques used:**
• Encryption
• Tokenization
• Data masking
• Identity-based access
• Backup & Disaster recovery

────────────────────────────────────────────
5. IDENTITY & ACCESS MANAGEMENT (IAM)
────────────────────────────────────────────
IAM manages **who can access what** in the cloud.

Key Components:
• Users
• Groups
• Roles
• Permissions
• Policies
Functions:
1. Authentication → proves identity (password, MFA)
2. Authorization → assigns permissions
3. Access control → grants/restricts resources
4. Auditing → logs all user activity

Examples:
• AWS IAM
• Azure AD
• Google Cloud IAM

Best Practices:
• Use MFA
• Implement least privilege
• Rotate access keys
• Use strong policies

────────────────────────────────────────────
6. VIRTUALIZATION SECURITY
────────────────────────────────────────────
Since cloud runs on virtualized environments, securing virtualization is essential.

Major risks:
• VM Escape
• Hypervisor attacks
• VM sprawl
• Insecure VM images

Security Measures:
1. Secure Hypervisor
– Keep Type-1 hypervisors updated
– Harden configurations

2. Isolation
– VMs must be isolated using virtualization boundaries

3. Image Security
– Use trusted VM images
– Scan for malware

4. Network Security
– Firewalls, VLANs, security groups
5. Monitoring
– Track VM creation, deletion, resource usage

────────────────────────────────────────────
7. CLOUD SECURITY THREATS
────────────────────────────────────────────
1. **SQL Injection**
2. **Cross-Site Scripting (XSS)**
3. **Man-in-the-Middle (MITM)**
4. **Brute Force Attacks**
5. **Malware & Ransomware**
6. **Misconfigured Storage Buckets**
7. **Zero-Day Vulnerabilities**

────────────────────────────────────────────
8. CLOUD SECURITY BEST PRACTICES
────────────────────────────────────────────
1. Encrypt everything (data at rest + in transit)
2. Enable MFA for all users
3. Use IAM roles, not root accounts
4. Regular audits and log monitoring
5. Patch systems regularly
6. Network segmentation using VPC, firewalls
7. Backup data across regions
8. Use WAF (Web Application Firewall) & IDS/IPS

────────────────────────────────────────────
9. COMPLIANCE & GOVERNANCE IN CLOUD
────────────────────────────────────────────
Compliance ensures cloud usage follows laws:
• GDPR (EU data protection)
• HIPAA (healthcare)
• ISO 27001
• PCI-DSS (payment security)
• SOC 2

Governance includes:
• Policies
• Procedures
• Risk management
• Access control
• Monitoring
────────────────────────────────────────────
10. SHARED RESPONSIBILITY MODEL
────────────────────────────────────────────
Very important question.

**Cloud Provider (AWS, Azure, GCP) Responsible For:**

• Physical security
• Network infrastructure
• Hypervisor security
• Hardware & data center

**Customer Responsible For:**

• Data security
• IAM configuration
• Application-level security
• OS patches
• Firewall rules

────────────────────────────────────────────
END OF UNIT–4 (Cloud Security)
──────────────────────────────────────────

──
────────────────────────────────────────────

CLOUD COMPUTING
UNIT – 5 : CLOUD DEPLOYMENT MODELS,
ARCHITECTURE, SLA, BILLING, LOAD BALANCING
────────────────────────────────────────────

UNIT–5 CONTENTS
• Cloud Deployment Models
• Public, Private, Hybrid, Community Cloud
• Cloud Computing Reference Architecture
• Service Level Agreements (SLA)
• Cloud Billing Models
• Load Balancing
• Auto Scaling
• Cloud Migration
• Interoperability & Portability
• Benefits & Challenges

────────────────────────────────────────────
1. CLOUD DEPLOYMENT MODELS
────────────────────────────────────────────
Cloud deployment models define **how** and **where** cloud resources are hosted.

There are four major deployment models:

──────────────────────────────
A) PUBLIC CLOUD
──────────────────────────────
• Cloud services offered over the public internet
• Shared infrastructure
• Owned by 3rd-party providers (AWS, Azure, GCP)

Features:
✓ Pay-per-use
✓ Highly scalable
✓ No infrastructure maintenance

Used by:
• Startups
• Web applications
• SaaS companies

Limitations:
✗ Data security concerns
✗ Less control

──────────────────────────────
B) PRIVATE CLOUD
──────────────────────────────
• Cloud infrastructure dedicated to a single organization
• Managed internally or by third-party
• Hosted on-premises or externally

Features:
✓ High security & privacy
✓ Full control
✓ Suitable for govt/banking/healthcare

Limitations:
✗ Expensive
✗ Requires skilled staff

──────────────────────────────
C) HYBRID CLOUD
──────────────────────────────
• Combination of Public + Private cloud
• Workloads can move between both

Use Case:
• Sensitive data → private cloud
• Normal workloads → public cloud

Features:
✓ Flexibility
✓ Better cost optimization

Limitations:
✗ Complex to manage

──────────────────────────────
D) COMMUNITY CLOUD
──────────────────────────────
• Shared by organizations with similar requirements
• Example: universities, banks, research labs

Features:
✓ Cost shared among members
✓ Secure and collaborative

────────────────────────────────────────────
2. CLOUD COMPUTING REFERENCE ARCHITECTURE
────────────────────────────────────────────
Cloud architecture consists of:

A) **Clients / Consumers**
• Access cloud services via browser, mobile, thin clients

B) **Cloud Services Layers**

1. SaaS Layer → applications
2. PaaS Layer → development platform
3. IaaS Layer → hardware resources

C) **Management Layer**
• Resource provisioning
• Metering & billing
• Monitoring
• Security & identity

D) **Security Layer**
• IAM
• Encryption
• Compliance

E) **Physical Infrastructure**
• Servers
• Storage
• Network
• Hypervisors

Workflow:
User request → Frontend → Middleware → Backend services → Response returned

────────────────────────────────────────────
3. SERVICE LEVEL AGREEMENTS (SLA)
────────────────────────────────────────────
SLA = **official contract** between cloud provider & customer defining:

1. Performance
2. Availability (usually 99.9% or 99.99%)
3. Security responsibilities
4. Response time
5. Penalties for downtime

Key SLA Metrics:

• Uptime
• Latency
• Throughput
• Disaster Recovery Time (RTO, RPO)

Importance:
✓ Ensures transparency
✓ Protects customer rights
✓ Defines shared responsibility

────────────────────────────────────────────
4. CLOUD BILLING MODELS
────────────────────────────────────────────
Billing depends on resource consumption.

Common models:

──────────────────────────────
A) PAY-AS-YOU-GO (On-demand)
──────────────────────────────
• Pay only for what you use
• No upfront cost

Best for:
• Unpredictable workloads

──────────────────────────────
B) RESERVED INSTANCES
──────────────────────────────
• Commit to 1 or 3 years usage
• Lower cost compared to on-demand

Best for:
• Stable, long-term workloads
──────────────────────────────
C) SPOT INSTANCES
──────────────────────────────
• Use unused cloud capacity at low price
• Can be terminated anytime

Used for:
• Batch jobs
• ML training

──────────────────────────────
D) SUBSCRIPTION / MONTHLY BILLING
──────────────────────────────
• Fixed monthly fee
• Used for SaaS products

────────────────────────────────────────────
5. LOAD BALANCING IN CLOUD
────────────────────────────────────────────
Load balancing distributes incoming network traffic across multiple servers.

Benefits:
✓ High availability
✓ Prevents overload
✓ Better application performance
✓ Redundancy

Types:
• Software load balancer
• Hardware load balancer
• Global load balancing (multi-region)

Examples:
• AWS ELB
• Azure Load Balancer
• Google Cloud Load Balancing

Techniques:
• Round Robin
• Least Connections
• IP Hash
────────────────────────────────────────────
6. AUTO SCALING
────────────────────────────────────────────
Auto-scaling allows cloud systems to **automatically add or remove** virtual machines based
on demand.

Example:
If traffic increases → new VMs automatically added
If traffic decreases → VMs removed to save cost

Advantages:
✓ Cost efficiency
✓ Handles peak loads
✓ Zero manual intervention
✓ Ensures performance

Examples:
• AWS Auto Scaling Groups
• Azure Scale Sets
• Google Instance Groups

────────────────────────────────────────────
7. CLOUD MIGRATION
────────────────────────────────────────────
Cloud migration = moving applications, data, and workloads from:

• On-premise → Cloud
• One cloud → Another cloud
• Legacy system → Cloud-native environment

Migration Strategies (6R Model):

1. Rehost (“Lift & Shift”)
2. Replatform
3. Refactor / Re-architect
4. Repurchase (SaaS)
5. Retire
6. Retain

Challenges:
✗ Data transfer cost
✗ Compatibility issues
✗ Downtime
✗ Security risks
────────────────────────────────────────────
8. CLOUD INTEROPERABILITY & PORTABILITY
────────────────────────────────────────────
Interoperability:
• Ability of cloud systems to communicate & exchange data
• Example: Azure app accessing AWS database

Portability:
• Ability to move apps/data between clouds without major changes
• Example: Migrating app from AWS → GCP

Standards that help:

• Kubernetes
• Docker containers
• OpenStack

────────────────────────────────────────────
9. BENEFITS OF CLOUD DEPLOYMENT MODELS
────────────────────────────────────────────
✓ Better resource utilization
✓ Reduced hardware cost
✓ Scalability
✓ Global reach
✓ Disaster recovery
✓ Automated operations

────────────────────────────────────────────
10. CHALLENGES OF CLOUD DEPLOYMENT
────────────────────────────────────────────
✗ Security risks
✗ Vendor lock-in
✗ Downtime
✗ Performance issues
✗ Compliance requirements

────────────────────────────────────────────
END OF UNIT–5
────────────────────────────────────────────