Cloud Services Management

Understand Cloud Service Management terminology, definition &

concepts

• Analyse and Compare the cloud service management with

traditional IT service

management

• Identify strategies to reduce risk and eliminate issues associated

with adoption of
Course
Learning cloud services

Objectives • Select appropriate structures for designing, deploying and running

cloud-based

services in a business environment

• Illustrate the benefits and drive the adoption of cloud-based

services to solve real

world problems

Exhibit cloud-design skills to build and automate business solutions

using cloud technologies.

Course Implement the theoretical foundation leading to excellence and

excitement towards adoption of cloud-based services
Outcomes
Solve the real world problems using Cloud services and technologies

Unit I: Cloud Service Management Fundamentals

Cloud Ecosystem, The Essential Characteristics, Basics of Information

Technology Service Management and Cloud Service Management, Service
Perspectives, Cloud Service Models, Cloud Service Deployment Models

Unit II: Cloud Services Strategy

Cloud Strategy Fundamentals, Cloud Strategy Management Framework,

 Cloud Policy, Key Driver for Adoption, Risk Management, IT Capacity and
Utilization, Demand and Capacity matching, Demand Queueing, Change
Management, Cloud Service Architecture

Unit III: Cloud Service Management

Cloud Service Reference Model, Cloud Service LifeCycle, Basics of Cloud

Service Design, Dealing with Legacy Systems and Services, Benchmarking of
Cloud Services, Cloud Service Capacity Planning, Cloud Service Deployment
and Migration, Cloud Marketplace, Cloud Service Operations

Management

Unit IV: Cloud Service Economics

Pricing models for Cloud Services, Freemium, Pay Per Reservation, Pay per
User, Subscription based Charging, Procurement of Cloud-based Services,
Capex vs Opex Shift, Cloud service Charging, Cloud Cost Models

Unit V: Cloud Service Governance & Value

IT Governance Definition, Cloud Governance Definition, Cloud Governance

Framework, Cloud Governance Structure, Cloud Governance Considerations,
Cloud Service Model Risk Matrix, Understanding Value of Cloud Services,
Measuring the value of Cloud Services, Balanced Scorecard, Total Cost of
Ownership

Course Duration: 45 Hours

Test Projects:

Use Cases

Use Case 1: Cloud Ecosystem Exploration

Objective:

Explore the cloud ecosystem of a selected cloud provider (AWS, GCP, or Azure) to
understand essential characteristics, service models, and deployment models.

Tasks:
Console Navigation:

Log in to the chosen cloud provider's console. Navigate through the console to
understand its layout and organization.[AWS Management console, Azure Portal,
Google Cloud Console].

Essential Characteristics:

Identify and understand the essential characteristics of cloud computing, such as

on- demand ,self-service[EC2,S3]Compute Engine, broad network
access[VPC,Virtual Networks], resource pooling, rapid elasticity, and measured
service[Cloud Watch,Azure Monitor].

Service Models Exploration:

Explore the three primary cloud service models: Infrastructure as a Service (IaaS),
Platform as a Service (PaaS), and Software as a Service (SaaS). Identify examples
of services within each model.

Deployment Models Investigation:

Investigate the three main cloud deployment models: Public Cloud, Private Cloud,
and Hybrid Cloud. Understand the characteristics and use cases for each
deployment model.
Learning Outcome:

Understanding of the chosen cloud provider's console navigation. Familiarity with

essential cloud characteristics, service models, and deployment models.

Evaluation:
MCQ Questions:

Assess knowledge of essential cloud characteristics and service models.

Live Session:

Present the navigation through the chosen cloud provider's console.

Feedback:

Evaluate the ability to identify and differentiate between cloud service models and
deployment models.

Use Case 2: Cloud Services Strategy

Objective:

Develop a cloud services strategy for a hypothetical business scenario using a

selected cloud provider (AWS, GCP, or Azure).

Tasks:
Define Key Drivers for Cloud Adoption:

Explore the following services to address key drivers:

AWS:

AWS Identity and Access Management (IAM) for secure and granular access
control. AWS Auto Scaling for efficient resource utilization.

GCP:

Google Cloud Identity and Access Management (IAM) for access

control. Google Cloud Pub/Sub for building event-driven systems.
Azure:
Azure Active Directory (AD) for identity and access
management. Azure Virtual Machine Scale Sets for high
availability.
Explore services for Risk management:

AWS:

AWS Config for assessing and auditing configurations.

AWS CloudTrail for tracking user activity and API
usage. GCP:

Google Cloud Config Management for configuration management.

Azure:
Azure Policy for enforcing policies and compliance.
Azure Monitor for monitoring and analyzing data.

Explore capacity and utilization management services:

AWS:
AWS CloudWatch for monitoring and alerting.

AWS Budgets for setting custom cost and usage budgets.

GCP:
Google Cloud Monitoring for resource and application
monitoring. Google Cloud Billing Budgets for managing costs.

Azure:
Azure Monitor for monitoring and diagnostics.

Azure Cost Management and Billing for managing costs.

Learning Outcome:
Ability to design a comprehensive cloud services strategy. Understanding of key
drivers, risk management, and best practices for the chosen cloud provider.
Evaluation:
MCQ Questions:

Assess understanding of key cloud adoption drivers and risk management concepts.

Live Session:

Present and discuss the developed cloud services strategy.

Feedback:

Evaluate the strategy's alignment with best practices and risk mitigation.

This use case provides hands-on experience exploring specific services offered
by cloud providers to address key elements of a cloud services strategy.
Use Case 3: Cloud Service Lifecycle Implementation

Objective:

Implement a cloud service lifecycle for a selected business application using

services from AWS, GCP, or Azure.

Tasks:
Define Application Architecture: AWS:
EC2 (Compute)

RDS (Relational Database Service)

GCP:

Compute Engine Cloud SQL

Azure:
Azure Virtual Machines Azure SQL Database
Configuration Management:

AWS:

AWS Elastic Beanstalk AWS Systems Manager

GCP:

Google App Engine, Google Cloud Deployment Manager

Azure:

Azure App Service

Azure Resource Manager

Continuous Integration/Continuous Deployment

(CI/CD): AWS:

AWS CodePipeline AWS CodeBuild AWS CodeDeploy

GCP:
Cloud Build

Cloud Source Repositories Cloud Deployment Manager

Azure:
Azure DevOps Azure Pipelines

Azure Resource Manager Templates

Monitoring and Logging:

AWS:

Amazon CloudWatch AWS CloudTrail

GCP:
Stackdriver Monitoring Stackdriver Logging
Azure:
Azure Monitor Azure Log Analytics
Scaling Strategies:
AWS:

Auto Scaling

Elastic Load Balancing

GCP:

Managed Instance Groups Load Balancing

Azure:

Virtual Machine Scale Sets Azure Load Balancer

Learning Outcome:

Proficiency in implementing cloud services throughout the application lifecycle.

Understanding of key services for configuration management, CI/CD, monitoring,
security, and scaling.

Evaluation:
MCQ Questions:

Assess understanding of selected cloud services for various lifecycle stages.

Live Session:

Demonstrate the implementation of key tasks using the chosen cloud provider's
console.

Feedback:

Evaluate the effectiveness of service integration and adherence to best practices.

Use Case 4: Cloud Service Economics Analysis

Objective:

Conduct an economic analysis of cloud services to optimize costs for a selected

business scenario using services from AWS, GCP, or Azure.
Business Context:

Imagine a growing e-commerce website that experiences varying traffic throughout

the year. During peak shopping seasons, the website faces a significant increase in
user traffic, requiring additional resources. The goal is to optimize costs while
ensuring the website can handle peak loads without overspending during periods of
lower demand.
Tasks:
Resource Cost Analysis:
AWS:

Estimate costs for EC2 instances to host the website, considering on-demand and
reserved instances. Evaluate costs for Amazon S3 for storing product images and
other static assets.

GCP:

Estimate costs for Compute Engine instances for web hosting, including preemptible
VMs for non-critical workloads. Analyze costs for Google Cloud Storage for media
files.

Azure:

Estimate costs for Virtual Machines to host the website, exploring reserved instances
for cost savings. Analyze costs for Azure Blob Storage for image storage.

Cost Monitoring and Management:

AWS:

Set up AWS Budgets to receive alerts when costs exceed predefined thresholds.
Use AWS Cost Explorer to analyze spending patterns.

GCP:

Configure billing alerts using GCP Billing Budgets. Utilize GCP Cost Explorer for
detailed cost breakdowns.
Azure:

Set up Azure Budgets and configure alerts for budget thresholds. Leverage Azure
Cost Management and Billing for in-depth cost insights.

Reserved Instances/Committed Use Discounts:

AWS:

Consider purchasing reserved instances for baseline compute needs.

GCP:

Explore committed use discounts for sustained usage of VMs.

Azure:

Investigate reserved VM instances for consistent compute workloads.

Spot Instances/Preemptible VMs:

AWS:

Use AWS Spot Instances during periods of low demand for cost-effective compute
resources.

GCP:

Utilize preemptible VMs for non-critical tasks during off-peak times.

Azure:

Explore Low Priority Virtual Machines for temporary and cost-efficient processing.

Storage Optimization:

AWS:

Implement S3 Lifecycle policies to transition infrequently accessed data to

cheaper storage classes.

GCP:

Use Object Lifecycle Management to automatically transition data to archival storage.

Azure:

Implement Blob Storage Lifecycle Management to manage data lifecycle and

reduce costs.

Learning Outcome:

Understanding of cost estimation, monitoring, and optimization strategies for an e-

commerce website.

Proficiency in utilizing cost management tools provided by AWS, GCP, or Azure.

Evaluation:
MCQ Questions:

Assess understanding of cost analysis and optimization concepts.

Live Session:

Demonstrate the application of cost optimization strategies for the given e-commerce
scenario.

Feedback:

Evaluate the effectiveness of cost management decisions in aligning with business

needs.

Use Case 5: Cloud Governance Implementation

Objective:

Implement cloud governance strategies to ensure compliance, security, and

efficient resource management for a simple business scenario using services from
AWS, GCP, or Azure.
Business Context:

Consider a corporate intranet portal used by employees for collaboration, document

sharing, and internal communications. The goal is to implement cloud governance
to enhance security, control costs, and maintain compliance with corporate policies.
Tasks:
Identity and Access Management (IAM):
AWS:

Implement AWS Identity and Access Management (IAM) to control access to AWS
services and resources.

GCP:

Utilize Google Cloud Identity and Access Management (IAM) to manage access
control.

Azure:

Implement Azure Active Directory to manage user identities and access.

Policy Enforcement:

AWS:

Implement AWS Organizations for policy-based management of multiple AWS

accounts. Utilize AWS Config to enforce and evaluate compliance rules.

GCP:

Use Resource Manager to apply and enforce policies across GCP projects.
Implement Google Cloud Security Command Center for security and policy
insights.

Azure:

Implement Azure Policy for enforcing organizational standards and assessing

compliance. Leverage Azure Security Center for threat protection and policy
management.

Cost Management:
AWS:

Utilize AWS Budgets to set cost and usage thresholds with alerts.
Implement AWS Cost Explorer for in-depth cost analysis.
GCP:

Set up GCP Budgets to control and monitor costs.

Use GCP Cost Explorer for analyzing and visualizing costs.

Azure:

Set up Azure Budgets and configure alerts for budget thresholds.

Leverage Azure Cost Management and Billing for detailed cost
insights.

Resource Tagging:
AWS:

Implement resource tagging for easy identification and cost allocation using AWS
Resource Groups.

GCP:

Utilize resource labels to organize resources and manage costs effectively.

Azure:

Implement resource tagging for categorization and cost management.

Security Best Practices:

AWS:

Implement AWS Key Management Service (KMS) for data

encryption. Use AWS CloudTrail for monitoring and logging API
requests.

GCP:
Utilize Google Cloud Key Management Service (KMS) for encryption.

Azure:

Implement Azure Key Vault for secure key management.

Learning Outcome:

Proficiency in implementing cloud governance strategies for a corporate intranet

portal. Understanding of IAM, policy enforcement, cost management, resource
tagging, and security best practices.

Evaluation:

MCQ Questions:

Assess understanding of cloud governance concepts and services.

Live Session:

Demonstrate the implementation of governance strategies for the given corporate

intranet scenario.

Feedback:

Evaluate the effectiveness of governance implementations in ensuring

compliance, security, and cost control.

Use case 6 : Cloud Service Model Risk Matrix & Understanding Value

Objective:

Implement a Cloud Service Model Risk Matrix and gain insights into the strategic
value of different cloud service models in AWS, Azure, or GCP for enhanced decision-
making.

Business Context:

Consider a scenario where a company is evaluating different cloud service models

(IaaS, PaaS, SaaS) for hosting its customer relationship management (CRM)
application on AWS, Azure or GCP. The goal is to assess the risks associated with
each service model and understand the strategic value they bring to the
organization on each cloud platform.
Tasks:
Cloud Service Model AWS:
Explore AWS services such as EC2 (IaaS), Elastic Beanstalk (PaaS), and Amazon
S3 (SaaS).

Azure:

Explore Azure services such as Azure Virtual Machines (IaaS), Azure App Service
(PaaS), and Office 365 (SaaS).

GCP:

Explore GCP services such as Compute Engine (IaaS), App Engine (PaaS), and G
Suite (SaaS).

Risk Identification and Assessment:

Develop a Cloud Service Model Risk Matrix identifying potential risks for IaaS, PaaS,
and SaaS on AWS, Azure, or GCP.

Mitigation Strategies:
AWS:

Develop mitigation strategies using AWS services such as AWS Identity and Access
Management (IAM) and AWS Config.

Azure:

Develop mitigation strategies using Azure services such as Azure Active Directory
and Azure Policy.

GCP:

Develop mitigation strategies using GCP services such as Google Cloud Identity
and Access Management (IAM) and Google Cloud Resource Manager.

Understanding Strategic Value:

AWS:

Examine the strategic value of AWS services for the CRM application, considering
scalability with Amazon EC2, simplified deployment with Elastic Beanstalk, and
robust storage with Amazon S3.

Azure:

Examine the strategic value of Azure services for the CRM application, considering
scalability with Azure Virtual Machines, simplified deployment with Azure App
Service, and collaboration with Office 365.

GCP:

Examine the strategic value of GCP services for the CRM application, considering
scalability with Compute Engine, simplified deployment with App Engine, and
collaboration with G Suite.

Learning Outcomes:

Participants will Understand different cloud services (like IaaS, PaaS, SaaS) on AWS,
Azure, or GCP, and know who's responsible for what and learn to identify and deal
with risks in cloud services on AWS, Azure, or GCP, and figure out smart ways to
handle them.

Evaluation:
MCQ Questions:

Assess understanding of hosting the CRM application on each service model on

AWS, Azure, or GCP.

Live Session:

Demonstrate the implementation of CRM application

Feedback:

Evaluate the effectiveness of application implementations in ensuring compliance,

security, and cost control.
Use case 7: Cloud Service Design and Legacy Systems Migration

Objective:

Explore cloud service design principles and strategies for migrating legacy
systems on three major cloud providers: AWS, Azure, or GCP.

Console Navigation:
AWS:

Log in to the AWS Management Console. Navigate through AWS services like EC2,
S3, and Lambda.Explore the console layout and organization.

Azure:

Log in to the Azure Portal. Explore Azure services, including Virtual Machines, Blob
Storage, and Azure Functions. Familiarize yourself with the layout of the Azure
Portal.

GCP:

Log in to the Google Cloud Console.Navigate through GCP services like Compute
Engine, Cloud Storage, and Cloud Functions.Understand the layout and organization
of the Google Cloud Console.

Cloud Service Design:

AWS:

Explore AWS services supporting cloud service design, such as AWS Lambda, AWS
Elastic Beanstalk, and Amazon RDS andIdentify examples of microservices or
serverless architectures.

Azure:
Investigate Azure services for service design, including Azure Functions, Azure App
Service, and Azure SQL Database. Identify tools or features promoting scalable and
resilient architectures.
GCP:

Explore GCP services like Google App Engine, Cloud Functions, and Cloud SQL for
service design.Identify features facilitating the design of scalable and distributed
applications.

Legacy Systems Migration:

AWS:

Investigate AWS services for migrating legacy systems, such as AWS Server
Migration Service and AWS Database Migration Service. Understand strategies like
rehosting, refactoring, and re architecting.

Azure:

Explore Azure services supporting legacy systems migration, including Azure

Migrate and Azure Database Migration Service. Understand migration strategies like
lift-and-shift and modernization.

GCP:

Investigate GCP services for legacy systems migration, such as Google Cloud
Migrate and Database Migration Service.Understand migration strategies aligning
with GCP's offerings.

Learning Outcome:

Upon completion, users gain proficiency in navigating AWS, Azure, or GCP consoles,
along with understanding cloud service design principles and associated services.
They also acquire insights into strategies and services for effective legacy systems
migration on these cloud platforms.

Evaluation:
MCQ Questions:

Assess knowledge of cloud service design principles and legacy systems migration
strategies on AWS, Azure, or GCP.
Live Session:

Participants present their navigation through the consoles and discuss chosen
services for cloud service design and legacy systems migration.

Feedback:

Evaluate participants' ability to identify and differentiate between cloud service

design principles and legacy systems migration strategies on different cloud platforms

Use case 8: Risk Management

Objective:

Implement a comprehensive risk management strategy for a selected business

application using services from AWS, GCP, or Azure.

Tasks:

Risk Identification and Assessment:

AWS:

AWS Identity and Access Management (IAM): Define and manage access
controls. AWS Config: Assess and audit resource configurations.

Amazon Inspector: Automated security assessment service.

GCP:

Identity and Access Management (IAM): Define and manage access controls.
Cloud Security Scanner: Web security scanner for identifying vulnerabilities.
Forseti Security: Open-source security toolkit for GCP environments.

Azure:

Azure Active Directory: Identity and access management.

Azure Security Center: Unified security management
system. Azure Policy: Implement and enforce governance
policies.

Risk Mitigation and Controls:

AWS:

AWS Key Management Service (KMS): Manage encryption keys.

AWS WAF: Web Application Firewall for protecting web applications.

GCP:

Cloud Key Management Service (KMS): Manage cryptographic

keys. Cloud Armor: DDoS and application defense.

Azure:

Azure Key Vault: Securely manage keys, secrets, and certificates.

Azure Application Gateway: Web application firewall.

Evaluation:
MCQ Questions:

Assess understanding of risk management tools and practices for AWS, GCP, and
Azure.

Live Session:

Demonstrate the implementation of risk identification, assessment, and mitigation

using the chosen cloud provider's console.

Feedback:
Evaluate the effectiveness of risk identification and mitigation strategies.

Use case 9 : Cloud Services Pricing Models

Objective:

Understand and compare the pricing models of cloud services offered by AWS, Azure,
or GCP to make informed decisions for cost-effective implementation.
Tasks:
AWS:
On-Demand Pricing:

Pay for compute capacity by the hour or second without any upfront commitment.

Reserved Instances (RIs):

Reserved capacity for 1 or 3 years, offering significant cost savings compared to On-
Demand pricing.

Spot Instances:

Bid for unused EC2 capacity, potentially saving up to 90% compared to On-
Demand pricing.

S3 Pricing:

Pay for storage space and data transfer for scalable and durable object storage.

Azure:
Pay-as-You-Go:

Pay for compute capacity per minute, with no upfront costs or termination fees.

Reserved VM Instances:

Commit to one or three years for discounted rates on virtual machine usage.

Azure Blob Storage Pricing:

Charges based on storage capacity, data retrieval, and data transfer.

GCP:
Compute Engine Pricing:

Pay for virtual machine instances based on usage, with sustained use discounts.

Preemptible VMs:

Low-cost, short-lived instances suitable for fault-tolerant workloads.

Cloud Storage Pricing:

Pay for storage capacity, data retrieval, and data transfer for scalable object storage.

Learning Outcome:

This use case aims to ensure a practical understanding of cloud services pricing
models, enabling participants to make informed decisions aligned with cost efficiency.

Evaluation:
MCQ Questions:

Assess knowledge of essential cloud services pricing models.

Live Session:

Pose scenarios for different pricing models and ask participants to recommend the
most cost-effective option.

Guide participants through using the cloud providers' pricing calculators to estimate
costs for a hypothetical workload.Feedback:

Assess participants' comprehension of each cloud provider's pricing models and

their ability to apply them.

Evaluate the accuracy of cost estimates generated during the live session.

Encourage participants to discuss and propose strategies for optimizing costs

based on the chosen pricing models.
Use case 10: Cloud Service Architecture and Demand/Capacity Matching

Objective:

Design a scalable and cost-effective cloud service architecture that dynamically

matches the demand and capacity for a given business scenario. The focus is on
optimizing performance during peak loads while efficiently scaling down during
periods of lower demand.

Business Context:

Consider an online streaming platform that experiences varying viewership

throughout the day. During peak hours, the platform faces a surge in users,
requiring additional resources to ensure seamless streaming. The goal is to architect
a solution that can dynamically scale to meet demand while minimizing costs during
off-peak hours.

Tasks:

Cloud Service Architecture Design:

AWS:

Utilize Amazon EC2 Auto Scaling to automatically adjust the number of EC2 instances
based on demand.

Explore Amazon RDS for scalable and managed relational databases.

GCP:

Leverage Google Kubernetes Engine (GKE) for containerized applications with

automatic scaling. Explore Cloud Spanner for globally distributed and scalable
databases.

Azure:

Implement Azure App Service with Autoscaling to automatically adjust the number
of app service instances. Explore Azure Cosmos DB for globally distributed, multi-
model databases.

Demand and Capacity Matching:

AWS:

Set up Amazon CloudWatch alarms to trigger scaling actions based on predefined

metrics. Use AWS Auto Scaling policies to dynamically adjust capacity in response
to changing demand.

GCP:

Configure Stackdriver Monitoring alerts to trigger scaling based on custom metrics.

Use GKE Horizontal Pod Autoscaler for automatic pod scaling based on observed
metrics.
Azure:

Utilize Azure Monitor alerts to trigger scaling based on metrics and activity logs.
Implement Azure Autoscale to dynamically adjust the number of VMs or instances.

Cost Optimization:
AWS:

Leverage AWS Spot Fleet during periods of low demand for cost-effective compute
resources.

GCP:

Utilize replaceable VMs for non-critical workloads during off-peak times.

Azure:

Explore Low Priority Virtual Machines for temporary and cost-efficient processing

Learning Outcome:

Understanding of cloud service architectures that dynamically scale to match

demand, proficiency in implementing auto scaling strategies, and knowledge of cost
optimization techniques for variable workloads in cloud environments.

Evaluation:
MCQ Questions:

Assess knowledge of essential cloud services pricing models which demand and
capacity.

Live Session:

Guide participants through using the cloud providers' pricing calculators to estimate
costs for a hypothetical workload.

Feedback:

Assess participants' on cloud service architectures that dynamically scale to match

demand, proficiency in implementing auto scaling strategies, and knowledge of cost
optimization techniques for variable workloads in cloud environments.
Use case 11 : Cloud Service Reference Model

Objective:

Establish a comprehensive reference model for cloud services, covering AWS, Azure,
or GCP, to facilitate understanding, comparison, and implementation.

Tasks:
Compute:
AWS

EC2 (Elastic Compute Cloud): Scalable virtual servers. AWS Lambda:

Serverless computing for code execution.

Azure

Azure Virtual Machines: On-demand scalable computing resources. Azure

Functions: Serverless compute service.

GCP

Compute Engine: Virtual machines for running applications. Google Cloud

Functions: Event-driven serverless functions.

Storage:
AWS

S3 (Simple Storage Service): Object storage for scalable and durable data
storage. EBS (Elastic Block Store): Persistent block storage volumes.

Azure

Azure Blob Storage: Scalable object storage for large amounts of unstructured
data. Azure Table Storage: NoSQL data store for semi-structured data.

GCP
Cloud Storage: Object storage for the storage and retrieval of any amount of
data. Cloud Firestore: Serverless NoSQL document database.
Database:
AWS

RDS (Relational Database Service): Managed relational databases.

Azure

Azure SQL Database: Fully managed relational database service.

GCP

Cloud SQL: Fully managed relational database service.

Networking:
AWS

VPC (Virtual Private Cloud): Isolated cloud resources.

Azure

Azure Virtual Network: Connect, isolate, and scale Azure resources.

GCP

VPC (Virtual Private Cloud): Global, scalable, and flexible networking.

Learning Outcome:

Proficiency in understanding and implementing cloud services across AWS, Azure,

or GCP. Gain insights into the reference models of each cloud provider to make
informed decisions in designing and deploying cloud-based applications.

Evaluation:
MCQ Questions:

Assess understanding of the reference models and the key components of AWS,
Azure, or GCP.

Live Session:

Demonstrate the practical implementation of key tasks within the reference model
using the respective cloud providers' consoles.
Feedback:

Evaluate the effectiveness of service integration, adherence to best practices, and

the ability to make informed choices based on the reference models provided.

Use case 12 : Cloud Service Deployment Models & Deployment/Migration

Objective:

Explore different cloud service deployment models and implement a strategy for
deploying and migrating applications to the cloud. The goal is to understand the
various deployment options and efficiently transition existing systems to a cloud
environment.

Business Context:

Imagine a company that currently runs its applications and services on on-premises
servers. The goal is to move these applications to the cloud to take advantage of
scalability, flexibility, and cost savings. Additionally, explore different deployment
models to understand their implications for the business.

Tasks:
Cloud Service Deployment Models:
Public Cloud:
AWS: Utilize Amazon Web Services (AWS) as the public cloud provider.
GCP: Leverage Google Cloud Platform (GCP) as another public cloud
option.

Azure: Explore Microsoft Azure as the third public cloud provider.

Private Cloud:
AWS: While AWS primarily provides public cloud services, consider using AWS
Outposts for a managed private cloud experience.

GCP: Utilize Google Cloud's Anthos for a hybrid cloud approach that includes
private cloud capabilities.

Azure: Azure Stack Hub can be employed to extend Azure services to an on-premises
environment, providing a private cloud solution.

Hybrid Cloud:

AWS: Implement AWS Outposts for a consistent hybrid cloud experience.

GCP: Use Google Cloud Anthos for managing applications across on-premises and
cloud environments seamlessly.

Azure: Leverage Azure Arc for extending Azure services and management to any
infrastructure, whether on-premises, multi-cloud, or edge.

Deployment to the Cloud:

AWS:

Utilize AWS Elastic Beanstalk for an easy and quick deployment experience.
Implement AWS CodeDeploy for automated application deployments.

GCP:

Deploy applications using Google App Engine for a fully managed and serverless
platform. Utilize Google Cloud Deployment Manager for infrastructure as code.

Azure:

Deploy applications using Azure App Service for a fully managed platform-as-a-
service (PaaS) experience.

Migration to the Cloud:

Rehosting (Lift and Shift):

Use AWS Server Migration Service (SMS) to move your programs to Amazon's
cloud. Try Google Cloud Migrate for Compute Engine to shift your servers to
Google's cloud.

Refactoring (Lift, Tinker, and Shift):

Optimize programs for the cloud with AWS Lambda for simpler, event-driven
computing. Use Google Cloud Functions for handling tasks without worrying about
servers.

Re-architecting (Rebuild):

Redesign programs for the cloud with AWS Lambda and Amazon API Gateway for
flexible and small parts.

Use Google Kubernetes Engine (GKE) to set up and manage your programs in
containers. Try Azure Kubernetes Service (AKS) for managing and growing your
programs in containers.

Learning Outcome:

Understanding the deployment models and services offered by AWS, GCP, and
Azure, and proficiency in using specific tools and services for deploying and
migrating applications in each cloud environment.

Use case 13: IT Governance Exploration on AWS, Azure, or GCP

Objective:

Explore IT Governance practices and tools on three major cloud providers: AWS,
Azure, or GCP.

Task:
Console Navigation:
AWS

Log in to the AWS Management Console. Navigate through AWS services relevant
to IT Governance, such as AWS Identity and Access Management (IAM), AWS
Organizations, and AWS Config.

Azure
Log in to the Azure Portal. Explore Azure services like Azure Active Directory,
Azure Policy, and Azure Blueprints for IT Governance.
GCP

Log in to the Google Cloud Console. Navigate through GCP services such as Google
Cloud Identity and Access Management (IAM), Resource Manager, and Cloud
Security Command Center.

IT Governance Practices:
AWS

Explore AWS services supporting IT Governance, emphasizing identity and access

management, compliance, and security.

Azure

Investigate Azure services designed for IT Governance, focusing on Azure Policy,

Azure Security Center, and Azure Blueprints.

GCP

Explore GCP services relevant to IT Governance, including Google Cloud Identity and
Access Management (IAM), Resource Manager, and Security Command Center.

Learning Outcome

Understanding of console navigation within AWS, Azure, or GCP. Familiarity with IT

Governance implementation using relevant services on each platform.

Evaluation MCQ Questions

Assess knowledge of IT Governance principles and practices on AWS, Azure, or GCP.

Live Session

Participants present their navigation through the consoles and discuss chosen
services for IT Governance.

Feedback

Evaluate participants' ability to identify and differentiate between IT Governance

practices on different cloud platforms.
Use case 14 : Procurement of Cloud-based Services and Capex vs Opex Shift
Exploration

Objective

Explore the procurement of cloud-based services and understand the shift from
Capital Expenditure (Capex) to Operational Expenditure (Opex) on three major
cloud providers: AWS, Azure, and GCP.

Task:
Console Navigation:
AWS

Log in to the AWS Management Console. Navigate through AWS services relevant
to cloud procurement, such as AWS Pricing Calculator, AWS Marketplace, and AWS
Budgets.

Azure

Log in to the Azure Portal. Explore Azure services related to cloud procurement,
including Azure Cost Management and Billing, Azure Marketplace, and Azure
Reservations.

GCP

Log in to the Google Cloud Console. Navigate through GCP services for cloud
procurement, such as Google Cloud Marketplace, Google Cloud Pricing Calculator,
and Google Cloud Billing.

Procurement of Cloud-based Services:

AWS

Explore AWS services for cloud procurement, including AWS Marketplace for third-
party solutions and various pricing models. Understand AWS Reserved Instances
and Savings Plans for cost optimization.

Azure

Investigate Azure services for cloud procurement, focusing on Azure Marketplace

for application services and Azure Reservations for reserved capacity. Explore Azure
Cost Management and Billing tools.

GCP

Explore GCP services related to cloud procurement, such as Google Cloud

Marketplace for solutions and Google Cloud Pricing Calculator for estimating costs.
Understand GCP Committed Use Discounts and sustained use pricing.

Capex vs Opex Shift:

AWS

Explore AWS pricing models, emphasizing the shift from Capex to Opex with on-
demand pricing and flexible payment options. Understand the financial benefits of
Opex-based cloud procurement.

Azure

Investigate Azure pricing models, highlighting the Opex advantages with pay-as-
you-go and reserved capacity options. Explore how Azure enables organizations to
align costs with actual usage.

GCP
Explore GCP pricing models, focusing on the Opex shift with per-second billing and
sustained use discounts. Understand the flexibility GCP provides in adjusting
resources based on business needs.
Learning Outcome

Understanding of console navigation within AWS, Azure, and GCP for cloud
procurement. Familiarity with cloud-based services procurement models on each
platform. Insight into the shift from Capex to Opex and its implications in cloud
procurement.
Evaluation MCQ Questions
Assess knowledge of cloud procurement models and the Capex vs Opex shift on
AWS, Azure, and GCP.
Live Session

Participants present their navigation through the consoles and discuss chosen
services for cloud procurement and cost management.

Feedback

Evaluate participants' ability to identify and differentiate between cloud

procurement models and understand the financial implications of the Capex to
Opex shift.

Use case 15: Total Cost of Ownership (TCO) and Balanced Scorecard
approach on Cloud Services

Objective:

Evaluate and compare the overall effectiveness and cost efficiency of the cloud
service lifecycle, encompassing AWS, Azure, and GCP, using the Balanced Scorecard
approach.

Task:
Total Cost of Ownership (TCO):
AWS:

Cost Explorer: Allows users to visualize, understand, and manage AWS costs and
usage. AWS Pricing Calculator: Helps estimate monthly costs based on selected
services and usage patterns.

Reserved Instances: Can significantly reduce costs by committing to a one- or three-

year term.

GCP:

Pricing Calculator: Allows users to estimate costs for GCP services based on usage.
Sustained Use Discounts: Automatically applied as usage increases, providing cost
savings. Committed Use Discounts: Offers discounts for committing to a
consistent amount of usage for a 1 or 3-year term.

Azure:

Azure Pricing Calculator: Provides cost estimates based on Azure services and
usage. Reserved Instances: Offers significant savings when committing to a 1 or
3-year term. Azure Cost Management and Billing: Allows monitoring and
controlling Azure spending.

Balanced Scorecard:
AWS:

Customer Metrics: AWS focuses on customer-centric metrics, including customer

satisfaction, support responsiveness, and service availability.

Operational Metrics: Monitors operational excellence, assessing performance,

reliability, and efficiency.

Financial Metrics: Tracks financial health, including cost management, resource

optimization, and return on investment.

GCP:

Customer Metrics: GCP emphasizes customer satisfaction and feedback, ensuring a

positive user experience. Operational Metrics: Focuses on reliability, scalability, and
performance of services.

Financial Metrics: Evaluates financial efficiency, cost-effectiveness, and resource

utilization.

Azure:

Customer Metrics: Azure values customer satisfaction, feedback, and loyalty.

Operational Metrics: Prioritizes reliability, availability, and performance of
services.

Financial Metrics: Assesses cost control, resource optimization, and return on

investment.
Learning Outcome:

Gain proficiency in analyzing and estimating the Total Cost of Ownership for cloud
services. Understand the importance of a Balanced Scorecard approach in
evaluating cloud service performance. Acquire knowledge of key metrics for
customer satisfaction, operational excellence, and financial efficiency.

Evaluation:
MCQ Questions:

Assess understanding of TCO estimation methods and Balanced Scorecard metrics.

Live Session:

Demonstrate the ability to use cost estimation tools and interpret Balanced Scorecard
metrics.

Feedback:

Evaluate the accuracy of TCO estimates and the effectiveness of applying Balanced
Scorecard principles in cloud service management.

Use Case 16: Multi-Region Deployment for High Availability

Objective:

Implement a multi-region deployment strategy for high availability of a web

application using services from AWS, GCP, or Azure.

Business Context:

Consider an e-commerce website that experiences high traffic and needs to ensure
availability and performance for users worldwide. The goal is to implement a multi-
region deployment to enhance the website's resilience and reduce latency for users
in different geographical locations.
Tasks:

Global Load Balancing:

AWS:

Utilize AWS Global Accelerator to distribute traffic across multiple AWS regions.

GCP:

Implement Global HTTP(S) Load Balancing to distribute traffic globally.

Azure:

Use Azure Traffic Manager for DNS-based global load balancing.

Multi-Region Deployment:

AWS:

Deploy the web application on EC2 instances across multiple AWS regions (e.g., North
America, Europe, Asia).

GCP:

Deploy the application on Compute Engine instances in different Google Cloud

regions.

Azure:

Deploy the application on Virtual Machines distributed across Azure regions.

Database Replication:
AWS:

Implement cross-region read replicas using Amazon RDS for database high
availability.

GCP:

Use Cloud SQL with read replicas in different regions for database redundancy.

Azure:

Implement Geo-Replication for Azure Database for PostgreSQL or MySQL.

Data Synchronization:
AWS:

Use AWS Database Migration Service (DMS) for real-time data replication between
regions.

GCP:

Implement Cloud Storage Transfer Service for efficient data transfer between
regions.

Azure:

Use Azure Storage Geo-Replication for asynchronous data replication.

Learning Outcome:

Proficiency in implementing multi-region deployment strategies for high availability.

Understanding of global load balancing, database replication, CDN usage, and data
synchronization.

Evaluation:
MCQ Questions:

Assess understanding of multi-region deployment concepts and services.

Live Session:

Demonstrate the implementation of a high-availability setup for the e-commerce

website.

Feedback:

Evaluate the effectiveness of the multi-region deployment in enhancing availability

and reducing latency for users worldwide.

Use Case 17: Disaster Recovery Planning

Objective:

Develop a disaster recovery plan for a business application using services from
AWS, GCP, or Azure to ensure data resilience and business continuity.
Business Context:

Imagine a finance management system critical for handling financial transactions.

The goal is to create a disaster recovery plan that ensures minimal data loss and
downtime in the event of a catastrophic failure.

Tasks:

Backup and Restore:

AWS:

Use Amazon S3 for regular backups of critical data and implement AWS Backup for
automated backup management.

GCP:

Utilize Cloud Storage for data backups and create automated backups using Cloud
Storage Object Lifecycle Management.

Azure:

Implement Azure Blob Storage for storing backup data and use Azure Backup for
automated backup solutions.

Cross-Region Replication:
AWS:

Implement cross-region replication for Amazon RDS databases to replicate data to a

secondary region.

GCP:

Use Cloud SQL with cross-region read replicas for database redundancy.

Azure:

Implement Geo-Replication for Azure Database for PostgreSQL or MySQL to

replicate data to a secondary region.
Failover Mechanism:

AWS:

Utilize AWS Route 53 for DNS failover to redirect traffic to a standby region in case
of a disaster.

GCP:

Implement Traffic Director for global traffic management and failover.

Azure:

Use Azure Traffic Manager for DNS-based failover to redirect traffic to a secondary
region.

Continuous Monitoring:
AWS:

Implement Amazon CloudWatch for continuous monitoring and set up alarms for
critical metrics.

GCP:

Utilize Stackdriver Monitoring for real-time insights and alerting.

Azure:

Implement Azure Monitor for monitoring applications, infrastructure, and network.

Automated Recovery Scripts:

AWS:

Develop AWS Lambda functions to automate recovery processes and reduce manual
intervention.

GCP:

Utilize Cloud Functions to automate recovery tasks and ensure rapid response to
disasters.

Azure:
Use Azure Functions for developing serverless scripts to automate recovery
procedures.

Learning Outcome:

Proficiency in designing disaster recovery plans for business applications.

Understanding of backup strategies, cross-region replication, failover mechanisms,

continuous monitoring, and automated recovery.

Evaluation:
MCQ Questions:

Assess understanding of disaster recovery concepts and services.

Live Session:

Demonstrate the implementation of disaster recovery mechanisms for the finance

management system.

Feedback:

Evaluate the effectiveness of the disaster recovery plan in ensuring data resilience
and business continuity in the face of a disaster.

Use Case 18: Dynamic Resource Scaling

Objective:

Implement dynamic resource scaling for an application to efficiently handle varying

workloads using services from AWS, GCP, or Azure.

Business Context:

Consider an e-learning platform that experiences fluctuating user activity, with peak
usage during specific hours. The goal is to implement dynamic resource scaling to
ensure optimal performance during high-demand periods and cost efficiency during
low-demand periods.

Tasks:
Auto Scaling Groups:
AWS:

Utilize AWS Auto Scaling to automatically adjust the number of EC2 instances based
on traffic.

GCP:

Implement Managed Instance Groups for automatic scaling of Compute Engine

instances.

Azure:

Use Virtual Machine Scale Sets for automatic scaling of VM instances.

Load Balancing:
AWS:

Employ Elastic Load Balancing (ELB) to distribute incoming traffic across multiple
instances.

GCP:

Utilize HTTP(S) Load Balancing for distributing traffic and managing the workload.

Azure:

Implement Azure Load Balancer for distributing network traffic across multiple VM
instances.

Container Orchestration:
AWS:

Use Amazon ECS or EKS for orchestrating containerized applications.

GCP:

Implement Google Kubernetes Engine (GKE) for container orchestration.

Azure:

Utilize Azure Kubernetes Service (AKS) for managing and orchestrating containerized
applications.
Serverless Computing:
AWS:

Leverage AWS Lambda for serverless execution of code in response to events.

GCP:

Utilize Cloud Functions for event-driven serverless computing.

Azure:

Use Azure Functions for building serverless applications with automatic scaling.

Monitoring and Metrics:

AWS:

Implement Amazon CloudWatch for monitoring application metrics and setting up

auto- scaling policies.

GCP:

Utilize Stackdriver Monitoring for real-time monitoring and creating alerts based
on metrics.

Azure:

Use Azure Monitor to collect, analyze, and act on telemetry data from applications
and infrastructure.

Learning Outcome:

Proficiency in implementing dynamic resource scaling for applications.

Understanding of auto scaling groups, load balancing, container orchestration,

serverless computing, and monitoring.

Evaluation:
MCQ Questions:

Assess understanding of dynamic resource scaling concepts and services.

Live Session:
Demonstrate the implementation of dynamic resource scaling for the e-learning
platform.

Feedback:

Evaluate the effectiveness of dynamic resource scaling in optimizing performance

and cost efficiency based on varying workloads.

Use Case 19: Cloud Security Best Practices

Objective:

Implement cloud security best practices to ensure the confidentiality, integrity, and
availability of data and resources using services from AWS, GCP, or Azure.

Business Context:

Imagine a Software as a Service (SaaS) collaboration platform handling sensitive

business documents and communications. The goal is to implement robust cloud
security measures to protect user data, prevent unauthorized access, and ensure
compliance with data protection regulations.

Tasks:
Identity and Access Management (IAM):
AWS:

Configure AWS IAM policies to enforce least privilege access for users and resources.

GCP:

Utilize Google Cloud IAM to manage access control and permissions.

Azure:

Implement Azure Active Directory and Role-Based Access Control (RBAC) for access
management.

Data Encryption:
AWS:
Utilize AWS Key Management Service (KMS) for encryption of data at rest and in
transit.

GCP:

Implement Google Cloud Key Management Service (KMS) for encryption of sensitive
data.

Azure:

Use Azure Key Vault for managing keys and secrets, ensuring data encryption.

Network Security:
AWS:

Implement AWS Virtual Private Cloud (VPC) with security groups and network ACLs.

GCP:

Utilize Google Cloud VPC with firewall rules for network security.

Azure:

Implement Azure Virtual Network with Network Security Groups (NSGs) for
network security.

Logging and Monitoring:

AWS:

Utilize AWS CloudTrail for logging and AWS CloudWatch for real-time monitoring.

GCP:

Implement Stackdriver Logging and Monitoring for comprehensive monitoring and

logging.

Azure:

Use Azure Monitor and Azure Security Center for logging and monitoring security
events.

Incident Response Planning:

AWS:
Develop an incident response plan using AWS Incident Response whitepapers.

GCP:

Create an incident response plan based on Google Cloud's incident response best
practices.

Azure:
Develop an incident response plan following Azure Security Incident Response Guide.

Learning Outcome:

Proficiency in implementing cloud security best practices for SaaS applications.

Understanding of IAM, data encryption, network security, logging, monitoring, and
incident response planning

Evaluation:

MCQ Questions:

Assess understanding of cloud security concepts and services.

Live Session:

Demonstrate the implementation of security best practices for the SaaS collaboration
platform.

Feedback:

Evaluate the effectiveness of security measures in ensuring data protection,

access control, and incident response.

Use Case 20: Cloud Service Monitoring and Alerts

Objective:

Implement cloud service monitoring and alerts to ensure proactive detection of

performance issues and rapid response to potential incidents using services from
AWS, GCP, or Azure.
Business Context:

Consider an e-commerce application that relies on various cloud services. The goal
is to set up robust monitoring and alerting systems to detect anomalies, ensure
optimal performance, and respond promptly to potential service disruptions.

Tasks:
Performance Metrics Monitoring:
AWS:

Utilize Amazon CloudWatch to monitor key performance metrics such as CPU

utilization, memory usage, and request latency.

GCP:

Implement Stackdriver Monitoring to track performance metrics and receive alerts

based on defined thresholds.

Azure:

Use Azure Monitor to collect and analyze performance data, setting up alerts for
critical metrics.

Log Monitoring:
AWS:

Set up Amazon CloudWatch Logs for centralized log monitoring, analyzing logs for
errors and exceptions.

GCP:

Utilize Stackdriver Logging to aggregate and analyze logs from various cloud services.

Azure:
Implement Azure Monitor Logs for collecting and analyzing log data across the
Azure environment.
Incident Alerts:
AWS:

Configure CloudWatch Alarms to send alerts when specific thresholds are breached,
indicating potential incidents.

GCP:

Set up alerting policies in Stackdriver to notify relevant teams when predefined

conditions are met.

Azure:

Use Azure Monitor Alerts to send notifications when specific conditions in the
application or infrastructure are met.

Auto-Scaling Alerts:
AWS:

Set up alerts in CloudWatch to trigger when auto-scaling events occur, ensuring

visibility into dynamic resource adjustments.

GCP:

Configure alerts in Stackdriver to notify when instances are automatically scaled

up or down.

Azure:

Use Azure Monitor to set up alerts for auto-scaling events, providing insights into
resource scaling activities.

Integration with Communication Channels:

AWS:

Integrate CloudWatch Alarms with Amazon SNS to send alert notifications via email,
SMS, or other channels.

GCP:
Configure Stackdriver Alerts to send notifications via email, SMS, or other
communication channels.

Azure:
Utilize Azure Monitor Alerts to send notifications through various channels, such as
email or Azure Logic Apps.

Learning Outcome:

Proficiency in implementing cloud service monitoring and alerting systems.

Understanding of performance metrics monitoring, log monitoring, incident alerts,

auto- scaling alerts, and integration with communication channels.

Evaluation:
MCQ Questions:

Assess understanding of cloud service monitoring and alerting concepts and services.

Live Session:

Demonstrate the implementation of monitoring and alerting for the e-commerce

application.

Feedback:

Evaluate the effectiveness of the monitoring and alerting systems in detecting and
responding to potential incidents.

Student Assessment Plan:

Each of the above-mentioned test projects will be divided into tasks by the
training partner for each specific institution. Such tasks will be jointly
evaluated by the faculty and the training partner and the following weightage
is to be followed.

● 70% weightage to the external practical assessment.

● 30% weightage to the internal assessment.
Final Test Project/External Assessment Plan:

The Final Test Project will be chosen from the list given above, jointly by the
college faculty and the Training Partner. The Final Test Project will be assessed on
the following tasks, for 70%

Details Marks

Task: 1 20

Task: 2 20

Task: 3 20

Task: 4 20
Task: 5 20