THEORY FILE : Cloud Computing .

(FULL NOTES: BY SAHIL RAUNIYAR / PTU-CODER) .

SUBJECT CODE: UGCA: 1936

BACHELOR OF COMPUTER APPLICATIONS

IL
MAINTAINED BY: TEACHER’S /MAM’:
Sahil Kumar Prof.

COLLEGE ROLL NO: 226617

UNIVERSITY ROLL NO: 2200315

H
SA

DEPARTMENT OF COMPUTER SCIENCE ENGINEERING

BABA BANDA SINGH BAHADUR ENGINEERING

COLLEGE FATEGARH SAHIB

 1

Program BCA ➖➖
Course Name ➖
Semester 5th.
Cloud Computing (Theory).

UNIT ➖01
● Overview of Computing Paradigm: Recent trends in Computing -Grid Computing,

➖
Cluster Computing, Distributed Computing, Utility Computing, Cloud
Computing

IL
# Overview of Computing Paradigm ➖
The computing paradigm has evolved significantly over the years, adapting to the increasing
demands for computational power, data storage, and accessibility. Below is an overview of
recent trends in computing, including Grid Computing, Cluster Computing, Distributed
Computing, Utility Computing, and Cloud Computing.

# Grid Computing ➖
H
Grid computing involves connecting multiple computer systems across different locations to
form a large-scale virtual supercomputer. This paradigm leverages idle computational
resources to solve complex scientific, mathematical, or technical problems.

I. Characteristics:
A. Resource Sharing: Utilises idle resources from multiple systems.
SA
B. Geographically Distributed: Systems can be spread across different locations.
C. Scalability: Easily scales by adding more resources.
D. Heterogeneity: Supports different types of systems and architectures.
II. Applications:
A. Scientific research
B. Engineering simulations
C. Data analysis in various fields like bioinformatics and climate modelling

# Cluster Computing ➖
Cluster computing involves connecting multiple computers (nodes) to work together as a single
system. These nodes are typically located in the same physical location and connected via a
high-speed local area network (LAN).

I. Characteristics:
A. Tight Coupling: Nodes work closely together, often with shared storage.
B. High Availability: Provides redundancy and failover capabilities.
C. High Performance: Suitable for tasks requiring significant computational power.
D. Load Balancing: Distributes workload evenly across nodes.
 2
II. Applications:
A. High-performance computing (HPC)
B. Database management
C. Financial modeling
D. Weather forecasting

# Distributed Computing ➖
Distributed computing involves multiple autonomous computers communicating and
coordinating to achieve a common goal. Unlike grid computing, which focuses on resource
sharing, distributed computing emphasizes the division of tasks.

I. Characteristics:

IL
A. Autonomy: Each node operates independently and can be geographically
dispersed.
B. Concurrency: Multiple processes run simultaneously.
C. Fault Tolerance: Designed to handle failures in individual nodes without affecting
the overall system.
D. Scalability: Easily scales with the addition of more nodes.
II. Applications:
A. Web services
H
B. E-commerce platforms
C. Social networks
D. Content delivery networks (CDNs)

# Utility Computing ➖
Utility computing is a service provisioning model where computing resources are provided and
SA
billed on a pay-as-you-go basis, similar to utilities like electricity and water.

I. Characteristics:
A. On-Demand: Resources are provisioned and billed based on usage.
B. Scalability: Easily adjusts resources based on demand.
C. Cost-Efficiency: Reduces capital expenditure by charging only for what is used.
D. Flexibility: Users can quickly scale up or down as needed.
II. Applications:
A. Software as a Service (SaaS)
B. Infrastructure as a Service (IaaS)
C. Platform as a Service (PaaS)

# Cloud Computing ➖
Cloud computing delivers computing services (servers, storage, databases, networking,
software, analytics, and intelligence) over the internet ("the cloud") to offer faster innovation,
flexible resources, and economies of scale.
 3
I. Characteristics:
A. Resource Pooling: Multiple clients share a pool of resources.
B. Broad Network Access: Accessible from anywhere with internet connectivity.
C. Rapid Elasticity: Quickly scale resources up or down.
D. Measured Service: Pay only for the resources you use.
II. Service Models:
A. Infrastructure as a Service (IaaS): Provides virtualized computing resources
over the internet.
1. Examples: Amazon EC2, Google Compute Engine
B. Platform as a Service (PaaS): Provides a platform allowing customers to
develop, run, and manage applications without dealing with the underlying
infrastructure.

IL
1. Examples: Google App Engine, Microsoft Azure
C. Software as a Service (SaaS): Delivers software applications over the internet,
on a subscription basis.
1. Examples: Google Workspace, Microsoft Office 365
III. Deployment Models:
A. Public Cloud: Services are delivered over the public internet and shared across
organizations.
B. Private Cloud: Services are maintained on a private network and used

IV.
H
exclusively by one organization.
C. Hybrid Cloud: Combines public and private clouds, allowing data and
applications to be shared between them.
Applications:
A. Data storage and backup
B. Disaster recovery
C. Virtual desktops
SA
D. Big data analytics
E. DevOps and continuous integration/continuous deployment (CI/CD)

Summary ➖
Recent trends in computing have shifted towards distributed and scalable systems, leveraging
the collective power of multiple resources to provide high performance, reliability, and
cost-efficiency. These paradigms, including Grid Computing, Cluster Computing, Distributed
Computing, Utility Computing, and Cloud Computing, have enabled advancements in scientific
research, enterprise applications, and consumer services, meeting the growing demand for
computational resources and flexibility.
 4
● Introduction to Cloud Computing: Vision of Cloud Computing, Defining a Cloud,
Cloud delivery Model, Deployment Model, Characteristics, Benefits of Cloud

➖
Computing, Challenges ahead. Cloud computing vs. Cluster computing vs. Grid
computing

Introduction to Cloud Computing ➖

# Vision of Cloud Computing ➖
Cloud computing envisions a world where computing resources are as readily accessible as
utilities like water and electricity. This paradigm shift allows organizations and individuals to
access and utilise vast amounts of computing power and storage on-demand, scaling up or

IL
down as needed, and paying only for what they use.

# Defining a Cloud ➖
Cloud computing is a model for enabling ubiquitous, convenient, on-demand network access
to a shared pool of configurable computing resources (e.g., networks, servers, storage,
applications, and services) that can be rapidly provisioned and released with minimal
management effort or service provider interaction.

➖
H
# Cloud Delivery Models

1. Infrastructure as a Service (IaaS):

○ Provides virtualized computing resources over the internet.
○ Users can rent virtual machines, storage, and networks.
○ Examples: Amazon EC2, Google Compute Engine, Microsoft Azure.
2. Platform as a Service (PaaS):
SA
○ Provides a platform allowing customers to develop, run, and manage applications
without dealing with the underlying infrastructure.
○ Examples: Google App Engine, Microsoft Azure App Services, Heroku.
3. Software as a Service (SaaS):
○ Delivers software applications over the internet, on a subscription basis.
○ Users access software through a web browser.
○ Examples: Google Workspace, Microsoft Office 365, Salesforce.

# Deployment Models ➖
1. Public Cloud:
○ Services are delivered over the public internet and shared across organizations.
○ Examples: Amazon Web Services (AWS), Google Cloud Platform (GCP),
Microsoft Azure.
2. Private Cloud:
○ Services are maintained on a private network and used exclusively by one
organization.
○ Provides greater control and security.
 5
3. Hybrid Cloud:
○ Combines public and private clouds, allowing data and applications to be shared
between them.
○ Provides flexibility and optimized workload distribution.
4. Community Cloud:
○ Shared infrastructure for a specific community of users from organizations with
common concerns.
○ Examples: Collaborative projects between universities or government agencies.

Characteristics of Cloud Computing ➖

1. On-Demand Self-Service:
○ Users can provision computing capabilities as needed automatically, without

IL
human intervention from the service provider.
2. Broad Network Access:
○ Capabilities are available over the network and accessed through standard
mechanisms that promote use by heterogeneous thin or thick client platforms.
3. Resource Pooling:
○ The provider’s computing resources are pooled to serve multiple consumers using
a multi-tenant model, with different physical and virtual resources dynamically
assigned and reassigned according to consumer demand.
H
4. Rapid Elasticity:
○ Capabilities can be elastically provisioned and released, in some cases
automatically, to scale rapidly outward and inward commensurate with demand.
5. Measured Service:
○ Cloud systems automatically control and optimize resource use by leveraging a
metering capability at some level of abstraction appropriate to the type of service.

➖
SA
Benefits of Cloud Computing

1. Cost Efficiency:
○ Reduces the capital expenditure on hardware and software.
○ Pay-as-you-go model eliminates the need for upfront investments.
2. Scalability and Flexibility:
○ Quickly scale resources up or down to handle varying workloads.
○ Accommodates growth and changing needs without significant infrastructure
investments.
3. Accessibility:
○ Access services and data from anywhere with an internet connection.
○ Supports remote work and collaboration.
4. Disaster Recovery and Business Continuity:
○ Provides backup and recovery solutions.
○ Ensures data is safe and accessible even in case of disasters.
5. Automatic Updates:
○ Service providers handle maintenance and updates.
 6
○ Users benefit from the latest features and security patches without managing
updates themselves.

# Challenges Ahead ➖
1. Security and Privacy:
○ Protecting sensitive data and ensuring privacy.
○ Addressing concerns about data breaches and unauthorized access.
2. Compliance:
○ Meeting regulatory and legal requirements for data protection and privacy.
○ Ensuring cloud providers comply with industry standards.
3. Latency and Performance:
○ Addressing issues related to data transfer speed and latency.

IL
○ Ensuring consistent performance for applications.
4. Data Management:
○ Handling data migration, storage, and backup effectively.
○ Managing large volumes of data efficiently.
5. Vendor Lock-In:
○ Avoiding dependency on a single cloud provider.
○ Ensuring interoperability and data portability.

➖
1. Cloud Computing:

I.
H
# Cloud Computing vs. Cluster Computing vs. Grid Computing

➖
Model: Service-based (IaaS, PaaS, SaaS)
II. Scalability: Elastic, on-demand scaling
III. Accessibility: Accessed via the internet
SA
IV. Usage: Broad use cases, including web services, applications, data storage
V. Management: Managed by third-party providers

2. Cluster Computing: ➖
I. Model: System-based (tightly coupled systems)
II. Scalability: Limited by physical hardware
III. Accessibility: Usually within a single location (LAN)
IV. Usage: High-performance computing (HPC), database management
V. Management: Managed locally, often by dedicated IT staff

3. Grid Computing: ➖
I. Model: Resource-sharing (loosely coupled systems)
II. Scalability: Aggregates resources from multiple locations
III. Accessibility: Distributed geographically, can be accessed remotely
IV. Usage: Scientific research, engineering simulations, large-scale computations
V. Management: Shared management across different organizations
 ➖
7
Summary

Cloud computing represents a transformative shift in how we access and utilize computing
resources, offering unprecedented flexibility, scalability, and cost-efficiency. As organizations
continue to adopt cloud services, they must navigate the challenges and leverage the benefits
to drive innovation and growth. Understanding the differences between cloud computing,
cluster computing, and grid computing helps in choosing the right approach for specific needs
and applications.

➖
● Migrating into a Cloud: Introduction, Broad approaches to Migrating into the
Cloud, The Seven-Step Model of Migration Into a Cloud

IL
# Migrating into a Cloud ➖
Introduction ➖
Migrating into a cloud involves moving an organisation's IT resources, applications, and data
from on-premises infrastructure to a cloud environment. This migration process offers
numerous benefits such as cost savings, scalability, and flexibility, but it also requires careful
H
planning and execution to ensure a smooth transition and to leverage the full advantages of
cloud computing.

Broad Approaches to Migrating into the Cloud ➖

There are several approaches to cloud migration, each with its own set of advantages and
considerations. Here are the broad approaches:
SA
1. Rehosting (Lift and Shift):
○ Definition: Moving applications and data to the cloud without making significant
changes.
○ Advantages: Quick and straightforward; minimal changes to existing applications.
○ Considerations: May not fully leverage cloud-native features; potential
inefficiencies if the application was not designed for the cloud.
2. Refactoring (Re-architecting):
○ Definition: Modifying applications to better exploit cloud capabilities.
○ Advantages: Optimizes performance, scalability, and cost-efficiency; makes full
use of cloud-native features.
○ Considerations: Requires significant time and effort; potential for higher initial
costs.
3. Replatforming (Lift, Tinker, and Shift):
○ Definition: Moving applications to the cloud with some optimizations for better
cloud utilization.
○ Advantages: Balances between rehosting and refactoring; some performance
and cost benefits.
 8
○ Considerations: Requires some changes to the application; more effort than
rehosting.
4. Repurchasing:
○ Definition: Replacing existing applications with cloud-based solutions, often
SaaS.
○ Advantages: Reduces management overhead; often comes with enhanced
features.
○ Considerations: Potential data migration challenges; possible disruption to
business processes.
5. Retiring:
○ Definition: Identifying and decommissioning applications that are no longer
needed.

IL
○ Advantages: Reduces cost and complexity; focuses resources on essential
applications.
○ Considerations: Requires careful assessment to avoid removing critical
functionality.
6. Retaining (Revisiting):
○ Definition: Keeping certain applications on-premises due to latency, regulatory, or
other considerations.
○ Advantages: Avoids the complexity and risk of moving certain applications;
H
maintains compliance and performance.
○ Considerations: Continued management and maintenance of on-premises
infrastructure.

# The Seven-Step Model of Migration Into a Cloud ➖

This model provides a structured approach to cloud migration, helping organizations
SA
systematically plan and execute their move to the cloud. The seven steps are as follows:

1. Assess:
○ Description: Evaluate the current IT environment, applications, and workloads to
determine suitability for cloud migration.
○ Activities: Conduct a thorough assessment of application dependencies,
performance requirements, and data storage needs.
2. Plan:
○ Description: Develop a detailed migration plan outlining the strategy, timeline,
and resources required.
○ Activities: Define the scope of migration, select the appropriate cloud service
provider, and establish a migration timeline.
3. Pilot:
○ Description: Test the migration process with a small, representative set of
applications.
○ Activities: Identify pilot applications, perform trial migrations, and address any
issues encountered during the pilot phase.
 9
4. Prepare:
○ Description: Prepare the cloud environment and the on-premises environment for
migration.
○ Activities: Set up the cloud infrastructure, configure network settings, and ensure
data security and compliance measures are in place.
5. Migrate:
○ Description: Execute the migration of applications and data to the cloud.
○ Activities: Move applications and data, verify data integrity, and ensure minimal
disruption to business operations.
6. Validate:
○ Description: Verify that the migrated applications are functioning correctly in the
cloud environment.

IL
○ Activities: Conduct testing to validate performance, security, and functionality;
make any necessary adjustments.
7. Optimise:
○ Description: Optimise the cloud environment for performance, cost-efficiency,
and scalability.
○ Activities: Monitor cloud usage, implement cost-saving measures, and refine
cloud operations to maximise benefits.
H
Summary

Migrating to the cloud is a complex but highly rewarding process that requires careful planning
and execution. By understanding the different approaches to cloud migration and following a
structured model like the Seven-Step Model, organisations can effectively transition to the
cloud, harnessing its full potential while minimising risks and disruptions.
SA
 10

UNIT ➖ 02
● Virtualization: Introduction, Characteristics of Virtualized environment, Taxonomy
of Virtualization techniques, Virtualization and Cloud Computing, Pros and Cons

➖
of Virtualization, Hypervisor Technology Examples- Xen, VMware, Microsoft
Hyper-V

# Virtualization ➖

IL
Introduction

Virtualization is the process of creating a virtual version of something, such as hardware

platforms, storage devices, and network resources. It allows multiple operating systems and
applications to run on a single physical machine, sharing the resources of that machine across
multiple environments. Virtualization is a foundational technology for cloud computing,
enabling the efficient use and management of IT resources.

➖
H
Characteristics of a Virtualized Environment

1. Resource Pooling:
○ Physical resources such as CPU, memory, storage, and network bandwidth are
pooled and allocated dynamically to virtual machines (VMs) as needed.
2. Scalability:
○ Virtual environments can be scaled up or down quickly to meet changing
SA
demands, providing flexibility and efficiency.
3. Isolation:
○ Each VM operates independently, isolated from others. This ensures that issues in
one VM do not affect others.
4. Encapsulation:
○ VMs are encapsulated into files, making them easy to copy, move, and back up.
5. Hardware Independence:
○ VMs can run on any physical machine that supports the virtualization software,
providing greater flexibility in hardware usage.
6. Snapshots and Cloning:
○ Virtual environments support taking snapshots of VMs, allowing for quick recovery
and cloning for rapid deployment.

# Taxonomy of Virtualization Techniques ➖

1. Full Virtualization:
○ Description: The hypervisor provides a complete simulation of the underlying
hardware, allowing unmodified operating systems to run in isolation.
○ Examples: VMware ESXi, Microsoft Hyper-V.
 11
2. Para-Virtualization:
○ Description: The hypervisor provides an API for the operating system, which
requires modifications to the OS kernel. This technique improves performance by
reducing the overhead of virtualization.
○ Examples: Xen.
3. Hardware-Assisted Virtualization:
○ Description: Uses hardware features of modern CPUs (such as Intel VT-x and
AMD-V) to support virtualization, reducing the complexity and improving the
performance of the hypervisor.
○ Examples: VMware ESXi, Microsoft Hyper-V, Xen with hardware assistance.
4. Operating System-Level Virtualization:
○ Description: Multiple isolated user-space instances (containers) run on a single

IL
kernel, sharing the OS while maintaining isolation.
○ Examples: Docker, LXC (Linux Containers).

# Virtualization and Cloud Computing ➖

Virtualization is a key enabler of cloud computing. It allows cloud service providers to:

I. Efficiently utilize physical resources by running multiple VMs on a single server.

II. Provide scalable and flexible services that can be adjusted dynamically to meet user

III.
demands.
H
Isolate different users and applications to ensure security and reliability.

Cloud computing platforms rely heavily on virtualization to deliver Infrastructure as a Service

(IaaS), where users can rent virtual machines and other resources on-demand.

# Pros and Cons of Virtualization ➖

➖
SA
1. Pros:

I. Resource Optimization: Maximizes the utilization of physical resources.

II. Cost Savings: Reduces the need for physical hardware, leading to lower capital and
operating costs.
III. Flexibility: Provides easy scalability and quick provisioning of resources.
IV. Isolation: Ensures that applications and users are isolated from each other, improving
security and stability.
V. Disaster Recovery: Simplifies backup, replication, and recovery processes through VM
encapsulation.

2. Cons: ➖
I. Performance Overhead: Virtualization introduces some performance overhead due to
the hypervisor layer.
II. Complexity: Managing and maintaining a virtualized environment can be complex,
requiring specialized skills.
 12
III. Security Concerns: Although virtualization provides isolation, vulnerabilities in the
hypervisor can lead to security risks.

# Hypervisor Technology Examples ➖

1. Xen:
○ Type: Both para-virtualization and hardware-assisted virtualization.
○ Features: Open-source, supports a wide range of guest operating systems, high
performance, and scalability.
○ Use Cases: Data centers, cloud computing platforms (e.g., Amazon EC2).
2. VMware:
○ Type: Full virtualization.

IL
○ Features: Market leader in virtualization, robust feature set, high reliability, and
extensive management tools.
○ Products: VMware vSphere, VMware Workstation, VMware Fusion.
○ Use Cases: Enterprise IT, data centers, cloud service providers.
3. Microsoft Hyper-V:
○ Type: Full virtualization and hardware-assisted virtualization.
○ Features: Integrated with Windows Server, easy management through familiar
Windows interfaces, supports a wide range of operating systems.
○ Use Cases: Enterprise IT, Windows-based data centers, hybrid cloud

Summary ➖
H
environments.

Virtualization is a crucial technology that enables efficient and flexible use of IT resources,
forming the backbone of modern cloud computing. By understanding the different types of
virtualization techniques and their applications, organizations can better leverage these
SA
technologies to optimize their infrastructure, reduce costs, and enhance performance. Despite
its many advantages, virtualization also comes with challenges that need careful consideration
and management.

● Capacity Planning: Elasticity vs Scalability, Introduction, Defining Baseline and

➖
Metrics-Baseline Measurements, System Metrics, Load Testing, Resource
Ceilings, Server and Instance types; Network Capacity, Scaling

# Capacity Planning ➖
Capacity planning is the process of determining the resources required to meet current and
future demands in a computing environment. Effective capacity planning ensures that IT
infrastructure can handle workloads efficiently, maintaining performance and avoiding
over-provisioning or under-provisioning.
 ➖
13
# Elasticity vs Scalability

Elasticity and scalability are key concepts in capacity planning, particularly in cloud computing
environments:

I. Elasticity:
A. Definition: The ability of a system to automatically expand and contract its
resources based on the current demand.
B. Example: Automatically adding more virtual machines during peak hours and
releasing them during off-peak hours.
C. Benefit: Cost efficiency, as resources are dynamically allocated only when
needed.
II. Scalability:

IL
A. Definition: The ability of a system to handle increasing workloads by adding
resources either vertically (adding more power to existing machines) or
horizontally (adding more machines).
B. Example: Adding more servers to a cluster to handle increased web traffic.
C. Benefit: Ensures that performance remains consistent as demand grows.

# Introduction to Capacity Planning

H ➖
Capacity planning involves analyzing current resource usage, predicting future requirements,
and implementing strategies to ensure that IT resources can meet these demands without
compromising performance. It is crucial for preventing downtime, maintaining user satisfaction,
and optimizing costs.

# Defining Baseline and Metrics ➖

➖
SA
1. Baseline Measurements:

● Definition: A baseline is a set of performance metrics collected during normal operations,

serving as a reference point for future comparisons.
● Purpose: To understand the current performance and resource utilization of the system.

2. System Metrics: ➖
● CPU Usage: Measures the percentage of CPU capacity being used.
● Memory Usage: Indicates how much of the available memory is being used.
● Disk I/O: Monitors the read and write operations on the disk.
● Network Throughput: Measures the amount of data being transmitted and received
over the network.

# Load Testing ➖
1. Load Testing:
I. Definition: A process of placing demand on a system and measuring its response.
II. Purpose: To identify how the system performs under various levels of load, revealing
potential bottlenecks and ensuring that it can handle expected traffic.
 ➖
14
# Resource Ceilings

1. Resource Ceilings: ➖
I. Definition: The maximum limits of resources (CPU, memory, storage) that a system can
use.
II. Purpose: To prevent a single application or service from consuming all available
resources, which could lead to performance degradation for other applications.

# Server and Instance Types ➖

1. Server and Instance Types: ➖

I. Definition: Different types of servers or virtual machine instances available for use, each

IL
optimized for specific tasks.
II. Examples:
A. General-purpose Instances: Balanced CPU, memory, and network resources.
B. Compute-optimized Instances: Higher CPU performance, suitable for
computational tasks.
C. Memory-optimized Instances: More memory, ideal for large datasets and
memory-intensive applications.
D. Storage-optimized Instances: High I/O performance, suitable for databases and

# Network Capacity
H
large-scale storage systems.

1. Network Capacity:
➖
➖
I. Definition: The amount of data that can be transmitted over a network within a given time
period.
SA
II. Purpose: To ensure that the network can handle peak traffic without congestion or
performance issues.
III. Considerations: Bandwidth, latency, and throughput requirements for different
applications and services.

# Scaling ➖
1. Scaling: ➖

I. Vertical Scaling (Scaling Up):

A. Definition: Adding more power (CPU, RAM) to an existing server.
B. Pros: Simple to implement; no changes to application architecture.
C. Cons: Limited by the maximum capacity of a single machine; potential single
point of failure.
II. Horizontal Scaling (Scaling Out):
A. Definition: Adding more servers or instances to distribute the load.
B. Pros: Increases capacity and redundancy; can handle more significant increases
in demand.
 15
C. Cons: More complex to manage; requires load balancing and possibly changes to
application architecture.

Summary ➖
Capacity planning is essential for maintaining the performance and reliability of IT systems. By
understanding and implementing the principles of elasticity, scalability, and thorough baseline
measurements, organisations can effectively manage resources to meet current and future
demands. Load testing, resource ceilings, and appropriate server and instance types further
contribute to robust capacity planning. Effective network capacity management and strategic
scaling ensure that systems remain responsive and efficient, even as demand fluctuates.

IL
H
SA
 16

UNIT ➖ 03
● SLA Management in Cloud Computing: Inspiration, Traditional Approaches to SLO

➖
Management, Types of SLA, Life Cycle of SLA, SLA management in Cloud.
Automated Policy-based management

# SLA Management in Cloud Computing ➖

# Inspiration ➖

IL
Service Level Agreements (SLAs) in cloud computing are inspired by the need to ensure
consistent and reliable service delivery from cloud service providers (CSPs) to customers.
SLAs define the performance and quality standards that customers can expect and outline the
remedies or compensations available if these standards are not met. They provide a
formalised way to manage expectations and responsibilities, fostering trust between CSPs and
customers.

# Traditional Approaches to SLO Management ➖

H
Service Level Objectives (SLOs) are specific, measurable characteristics of the SLA, such as
uptime, response time, and throughput. Traditional approaches to SLO management include:

1. Manual Monitoring:
○ Regularly checking system performance against predefined thresholds.
○ Reporting metrics manually to stakeholders.
SA
2. Reactive Management:
○ Responding to incidents as they occur rather than preventing them.
○ Focused on troubleshooting and resolving issues after they impact the user
experience.
3. Periodic Reviews:
○ Conducting scheduled reviews of performance data to identify trends and areas
for improvement.
○ Adjusting SLOs and operational practices based on review outcomes.
4. Basic Automation:
○ Utilizing simple scripts or tools to automate repetitive monitoring tasks.
○ Limited to basic threshold alerts without advanced analytics.

# Types of SLA ➖
1. Service-based SLA:
○ Covers one service for all customers.
○ Example: An SLA for an email service that guarantees 99.9% uptime for all users.
2. Customer-based SLA:
○ Customized for individual customers, covering all services used by that customer.
 17
○ Example: An SLA for a specific company that includes different performance
guarantees for email, database, and storage services.
3. Multi-level SLA:
○ Combines service-based and customer-based SLAs, addressing different service
levels and customer needs.
○ Example: A layered approach where a general SLA is supplemented by specific
agreements for particular services or departments within an organization.

# Life Cycle of SLA ➖

1. Definition:
○ Identifying the services to be covered and the metrics to be measured.
○ Setting performance targets and penalties for non-compliance.

IL
2. Negotiation:
○ Discussing the terms of the SLA with stakeholders to ensure mutual agreement.
○ Customizing the SLA to meet specific business needs and legal requirements.
3. Implementation:
○ Deploying monitoring tools and processes to track performance against SLA
metrics.
○ Training staff and configuring systems to adhere to SLA requirements.
4. Monitoring:
H
○ Continuously tracking performance data to ensure compliance with SLOs.
○ Utilizing automated tools and dashboards for real-time visibility.
5. Reporting:
○ Generating regular reports on SLA performance for stakeholders.
○ Highlighting areas of compliance and non-compliance.
6. Review and Improvement:
SA
○ Periodically reviewing SLA performance and making necessary adjustments.
○ Updating SLAs to reflect changing business needs or technological
advancements.

# SLA Management in Cloud ➖

SLA management in cloud environments involves several unique challenges and
considerations:

1. Dynamic and Scalable Environments:

○ Cloud resources are dynamically allocated, requiring flexible and adaptive SLA
management.
○ Scaling up or down can impact performance metrics, necessitating continuous
adjustment.
2. Multi-Tenancy:
○ Shared infrastructure among multiple customers can lead to resource contention.
○ SLAs must account for potential variability in performance due to multi-tenancy.
3. Geographical Distribution:
○ Cloud services are often distributed across multiple data centers and regions.
 18
○ SLAs should consider latency, data sovereignty, and compliance with regional
regulations.
4. Automated and Real-Time Monitoring:
○ Advanced monitoring tools and analytics are used to track SLA compliance in
real-time.
○ Automated alerts and corrective actions help maintain SLA standards without
manual intervention.

# Automated Policy-based Management ➖

Automated policy-based management in cloud computing leverages predefined policies and
rules to manage resources and ensure SLA compliance automatically. Key components
include:

IL
1. Policy Definition:
○ Creating rules and policies that specify desired performance levels, thresholds,
and actions.
○ Example: A policy that triggers the provisioning of additional resources if CPU
utilization exceeds 80%.
2. Real-Time Monitoring and Analytics:
○ Continuously collecting and analyzing performance data to detect deviations from
SLOs.
H
○ Utilizing machine learning and predictive analytics to anticipate and prevent SLA
breaches.
3. Automated Actions:
○ Implementing automated responses to policy violations, such as scaling
resources, rerouting traffic, or notifying administrators.
○ Ensuring that corrective measures are taken promptly to maintain SLA
SA
compliance.
4. Self-Healing Systems:
○ Designing systems that can automatically recover from failures or performance
issues.
○ Example: Automatically restarting a failed virtual machine or switching to a backup
server.
5. Feedback and Improvement:
○ Continuously refining policies based on performance data and incident analysis.
○ Implementing a feedback loop to improve the accuracy and effectiveness of
automated management.

Summary

SLA management is critical in cloud computing for ensuring reliable and consistent service
delivery. By understanding traditional SLO management approaches, different types of SLAs,
and the life cycle of SLAs, organizations can effectively manage their cloud resources.
Automated policy-based management further enhances SLA compliance by leveraging
 19
real-time monitoring, analytics, and automated actions to maintain performance standards
dynamically and efficiently.

● Securing Cloud services: Cloud Security, Securing Data- Brokered Cloud Storage

➖
Access, Storage location and tenancy, Encryption, Auditing and compliance.
Steps to ensure security over cloud

# Securing Cloud Services ➖

Securing cloud services involves multiple layers of protection to ensure data privacy, integrity,
and compliance with regulatory standards. This includes securing the infrastructure,

IL
applications, and data stored in the cloud. Here’s an overview of the key aspects of cloud
security and the steps to ensure robust security over cloud services:

# Cloud Security ➖
Cloud Security encompasses a broad range of policies, technologies, and controls designed to
protect data, applications, and the associated infrastructure of cloud computing. Key
components include:
H
1. Identity and Access Management (IAM):
○ Ensuring that only authorized users and devices can access cloud resources.
○ Implementing multi-factor authentication (MFA) and role-based access controls
(RBAC).
2. Network Security:
○ Using firewalls, VPNs, and secure network architectures to protect data in transit.
○ Implementing intrusion detection and prevention systems (IDS/IPS).
SA
3. Data Security:
○ Encrypting data at rest and in transit to prevent unauthorized access.
○ Regularly backing up data and ensuring secure storage.
4. Application Security:
○ Conducting regular vulnerability assessments and penetration testing.
○ Implementing secure coding practices and patch management.
5. Endpoint Security:
○ Securing devices that access cloud services using antivirus, anti-malware, and
endpoint detection and response (EDR) solutions.

# Securing Data ➖
Securing data in the cloud involves several critical steps:

1. Brokered Cloud Storage Access:

I. Using a third-party broker to manage access to cloud storage.

II. Ensuring that the broker enforces strict access controls and monitors data access for
suspicious activity.
 20
2. Storage Location and Tenancy:

I. Knowing where data is physically stored and ensuring compliance with data residency
regulations.
II. Understanding the implications of multi-tenancy and ensuring that data isolation
mechanisms are in place to prevent data leakage between tenants.

3. Encryption:

I. Encrypting data both at rest and in transit using strong encryption algorithms (e.g.,
AES-256).
II. Managing encryption keys securely using hardware security modules (HSMs) or cloud
key management services (KMS).

IL
4. Auditing and Compliance:

I. Implementing continuous monitoring and auditing to ensure compliance with regulatory

standards (e.g., GDPR, HIPAA, SOC 2).
II. Maintaining detailed logs of access and changes to cloud resources for forensic
analysis.

# Steps to Ensure Security Over Cloud ➖

following steps:
H
Ensuring security over cloud services involves a comprehensive approach that includes the

1. Risk Assessment:
○ Conduct a thorough risk assessment to identify potential threats and
vulnerabilities.
SA
○ Prioritize risks based on their potential impact and likelihood.
2. Security Policies and Procedures:
○ Develop and enforce security policies and procedures that align with industry best
practices and regulatory requirements.
○ Ensure that all employees and stakeholders are aware of and comply with these
policies.
3. Access Control:
○ Implement strict access controls to ensure that only authorized users can access
sensitive data and systems.
○ Regularly review and update access controls based on the principle of least
privilege.
4. Data Protection:
○ Use encryption to protect data both at rest and in transit.
○ Implement data loss prevention (DLP) solutions to detect and prevent data
breaches.
5. Monitoring and Logging:
○ Continuously monitor cloud environments for suspicious activity and potential
security incidents.
 21
○ Use logging and monitoring tools to maintain detailed records of access and
changes to cloud resources.
6. Incident Response:
○ Develop and maintain an incident response plan to quickly and effectively respond
to security incidents.
○ Regularly test and update the incident response plan to ensure its effectiveness.
7. Regular Audits and Assessments:
○ Conduct regular security audits and assessments to identify and address
vulnerabilities.
○ Use third-party auditors to provide an independent assessment of security
controls.
8. Security Awareness Training:

IL
○ Provide regular security awareness training to employees to ensure they
understand the risks and how to mitigate them.
○ Encourage a culture of security awareness and vigilance.
9. Compliance Management:
○ Ensure compliance with relevant regulatory requirements and industry standards.
○ Regularly review and update compliance practices to address new regulations
and standards.
10. Backup and Disaster Recovery:

Summary
H
○ Implement robust backup and disaster recovery plans to ensure data availability
and integrity in the event of a security incident.
○ Regularly test backup and recovery procedures to ensure they work as intended.

Securing cloud services requires a comprehensive approach that includes identity and access
SA
management, network and data security, application and endpoint security, and continuous
monitoring and auditing. By implementing robust security policies and procedures, encrypting
data, and ensuring compliance with regulatory standards, organizations can protect their cloud
environments from threats and vulnerabilities. Regular risk assessments, security training, and
incident response planning are essential to maintaining a secure and resilient cloud
infrastructure.
 22

UNIT ➖ 04
● Cloud Platforms in Industry: Amazon Web Services-Compute Services, Storage
Services, Communication Services, Additional Services. Google
AppEngine-Architecture and Core Concepts, Application Life Cycle. Cost Model.

➖
Microsoft Azure-Azure Core Concepts, SQL Azure, Windows Azure Platform
Appliance

Cloud Platforms in Industry ➖

IL
# Amazon Web Services (AWS) ➖
1. Compute Services: ➖
I. Amazon EC2 (Elastic Compute Cloud): Provides resizable compute capacity in the cloud.
EC2 instances can be used to run applications, host websites, or perform
high-performance computing.
II. AWS Lambda: Allows you to run code without provisioning or managing servers. You

III.

IV.
H
only pay for the compute time you consume.
Amazon ECS (Elastic Container Service): A container orchestration service that
makes it easy to deploy, manage, and scale containerized applications.
AWS Fargate: A serverless compute engine for containers that works with both ECS
and EKS (Elastic Kubernetes Service).

2. Storage Services: ➖
SA
I. Amazon S3 (Simple Storage Service): Scalable object storage with industry-leading
durability, availability, and performance.
II. Amazon EBS (Elastic Block Store): Provides block-level storage volumes for use with
EC2 instances.
III. Amazon Glacier: Secure, durable, and low-cost storage service for data archiving and
long-term backup.
IV. Amazon FSx: Fully managed file systems optimized for a variety of workloads, including
Windows-based applications and high-performance computing.

3. Communication Services: ➖
I. Amazon SNS (Simple Notification Service): A managed service that provides
message delivery from publishers to subscribers (e.g., email, SMS).
II. Amazon SQS (Simple Queue Service): A fully managed message queuing service that
enables decoupling and scaling of microservices, distributed systems, and serverless
applications.
 ➖
23
4. Additional Services:

I. Amazon RDS (Relational Database Service): Makes it easy to set up, operate, and
scale a relational database in the cloud.
II. Amazon DynamoDB: A fast, flexible NoSQL database service for single-digit
millisecond performance.
III. Amazon CloudFront: A fast content delivery network (CDN) service that securely
delivers data, videos, applications, and APIs to customers globally.

# Google App Engine ➖

1. Architecture and Core Concepts: ➖

IL
I. App Engine Standard Environment: Runs applications in a sandbox and supports several
programming languages (e.g., Python, Java, Node.js, PHP).
II. App Engine Flexible Environment: Runs applications in Docker containers on Google
Compute Engine VMs, providing more flexibility in terms of runtime and scalability.
III. Auto-Scaling: Automatically scales the number of instances based on the application's
load.
IV. Integrated Services: Includes built-in services like a NoSQL datastore, memcache, and
user authentication APIs.

➖
I.
H
2. Application Life Cycle:

Development: Write your code using supported languages and frameworks, and use
the Google Cloud SDK for local testing and debugging.
II. Deployment: Deploy applications to App Engine using the gcloud command-line tool or
the Cloud Console.
SA
III. Scaling: App Engine automatically scales your application based on traffic, ensuring
high availability and performance.
IV. Monitoring: Use Google Cloud's monitoring and logging services to track application
performance and troubleshoot issues.

3. Cost Model: ➖
I. Pay-as-You-Go: Charges are based on the resources your application uses, such as
instance hours, bandwidth, and storage.
II. Free Tier: Provides a limited amount of resources at no charge, making it cost-effective
for small applications and development environments.

# Microsoft Azure ➖
1. Azure Core Concepts: ➖
I. Azure Virtual Machines: On-demand, scalable computing resources that can run Windows
and Linux operating systems.
II. Azure App Service: A fully managed platform for building, deploying, and scaling web
apps and APIs.
 24
III. Azure Functions: A serverless compute service that allows you to run event-driven
code without managing infrastructure.
IV. Azure Kubernetes Service (AKS): Simplifies the deployment, management, and
operations of Kubernetes.

2. SQL Azure: ➖
I. Azure SQL Database: A fully managed relational database service with built-in
intelligence, high availability, and scalability.
II. SQL Managed Instance: Provides a managed environment with SQL Server
compatibility, enabling easy migration of on-premises SQL Server databases.

3. Windows Azure Platform Appliance: ➖

IL
I. Hybrid Cloud: Allows organisations to run Azure services within their own data centres,
providing the benefits of cloud computing while meeting regulatory and compliance
requirements.
II. Consistency: Ensures a consistent experience across on-premises, cloud, and edge
environments, simplifying management and development.

Summary
H
Cloud platforms like AWS, Google App Engine, and Microsoft Azure provide a wide range of
services and tools to meet diverse computing needs. AWS offers a comprehensive suite of
compute, storage, and communication services, while Google App Engine focuses on a highly
scalable and integrated platform for web applications. Microsoft Azure provides robust support
for both cloud-native and hybrid environments, with a strong emphasis on enterprise
integration and database services. Each platform has its own strengths and cost models,
SA
allowing organisations to choose the best fit for their specific requirements.

😀😀
HAPPY ENDING BY : SAHIL RAUNIYAR /
PTU-CODER !