Loading...
Your own isolated network inside a public cloud, with private addresses and controlled doors.
Quick Definition
A virtual private cloud (VPC) is an isolated, logically segmented network within a public cloud where resources are launched. It gives organizations control over IP ranges, subnets, routing, and security, providing private, secure networking on shared cloud infrastructure.
A Virtual Private Cloud, or VPC, is a logically isolated network you define inside a public cloud: your own address space, subnets, routing rules, and firewalls, invisible to other customers sharing the same physical infrastructure. It is how the public cloud delivers private-network behavior.
VPCs organize both security and traffic. Subnets separate public-facing services from internal ones, security rules control which doors are open, and the network design quietly determines costs, because in the cloud, data movement is billed. Traffic crossing availability zones, regions, or leaving the provider entirely each carries a different price.
Example. A team places a database and its application servers in different availability zones without thinking about it. The chatty traffic between them generates thousands of dollars in monthly cross-zone charges that same-zone placement would have avoided.
Good VPC design keeps heavy traffic local, routes external transfers deliberately, and isolates environments cleanly. Egress costs and data transfer charges are where network architecture meets the invoice. The cloud security guide covers the protective side of VPC design.
The VPC is typically free; its accessories, NAT gateways, VPN connections, and cross-boundary traffic, are what appear on the bill.
Commonly one per environment or business domain, connected deliberately. Sprawling dozens of ad hoc VPCs multiplies both risk and connectivity cost.
Because data movement is metered. Architecture that keeps chatty services close together avoids cross-zone and cross-region charges entirely.