🏢 Traditional Corporate Datacenter (Analogy)
- Users access applications (like www.google.com) hosted in the datacenter via the internet.
- Direct server access is blocked (Web/App/DB servers stay private).
- Network/System Admins can access servers using the corporate private network from different office locations.
👉 In Google Cloud, the equivalent of this private corporate network is VPC (Virtual Private Cloud).
🔑 Key Features of Google Cloud VPC
- Private Network in Google Cloud.
- Global resource → not tied to a specific region or zone.
- VPC resources like routes & firewalls are also global.
- Isolation & Security → You can logically isolate networks and control who can access.
- Resources (VMs, databases, etc.) created inside VPC are protected from unauthorized access.
🌍 Google Cloud VPC – Subnets
- Subnets are regional resources (not global).
- A subnet can span multiple zones in one region (⚡ different from AWS where subnets are tied to a single zone).
- Each subnet has its own IP range (e.g., 10.128.0.0/20).
- A VPC needs at least one subnet before you can deploy resources.
⚙️ Google Cloud VPC – Modes
1️⃣ Auto-Mode VPC
- Google automatically creates one subnet per region.
- Every new project comes with a default auto-mode VPC.
- Subnets are predefined with IP ranges.
- As new regions are launched, new subnets get added automatically.
- Supports IPv4 only.
👉 Good for testing & learning, not recommended for production.
2️⃣ Custom-Mode VPC
- You manually create subnets.
- You define your own IP ranges.
- Supports IPv4 or dual-stack (IPv4 + IPv6).
- Recommended for all workloads (from Dev → Prod).
Google Cloud VPC - Auto vs Custom modes
Top comments (0)