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, and 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 and those 10 other customers I don't have any information on.
I don't have any say on the actual security of that server, so 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 these services exclusively.
There is no commingling 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 are 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, and usually that industry is going to have set security configurations and requirements.
Let's say I'm a healthcare provider and I collect information on my patients That's considered to be both P I and P. H. I 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 they give the assurance of meeting the regulations and the requirements with H. I. P. A.
I don't have exclusive use. There's still multi tendency, 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 bursts and 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, that I may borrow resources,
sometimes it's called cloud bursting, and we get that in a hybrid environment,
wrapping up the cloud, the big things to understand about cloud computing. First of all, no a cloud computing is and why we care. Our driver saving money, ubiquitous activists, 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, so 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.
And then we set community cloud right in the middle, and then hybrid takes private cloud and then for bursts, we use resources from the public cloud.