A VPC (Virtual Private Cloud) is a private, logically isolated network that you create inside a public cloud provider. You choose its IP address range, divide it into subnets, and control routing and traffic with route tables, gateways and firewall rules.
Why it matters
A VPC decides which of your servers are reachable from the internet and which stay private. A common design puts load balancers in public subnets and application servers and databases in private subnets that have no direct inbound internet route. Getting this layout right limits the blast radius of a compromise and is the base for private connections to offices or other networks.
Example
VPC 10.0.0.0/16
public subnet 10.0.1.0/24 -> route to internet gateway
private subnet 10.0.2.0/24 -> outbound via NAT gateway only
A web server in the private subnet can download updates through the NAT gateway, but nobody on the internet can open a connection to it directly.
Common mistakes
- Choosing an address range that overlaps an office or another VPC, which blocks peering and VPN links later.
- Making everything a public subnet for convenience.
- Using subnets that are too small and running out of addresses.
- Forgetting that NAT gateways and cross-zone traffic can add data transfer charges.
Related
Get notified when this term updates
Plus occasional practical tips on uptime and monitoring, nothing else. Unsubscribe anytime.
यह पेज सामान्य जानकारी है, जिसे हमारी संपादकीय टीम ने लिखा है और दस्तावेज़ीकरण बदलने पर अपडेट किया जाता है। सर्वर और प्रदाता अलग-अलग होते हैं, इसलिए बदलाव पहले सुरक्षित तरीके से जाँचें। देखें: संपादकीय नीति और अस्वीकरण.