Multi-cloud Series Blog 1: Azure VNET vs AWS VPC vs GCP VPC

Dear readers/subscribers,

I started my multi-cloud journey after completing Azure and AWS certification before started my preparation for Google Cloud Professional architect exam. Soon I learned about differences and the wayt these 3 cloud providers have constructed their cloud services. To clear the air and make it easy to understand I decided to start a multi-cloud blog series. In this article we’ll compare Azure VNET vs AWS VPC vs GCP VPC.

Azure Vnet or AWS VPC or GCP VPC is a logical isolated network construct which enables you to launch cloud resources into a virtual network. You can think of this virtual network as your traditional network that you’d build in your on-premise data center. In nut shell it’s a Virtual Private datacenter in cloud. Let’s understand the difference among these three network constructs.

Features

Cloud Providers

Azure VNET AWS VPC GCP VPC
VNET/VPC Scope Region Region Global (spans across region). They are not associated with any particular region or zone.
Subnet Scope Region (spans across AZs) Availability Zone Region (spans across AZs)
VNET/VPC CIDR Need to define CIDR block for VNET Need to define CIDR block for VPC No CIDR block is defined for VPC. VPC is just a container for subnets.
VNET/VPC CIDR Expansion Yes can be expanded by adding additional CIDR blocks to VNET Yes can be expanded by adding additional CIDR blocks to VPC Yes can be expanded by adding new contiguous or non-contiguous subnets
Subnet CIDR Expansion No it can’t be expanded (except when it’s empty) No it can’t be expanded. Yes can be expanded but not shrunk.
Subnet CIDR Block Derived from VNET CIDR block Derived from VPC CIDR block Independent and can be any non-contiguous CIDR block assigned to Subnets
VNET/VPC Types Only one type. There is 2 types: default and non-default 3 types: auto mode, default auto mode and custom mode
VNET/VPC Type conversion NA NA. Can’t be converted. Default VPC can be deleted, however if you want to recover the deleted VPC then you will have to call AWS support. You can switch non-default auto mode to custom mode but this conversion is one-way. Custom mode networks cannot be changed to auto mode networks.
Reserved IPs 5 (first 4 and last) IP’s in each subnet are reserved 5 (first 4 and last) IP’s in each subnet are reserved 4 (first 2 and last 2) IP’s in each subnet are reserved
Internet Access Turned on by default for all resources inside VNET. Turned on by default for default VPC but turned off for non-default VPC ( created without using VPC Wizard) Turned on by default for default auto mode VPC but turned off for new auto mode or custom mode VPC
VNET/VPC peering Regional and Global VNET peering Regional and inter-regional VPC peering Since VPC is a global construct in GCP hence VPC peering is global in nature.

I tried to summarize everything about VPC and VNET in easiest possible way, however it’s not possible to cover all features here and I’ll be covering more services and details in my next Multi-Cloud blog series. If you have any feedback or questions please feel free to leave your comments below!

Thanks,

Niraj Kumar|Azure Architect-MCSD, AWS SA-A, MCSA-O365, MCT, PMP

Reference:

8 Replies to “Multi-cloud Series Blog 1: Azure VNET vs AWS VPC vs GCP VPC”

Leave a Reply

Your email address will not be published. Required fields are marked *