WEBVTT

00:00.000 --> 00:01.305
>> In the previous section,

00:01.305 --> 00:03.120
we talked about the
various services that

00:03.120 --> 00:05.475
we might want from our
Cloud service provider.

00:05.475 --> 00:07.290
The next thing we have
to think about is

00:07.290 --> 00:09.645
how do we want our
deployment to work?

00:09.645 --> 00:11.430
When I say the deployment,

00:11.430 --> 00:13.830
we've got various deployment
models that are public,

00:13.830 --> 00:16.365
private, hybrid, and community.

00:16.365 --> 00:18.420
What this deals with
is who's going to

00:18.420 --> 00:21.165
share the hardware where
your data is stored?

00:21.165 --> 00:24.360
Of course, the cheapest is
going to be the public.

00:24.360 --> 00:27.765
We're going to use Amazon's
web services or whomever,

00:27.765 --> 00:30.165
and these services are
publicly available.

00:30.165 --> 00:32.805
This is where we have
multi-tenancy though.

00:32.805 --> 00:34.950
What this means is my data,

00:34.950 --> 00:36.765
my resources, my servers,

00:36.765 --> 00:38.370
everything is going
to be running in

00:38.370 --> 00:39.780
a virtualized environment on

00:39.780 --> 00:42.330
a server that might have
10 other customers.

00:42.330 --> 00:44.025
Those 10 other customers,

00:44.025 --> 00:46.055
I don't have any information on.

00:46.055 --> 00:48.500
I don't have any say on
the actual security of

00:48.500 --> 00:50.960
that server. That
might be a concern.

00:50.960 --> 00:53.465
This is not for
top-secret information.

00:53.465 --> 00:55.700
However, many
organizations choose

00:55.700 --> 00:58.540
this option because
it is the cheapest.

00:58.540 --> 01:00.565
In a private cloud however,

01:00.565 --> 01:02.570
you get a little bit more
control because you're

01:02.570 --> 01:04.130
the only organization that is

01:04.130 --> 01:06.575
accessing the
services exclusively.

01:06.575 --> 01:08.850
There is no co-mingling of data.

01:08.850 --> 01:10.740
There is no multi-tenancy.

01:10.740 --> 01:12.530
Essentially, what
you have is you have

01:12.530 --> 01:14.375
resources that are
available to you,

01:14.375 --> 01:16.445
but their access
across the Internet,

01:16.445 --> 01:17.630
and usually they're maintained

01:17.630 --> 01:19.310
by a Cloud service provider.

01:19.310 --> 01:20.990
We in our organization can

01:20.990 --> 01:22.760
maintain a private
cloud as well.

01:22.760 --> 01:26.000
For instance, the government's
Cloud services provider

01:26.000 --> 01:28.393
or the government's Cloud
is going to be managed

01:28.393 --> 01:30.950
>> by the Department of
Defense and those entities

01:30.950 --> 01:33.139
>> because of the greater
need for security.

01:33.139 --> 01:35.480
>> If I'm an organization
that's storing

01:35.480 --> 01:37.790
personally identifiable
information

01:37.790 --> 01:40.309
>> or personal and
financial information,

01:40.309 --> 01:43.770
>> probably the private cloud
is going to be best for me.

01:44.990 --> 01:48.425
Something in the middle is
called the Community Cloud.

01:48.425 --> 01:50.390
A community Cloud
service provider

01:50.390 --> 01:53.464
>> will be specializing
towards a specific industry.

01:53.464 --> 01:56.000
>> Usually that industry
is going to have set

01:56.000 --> 01:59.020
security configurations
and requirements.

01:59.020 --> 02:01.280
Let's say I'm a
health care provider

02:01.280 --> 02:02.690
and I collect information on

02:02.690 --> 02:06.605
my patients that's considered
to be both PII and PHI,

02:06.605 --> 02:08.975
personally identifiable
information,

02:08.975 --> 02:10.990
personal healthcare information.

02:10.990 --> 02:13.260
Both of those need
to be protected.

02:13.260 --> 02:15.170
I might want the cost
of a public cloud

02:15.170 --> 02:16.134
>> because it's cheap.

02:16.134 --> 02:17.740
>> But the privacy
of a private cloud,

02:17.740 --> 02:20.315
I'm going to look for
something in the middle.

02:20.315 --> 02:22.460
A community Cloud
service provider is

02:22.460 --> 02:25.082
going to provide services
in this instance

02:25.082 --> 02:26.764
>> to other health
care providers

02:26.764 --> 02:29.120
>> and to give the assurance
of meaning, the regulations,

02:29.120 --> 02:32.364
>> and the requirements
with HIPAA.

02:32.364 --> 02:34.305
>> I don't have exclusive use.

02:34.305 --> 02:35.945
There's still multi-tenancy,

02:35.945 --> 02:38.165
but I do have a higher
degree of security,

02:38.165 --> 02:40.975
which I'm going to need
for my environment.

02:40.975 --> 02:43.350
Then we also have a hybrid.

02:43.350 --> 02:45.229
Hybrid is one of
those situations

02:45.229 --> 02:46.670
where I have private
cloud access.

02:46.670 --> 02:47.795
But from time to time,

02:47.795 --> 02:49.490
like with  burst businesses,

02:49.490 --> 02:52.870
I may need to access resources
from the public cloud.

02:52.870 --> 02:54.800
I have the primary privacy of

02:54.800 --> 02:56.450
a private cloud
most of the time,

02:56.450 --> 02:58.190
but when there's an
increase in demand like

02:58.190 --> 02:59.930
the Christmas holidays
for instance,

02:59.930 --> 03:01.895
then I may borrow resources.

03:01.895 --> 03:04.055
Sometimes it's called
Cloud bursting.

03:04.055 --> 03:06.640
We get that in a
hybrid environment.

03:06.640 --> 03:08.545
Wrapping up the Cloud.

03:08.545 --> 03:09.980
The big things to
understand about

03:09.980 --> 03:11.840
Cloud computing first of all,

03:11.840 --> 03:14.570
know what Cloud computing
is and why we care.

03:14.570 --> 03:16.220
Our driver, saving money,

03:16.220 --> 03:17.660
ubiquitous [inaudible],

03:17.660 --> 03:20.660
strong network availability,
and resources.

03:20.660 --> 03:22.535
Then with our Cloud services,

03:22.535 --> 03:24.050
we have software as a service,

03:24.050 --> 03:25.580
we have platform as a service,

03:25.580 --> 03:27.620
we have infrastructure
as a service.

03:27.620 --> 03:29.030
We have shared responsibility

03:29.030 --> 03:30.589
>> across the service models.

03:30.589 --> 03:31.940
>> It's always
good to understand

03:31.940 --> 03:33.170
>> how we trade off flexibility

03:33.170 --> 03:35.619
>> for configuration
options and control.

03:35.619 --> 03:38.525
>> Last, we looked at
Cloud deployment models,

03:38.525 --> 03:41.285
which are going to consist
of public or private cloud.

03:41.285 --> 03:43.700
Then we set community
Cloud right in the middle.

03:43.700 --> 03:45.605
Then hybrid takes private cloud.

03:45.605 --> 03:49.530
Then for burst, we use resources
from the public cloud.