CCAD Self-Service in Cloud Models
CCAD Self-Service in Cloud Models
• Essential Characteristics
• Deployment Models
• Public, Private, Hybrid And Community Models
• Service models
• Cloud Reference Architecture
• Cloud Platforms Reference Architecture
Section 1: Essential Characteristics
Chapter 2: Cloud Characteristics and Models
Cloud computing essential characteristics
4
1.1-On demand self-service
5
1.2-Broad network access
• Cloud computing resources are available over the network and can be
accessed by diverse customer platforms:
• High broadband communication link—such as the internet, or in the case of a
private clouds it could be a local area network (LAN).
• Via standard mechanisms that promote use by heterogeneous thin or thick
client platforms (e.g., mobile phones, tablets, laptops, and workstations).
• Network bandwidth and latency are very important aspects of cloud
computing and broad network access, because they relate to the
quality of service (QoS) on the network. This is particularly important
for serving time sensitive applications.
6
1.3-Multi-tenancy and resource pooling
7
What is Multi-tenancy?
• Multitenancy refers to the ability of services to be offered to multiple user
entities (tenants) in a way so that each tenant operates as logically isolated,
while, in fact, using physically shared resources.
• Customizations made for one tenant are contained within metadata e.g. Cascading
Style Sheets for UI branding
• Each tenant runs the same application code
• Consumer applications are usually excluded from discussions of
multitenancy .
8
Multi-tenancy through shared middleware
• Hardware, OS and Application server layers are shared, to varying degrees,
across users. Data Layer comprises Shared Databases with either shared or
separate tables.
9
1.4-Rapid elasticity
10
1.5-Measured service
11
AWS pricing model
Three fundamental drivers of cost with AWS
Pay for what you use Pay less when you reserve Pay less when you use
more and as AWS grows
13
Pay for what you use
Pay only for the services that you consume, with no large
upfront expenses.
On premises AWS
14
Pay less when you reserve
Invest in Reserved
Instances (RIs):
• Save up to 75 percent
• Options: EC2
• All Upfront Reserved instance
Instance (AURI) largest
discount
• Partial Upfront Reserved On NURI PURI AURI
Instance (PURI) lower Demand
discounts
• No Upfront Payments
Reserved Instance (NURI)
smaller discount
15
Pay less by using more
16
Services with no charge
Amazon VPC
Elastic Beanstalk**
Auto Scaling**
AWS CloudFormation**
17
Section 2: Deployment Models
Chapter 2: Cloud Characteristics and Models
Cloud computing deployment models
19
Section 3:Public, Private, Hybrid And Community
Models
Chapter 2: Cloud Characteristics and Models
Public Cloud (1/2)
21
Public Cloud (2/2)
22
Private Cloud (1/2)
• Private cloud are neologisms that some vendors have recently used to
describe offerings that emulate cloud computing on private networks.
• These (typically virtualization automation) products claim to "deliver some
benefits of cloud computing without the pitfalls", capitalizing on data
security, corporate governance, and reliability concerns.
• Private clouds are where activities and functions are provided "as a
service" over a company's intranet.
• Private clouds are built by an organization for its own users, and everything is
delivered within the organization's firewall (instead of the Internet).
• The private cloud owner does not share resources with any other companies,
so multitenancy is not an issue. Therefore, private clouds are also called
"internal clouds".
23
Private Cloud (2/2)
24
Hybrid Cloud (1/2)
26
Community Cloud
27
Virtual Private Cloud
28
Amazon VPC Amazon
VPC
29
Public vs. Private vs. Hybrid
• Public Cloud
• Service provider lets clients access the cloud via the Internet
• Made available to the general public or a wide industry group
• Private Cloud
• The cloud infrastructure is used solely by the organization that owns it
• May reside in-house or off premises
• Hybrid Cloud
• Composed of two or more clouds that remain unique entities but that can
interoperate using standard or proprietary protocols
30
Section 4: Service Models
Chapter 2: Cloud Characteristics and Models
Cloud service models
© 2022, Amazon Web Services, Inc. or its affiliates. All rights reserved. 32
Software as a service (SaaS)
33
Platform as a service (PaaS)
34
Infrastructure as a service (IaaS)
35
SaaS vs. PaaS vs. IaaS
36
Cloud service models
37
SaaS vs. PaaS vs. IaaS Layers of Cloud
Computing
38
SaaS vs. PaaS vs. IaaS Layers Tradeoffs
39
Service models of cloud service platforms
40
Similarities between AWS and traditional IT
Security
Security groups
Firewalls ACLs Administrators Network ACLs IAM
Networking
Router Network pipeline Switch Elastic Load Balancing Amazon VPC
On-premises
Compute
servers Amazon EC2
AMI
instances
41
Section 5: Cloud Reference Architecture
Chapter 2: Cloud Characteristics and Models
Cloud Computing Reference Architecture
(CCRA) (1/2)
• CCRA is a generic high-level conceptual model that is a powerful
tool for discussing the requirements, structures, and operations of
cloud computing.
• The model is not tied to any specific vendor products, services, or reference
implementation, nor does it define prescriptive solutions that inhibit
innovation.
• It defines a set of actors, activities, and functions that can be used in the
process of developing cloud computing architectures, and relates to a
companion cloud computing taxonomy.
• It contains a set of views and descriptions that are the basis for discussing the
characteristics, uses and standards for cloud computing.
• The NIST CCRA focuses on the requirements of what cloud service
provides, not on a design that defines a solution and its
implementation [2].
• It is intended to facilitate the understanding of the operational intricacies in
cloud computing.
43
Cloud Computing Reference Architecture
(CCRA) (1/2)
• The reference architecture does not represent the system architecture
of a specific cloud computing system;
• instead, it is a tool for describing, discussing, and developing the system-
specific architecture using a common framework of reference.
• The design of the CCRA serves the objectives to:
• illustrate and understand various cloud services in the context of an overall
cloud computing conceptual model;
• provide technical references to USG agencies and other consumers to
understand, discuss, categorize, and compare cloud services; and
• communicate and analyze security, interoperability, and portability candidate
standards and reference implementations.
• The NIST CCRA defines five major actors: cloud consumer, cloud
provider, cloud auditor, cloud broker, and cloud carrier.
• Each actor is an entity (a person or an organization) that participates in a
transaction or process and/or performs tasks in cloud computing.
44
Actors in Cloud Computing
Actor Definition
Cloud Consumer Person or organization that maintains a business relationship with,
and uses service from, Cloud Providers.
45
Interactions between the Actors in Cloud
Computing
46
1-Cloud Consumer
47
Cloud Consumer and Cloud Provider
48
Example of Services Available to a Cloud
Consumer
49
2-Cloud Provider
50
2.1-Service deployment
• A cloud infrastructure may be operated in one of the following deployment
models:
• Public cloud
• Private cloud
• Community cloud, or
• Hybrid cloud.
51
2.2-Service orchestration
• Service orchestration refers to the arrangement, coordination, and
management of cloud infrastructure to provide different cloud services to
meet IT and business requirements.
• A three-layered framework is identified for a generalized cloud environment:
• Service layer
• Resource abstraction and control layer
• Physical resource layer
52
2.3-Cloud service management
• Cloud Service Management includes all of the service-related functions that
are necessary for the management and operation of those services required
by or proposed to cloud consumers.
• Cloud service management can be described from the perspective of business
support, provisioning and configuration, and from the perspective of
portability and interoperability requirements.
53
2.4-Security
• It is critical to recognize that security is cross-cutting that spans across all
layers of the reference model, ranges from physical security to application
security, and in general, shares the responsibility between cloud provider and
federal cloud consumer.
• For example, the protection of the physical resource layer requires physical security
that denies unauthorized access to the building, facility, resource, or stored
information.
• Cloud providers should ensure that the facility hosting cloud services is
secure and that their staff has proper background checks.
• When data or application is moved to a cloud, it is important to ensure that
the cloud offering satisfies the security requirements and enforces the
compliance rules.
• An independent audit should be conducted to verify the compliance with
regulation or security policy.
54
2.5-Privacy
• Cloud providers should protect the assured, proper, and consistent collection,
processing, communication, use and disposition of personal information (PI)
and personally identifiable information (PII) in the cloud.
• According to the CIO Council, one of the federal government’s key business
imperatives is to ensure the privacy of the collected personally identifiable
information.
• PII is the information that can be used to distinguish or trace an individual’s identity,
such as their name, social security number, biometric records, etc., alone, or when
combined with other personal or identifying information that is linked or linkable to a
specific individual, such as date and place of birth, mother’s maiden name, etc.
• Though cloud computing provides a flexible solution for shared resources,
software and information, it also poses additional privacy challenges to
consumers using the clouds.
55
3-Cloud Auditor
56
4-Cloud Broker (1/2)
• Service Intermediation
• A cloud broker enhances a given service by improving some specific
capability and provides the value-added service to cloud consumers.
• Service Aggregation
• A cloud broker combines and integrates multiple services into one or more
new services. The broker will provide data integration and ensure the secure
data movement between cloud consumer and multiple cloud providers.
• Service Arbitrage
• Service arbitrage is similar to service aggregation, with the difference in that
the services being aggregated aren’t fixed. Service arbitrage allows flexible
and opportunistic choices for the broker. For example, the cloud broker can
use a credit-scoring service and select the best score from multiple scoring
agencies.
58
3-Cloud Carrier
60
Activity Work in Group: Discuss CCRA
Subtopic Group
Overview (purpose & benefits) Danish Attractive slides & details
explanation
Cloud Consumer Hayati Good comparison table with
examples
Cloud Provider Chong Well organise contents
Sarween Thorough contents and well
Cloud Auditor
researched
Cloud Broker Isaac Helpful illustration and example
Cloud Carrier Izrin Good effort in explanation that
include the process and sub-criteria
61
Section 6: Cloud Platform Reference Architecture
Chapter 2: Cloud Characteristics and Models
Cloud Platform Reference Architectures (2/2)
64
Example: IBM Cloud Computing Reference Architecture (1/2)
65
Example: IBM Cloud Computing Reference Architecture (2/2)
66
Well Architected Framework
68
The AWS Well-Architected Tool
• Helps you review the state of your workloads and compares them to the latest
AWS architectural best practices
• Gives you access to knowledge and best practices used by AWS architects,
whenever you need it
• Delivers an action plan with step-by-step guidance on how to build better
workloads for the cloud
• Provides a consistent process for you to review and measure your cloud
architectures
69
Takeaway