>> In the previous section,
we talked about the various services that
we might want from our Cloud service provider.
The next thing we have to think about is
how do we want our deployment to work?
When I say the deployment,
we've got various deployment models that are public,
private, hybrid, and community.
What this deals with is who's going to
share the hardware where your data is stored?
Of course, the cheapest is going to be the public.
We're going to use Amazon's web services or whomever,
and these services are publicly available.
This is where we have multi-tenancy though.
What this means is my data,
my resources, my servers,
everything is going to be running in
a virtualized environment on
a server that might have 10 other customers.
Those 10 other customers,
I don't have any information on.
I don't have any say on the actual security of
that server. That might be a concern.
This is not for top-secret information.
However, many organizations choose
this option because it is the cheapest.
In a private cloud however,
you get a little bit more control because you're
the only organization that is
accessing the services exclusively.
There is no co-mingling of data.
There is no multi-tenancy.
Essentially, what you have is you have
resources that are available to you,
but their access across the Internet,
and usually they're maintained
by a Cloud service provider.
We in our organization can
maintain a private cloud as well.
For instance, the government's Cloud services provider
or the government's Cloud is going to be managed
>> by the Department of Defense and those entities
>> because of the greater need for security.
>> If I'm an organization that's storing
personally identifiable information
>> or personal and financial information,
>> probably the private cloud is going to be best for me.
Something in the middle is called the Community Cloud.
A community Cloud service provider
>> will be specializing towards a specific industry.
>> Usually that industry is going to have set
security configurations and requirements.
Let's say I'm a health care provider
and I collect information on
my patients that's considered to be both PII and PHI,
personally identifiable information,
personal healthcare information.
Both of those need to be protected.
I might want the cost of a public cloud
>> because it's cheap.
>> But the privacy of a private cloud,
I'm going to look for something in the middle.
A community Cloud service provider is
going to provide services in this instance
>> to other health care providers
>> and to give the assurance of meaning, the regulations,
>> and the requirements with HIPAA.
>> I don't have exclusive use.
There's still multi-tenancy,
but I do have a higher degree of security,
which I'm going to need for my environment.
Then we also have a hybrid.
Hybrid is one of those situations
where I have private cloud access.
But from time to time,
like with burst businesses,
I may need to access resources from the public cloud.
I have the primary privacy of
a private cloud most of the time,
but when there's an increase in demand like
the Christmas holidays for instance,
then I may borrow resources.
Sometimes it's called Cloud bursting.
We get that in a hybrid environment.
Wrapping up the Cloud.
The big things to understand about
Cloud computing first of all,
know what Cloud computing is and why we care.
Our driver, saving money,
ubiquitous [inaudible],
strong network availability, and resources.
Then with our Cloud services,
we have software as a service,
we have platform as a service,
we have infrastructure as a service.
We have shared responsibility
>> across the service models.
>> It's always good to understand
>> how we trade off flexibility
>> for configuration options and control.
>> Last, we looked at Cloud deployment models,
which are going to consist of public or private cloud.
Then we set community Cloud right in the middle.
Then hybrid takes private cloud.
Then for burst, we use resources from the public cloud.