In #explainlikeimfive terms, I'd say it's a bit like having a vacation timeshare. On one hand, it's meant to have all the amenities and the feeling of your own home, but on the other hand, you save money by sharing the cost with the other timeshare owners.
With vpc, it's a similar idea: You can access shared cloud infrastructure in a way that feels like part of your organization's private network.
If it works well, it means you won't need to manage your own data centre: You can more easily scale up/down what you're using based on your real-time computing needs. However, you still get the security and isolation that would be expected from a self-managed data centre.
The term "virtual" comes into play because the physical infrastructure you're using is shared with other customers of the cloud provider, but it's isolated in such a way that this sharing is not visible to the parties involved.
Many thanks for your reply ! :)) But I have difficulty in understanding how is this different from having a public cloud ? If we choose to have our instances in the public cloud, they come with their own isolation from other different tenants. Our data , instances are secured from the other customers who share resources by the same cloud provider. I will read up on the link which you have provided ! :D Thanks again.
I believe the distinction is simply that with vpc, you can customize the network (ip address range, subnets etc). Again, it is meant to feel as though you have your own network infrastructure in house or hosted privately at a data centre. You can even separate out publicly-facing servers, just as you would if this was your own IT infrastructure. I think the amazon vpc page may be helpful for reference: aws.amazon.com/vpc/.
In #explainlikeimfive terms, I'd say it's a bit like having a vacation timeshare. On one hand, it's meant to have all the amenities and the feeling of your own home, but on the other hand, you save money by sharing the cost with the other timeshare owners.
With vpc, it's a similar idea: You can access shared cloud infrastructure in a way that feels like part of your organization's private network.
If it works well, it means you won't need to manage your own data centre: You can more easily scale up/down what you're using based on your real-time computing needs. However, you still get the security and isolation that would be expected from a self-managed data centre.
The term "virtual" comes into play because the physical infrastructure you're using is shared with other customers of the cloud provider, but it's isolated in such a way that this sharing is not visible to the parties involved.
This overview of the different kinds of private clouds might be helpful: vmware.com/topics/glossary/content...
Many thanks for your reply ! :)) But I have difficulty in understanding how is this different from having a public cloud ? If we choose to have our instances in the public cloud, they come with their own isolation from other different tenants. Our data , instances are secured from the other customers who share resources by the same cloud provider. I will read up on the link which you have provided ! :D Thanks again.
I believe the distinction is simply that with vpc, you can customize the network (ip address range, subnets etc). Again, it is meant to feel as though you have your own network infrastructure in house or hosted privately at a data centre. You can even separate out publicly-facing servers, just as you would if this was your own IT infrastructure. I think the amazon vpc page may be helpful for reference: aws.amazon.com/vpc/.
Great ! I will go through the reference. Thank you :))