All right, introduction to cloud computing.
Yes. All right, so the cloud, what is it?
It's somebody else's computer that you rent time on.
They pay for the hardware, they pay for
the software, you rent space, more or less.
So it is not unlike an on premise solution, its structure definitely is,
but its behavior and its security vulnerabilities are pretty much identical
to an on premise or hosted solution, but it also has its own range of
vulnerabilities based on the infrastructure.
The identity access management systems,
the buckets, storage services, and that thing.
Introduction to cloud computing.
Cloud computing gives us benefits of on
demand self service, distributed storage, rapid elasticity,
broad network to access, resource pooling, virtualization technology.
It allows us to accommodate larger workload.
You're still going to pay, again, more for
that elasticity piece, but it's flexible, it's malleable.
Different types of cloud computing services.
The big three are infrastructures of
service, platform as a service, software as a service.
Those are the three amigas of cloud computing.
Infrast structures of service, virtual machines, and other abstract and
hardware operating systems controlled through a service API.
This is a rough analogy.
I'm taking some liberties with it.
But think of it like renting a network on the cloud.
Platform as a service
offers development tools, configuration management, deployment
platforms that can be used by subscribers to develop custom applications.
Think of renting a host in the cloud.
Now, again, I'm taking some liberties with
this, but think of network host or application, software as a service.
Software as a service, I am basically leasing an application in the cloud.
Software subscribers on demand over the internet.
Example, web based app office applications
like Google Docs, calendar, Salesforce, or FreshBooks.
Then end customers.
Again, you've got SIS admins,
infrastructure as a service, developers, platform as a service.
Hit end customers, software as a service,
end customers as well, identity as a service.
Offers identity and access management
services, including single sign on, multifactor authentication, etc.
Identity as a service or identity and access management, you're actually going
to be doing a couple of labs on that with IAM for AWS, but allows you to create and
manage your users through a third party provider.
Security as a service.
There's a lot of as a service variants coming out these days.
Provides pen testing, authentication, intrusion detection, anti malware,
security incident management services as a service.
Function as a service, platform for developing, running, and
managing application functionalities for microservices.
Container as a Service offers
virtualization of container engines, and then anything else as a service, XAAS.
Anything as a service of the digital based
on the user's demand and insert your initial here.
The shared responsibility model.
Customer versus cloud service provider shared responsibility.
An on premise solution.
The customer is responsible for...
It wouldn't really be a customer because there's no cloud use there, but an on
premise solution, you're responsible for administering everything.
In infrastructure as a service, you're responsible for much less.
Part of that is managed by the provider.
In platform as a service, less than that.
And in software as a service, even less than that.
Depending on the model you're using, your
responsibilities for security or administration are going to vary.
All right, cloud deployment models.
Okay, the public cloud versus the private cloud.
Public clouds services are rendered over a network that is open for public use.
So that's available to the public, publicly exposed resources, that thing.
Private cloud operated for a single
organization only, whether that's hosted or local.
So your cloud does not have to be an Amazon or Azure.
It's just any other third party provider.
And you can actually maintain your own
private cloud even locally, which would define the definition.
But you could definitely set up the same
virtualized infrastructure and own the facility.
My cloud deployment models.
A community cloud
is shared between several organizations from a specific community with common
concerns, security, compliance, jurisdiction, etc.
And a hybrid cloud is a combination of two or more clouds.
Any flavor, the remaining unique entities,
but are bound together, offering the benefits of multiple deployment models.
The multi cloud, which is a newer term.
You don't really see this normally in the list of the four different cloud types.
Dynamic, heterogeneous environment that
combines workloads across multiple cloud vendors, managed via one proprietary
interface to achieve long term business goals.
So maybe something that uses Amazon Azure and Google or even your own private cloud.
All right, NIST, the National Institute of
Standardization of Technologies, has a cloud computing reference guide.
Their architecture defines five major
actors or players in the cloud scenario or cloud concept.
Cloud consumer, cloud provider,
the carrier, which is an intermediary for connectivity between consumers and
providers, the cloud auditor, making independent assessments of cloud service
controls, and the cloud broker, an entity that manages cloud services in
the form terms of use, performance, delivery.
Now, be on the lookout for exam questions that ask you to recite some of these
definitions or ask you to demonstrate a working knowledge of these definitions.
Here we go.
Fog computing.
Fog versus Edge.
A fog computing environment is a distributed and independent digital
environment which applications and data storage are positioned between data
sources, device generating data, and a cloud service.
It acts as an intermediary between the hardware and the servers.
Also called an intelligent gateway.
It's used for enhanced data processing,
storage, and analysis in a quick and efficient manner.
The Edge computing concept is distributed, decentralized computing
model, which data processing is performed close to the Edge devices.
It helps building automation systems,
provide fast processing, and enables efficient real time applications.
Both of these are referring to distributed
environments and where the data is actually processed, whether it's
at the on individual devices or in a more centralized location.