You can use this document to learn about virtual private cloud (VPC) at StackPath.
What is a virtual private cloud (VPC)?
A VPC is a networking functionality that allows you to create isolated virtual networks from a workload.
A VPC gives you the ability to control your virtual network configurations, which includes a selection of IP address ranges, subnets, route table configurations, and network interfaces.
What are the main components of a VPC?
StackPath VPC comprises of the following components:
Network policies allow you to create multiple inbound and outbound security rules to filter traffic to and from resources by source and destination IP address, port, and protocol at the instance or network resource level.
|VPC networks are the fundamental building block for private networks.
|A network interface is a logical networking component of a VPC, which allows you to create and configure interfaces to connect VPCs and workloads in your account.
|Routing allows you to create and specify traffic routes from one instance to another within the same network.
|Subnets are a segment of a VPC’s IP address range where you can place groups of isolated resources.
|Labels allow you to add descriptive metadata to network components, such as dev, stage, prod.
Why should I use a VPC?
A VPC provides greater control over a virtual machine's network. Additionally, a VPC provides increased security because you can define a gateway virtual machine to handle inbound traffic, as well as internal virtual machines that cannot send or receive internal traffic.
How do I get started with a VPC?
Every workload is automatically provisioned with a default VPC; however, you can create additional VPC networks for a specified workload.
To learn more, see Create and Manage a VPC Network.
What charges are associated with VPC functionality?
There is no charge to use a VPC; however, standard charges are applicable for compute resources, such as virtual machines and containers. To learn more about charges, see Virtual Machines and Containers.
You can create an unlimited number of virtual networks. Similarly, VPC ingress routing is available in all regions at no additional cost. You can route traffic between 2 VPCs using interfaces. Support can enable additional public IP addresses at request, which carries a nominal charge ($0.005/IP/HR).