Creating a Virtual Network
What you'll learn: How to set up your first isolated network in the cloud by defining its address space and basic configuration.
What Does "Creating" Mean Here?
Creating a Virtual Network (VPC in AWS, VNet in Azure/GCP) is like claiming a plot of land in the cloud where all your resources will live. You're not building anything physical—you're defining logical boundaries and rules that the cloud provider enforces for you.
The Creation Process
When you create a virtual network, you specify three essential things:
- Name and Region: What to call it and where it physically exists (e.g.,
us-east-1orwesteurope) - Address Space (CIDR block): The range of private IP addresses available in this network—typically using RFC 1918 ranges like
10.0.0.0/16or172.16.0.0/12 - Basic Options: Tags for organization, whether to enable features like DNS resolution, and flow logs for monitoring
Why Address Space Matters
Think of your CIDR block as the total number of addresses available. Choosing 10.0.0.0/16 gives you ~65,000 addresses. Too small and you'll run out of IPs as you grow; too large wastes planning space. Most beginners start with /16 networks—plenty of room without being overwhelming.
What Happens After Creation?
The network exists but is empty—no subnets, no VMs, nothing. It's a container waiting to be subdivided into subnets (covered later). You can create multiple virtual networks in different regions, and they're completely isolated from each other by default.
Key Takeaway: Creating a virtual network establishes an isolated address space in a specific region—think of it as drawing property lines before building anything inside them.