Virtual Private Cloud
{'<entity_0>': 'Virtual Private Cloud', '<entity_1>': 'Google Cloud Platform', '<entity_2>': 'Amazon Web Services', '<entity_3>': 'IBM Cloud', '<entity_4>': 'Google', '<entity_5>': 'cloud computing', '<entity_6>': 'VPC'}
[['Virtual Private Cloud', 'instance of', 'cloud computing'], ['Virtual Private Cloud', 'part of', 'Google Cloud Platform'], ['Virtual Private Cloud', 'part of', 'Amazon Web Services'], ['Virtual Private Cloud', 'part of', 'IBM Cloud'], ['Virtual Private Cloud', 'alternative', 'VPC'], ['Virtual Private Cloud', 'developer', 'Google'], ['Virtual Private Cloud', 'owned by', 'Google']]
A <entity_0> is an on-demand configurable pool of shared computing resources allocated within a public <entity_5> environment, providing a certain level of isolation between the different organizations (denoted as users hereafter) using the resources. The isolation between one <entity_6> user and all other users of the same <entity_5> (other <entity_6> users as well as other public <entity_5> users) is achieved normally through allocation of a private IP subnet and a virtual communication construct (such as a VLAN or a set of encrypted communication channels) per user. In a <entity_6>, the previously described mechanism, providing isolation within the <entity_5>, is accompanied with a VPN function (again, allocated per <entity_6> user) that secures, by means of authentication and encryption, the remote access of the organization to its <entity_6> resources. With the introduction of the described isolation levels, an organization using this service is in effect working on a 'virtually private' <entity_5> (that is, as if the <entity_5> infrastructure is not shared with other users), and hence the name <entity_6>. <entity_6> is most commonly used in the context of <entity_5> infrastructure as a service. In this context, the infrastructure provider, providing the underlying public <entity_5> infrastructure, and the provider realizing the <entity_6> service over this infrastructure, may be different vendors. <entity_2> launched Amazon <entity_0> on 26 August 2009, which allows the Amazon Elastic Compute Cloud service to be connected to legacy infrastructure over an IPsec virtual private network connection. <entity_3> launched <entity_3>™ <entity_6> on 4 June 2019, provides an ability to manage virtual machine-based compute, storage, and networking resources. Pricing for <entity_3>™ <entity_0> is applied separately for internet data transfer, virtual server instances, and block storage used within <entity_3> <entity_6>. <entity_1> resources can be provisioned, connected, and isolated in a <entity_0> across all GCP regions. VPCs on <entity_1> leverage the security of <entity_4>'s data centers.
['software', 'application programming interface', 'cloud computing', 'concept', 'service on internet']