AWS Virtual Private Cloud

AKA: Amazon Virtual Private Cloud Amazon VPC Service.
Context:
- Website: https://aws.amazon.com/vpc/.
- It can (typically) have:
  - a VPC ID (e.g. vpc-e10d4185).
  - a Network ACL (e.g. acl-6fc49b0b).
  - a VPC CIDR (e.g. 172.30.0.0/16).
  - a Route table (e.g. rtb-53676e37).
Example(s):
- It can be inspect at https://console.aws.amazon.com/vpc/home?region=us-east-1#vpcs:
- AWS VCP features,
- …
Counter-Example(s):
- AWS DynamoDB Service,
- AWS Lambda Service.
See: Amazon Web Services (AWS), Virtual Private Server, AWS EC2, AWS S3.

References

(Wikipedia, 2022) ⇒ https://en.wikipedia.org/wiki/Amazon_Virtual_Private_Cloud Retrieved:2022-7-17.
- Amazon Virtual Private Cloud (VPC) is a commercial cloud computing service that provides users a virtual private cloud, by "provision[ing] a logically isolated section of Amazon Web Services (AWS) Cloud".^[1] Enterprise customers are able to access the Amazon Elastic Compute Cloud (EC2) over an IPsec based virtual private network. Unlike traditional EC2 instances which are allocated internal and external IP numbers by Amazon, the customer can assign IP numbers of their choosing from one or more subnets. By giving the user the option of selecting which AWS resources are public facing and which are not, VPC provides much more granular control over security. For Amazon it is "an endorsement of the hybrid approach, but it's also meant to combat the growing interest in private clouds".

(AWS, 2015) ⇒ http://aws.amazon.com/vpc/
- Amazon Virtual Private Cloud (Amazon VPC) lets you provision a logically isolated section of the Amazon Web Services (AWS) Cloud where you can launch AWS resources in a virtual network that you define. You have complete control over your virtual networking environment, including selection of your own IP address range, creation of subnets, and configuration of route tables and network gateways.
  You can easily customize the network configuration for your Amazon Virtual Private Cloud. For example, you can create a public-facing subnet for your webservers that has access to the Internet, and place your backend systems such as databases or application servers in a private-facing subnet with no Internet access. You can leverage multiple layers of security, including security groups and network access control lists, to help control access to Amazon EC2 instances in each subnet.
  Additionally, you can create a Hardware Virtual Private Network (VPN) connection between your corporate datacenter and your VPC and leverage the AWS cloud as an extension of your corporate datacenter.