Compare VPC/VNet/VCN peering models across AWS, Azure, GCP, and OCI.
Showing 20 of 20 features.
| Feature | AWS | Azure | GCP | OCI |
|---|---|---|---|---|
Service Name Core Features | VPC Peering / Transit Gateway | VNet Peering / Virtual WAN | VPC Network Peering | Local/Remote Peering (LPG/RPC via DRG) |
Peering Model Core Features | Point-to-point VPC peering; hub-and-spoke via Transit Gateway | Point-to-point VNet peering; hub-and-spoke via Virtual WAN | Point-to-point VPC peering (up to 25 per VPC network) | Local Peering Gateway (same region); Remote Peering Connection (cross-region) |
Transitive Routing Core Features | VPC Peering: non-transitive; Transit Gateway: transitive routing | VNet Peering: non-transitive; Virtual WAN: transitive hub routing | Non-transitive by default; use NVA or Cloud Router for transit | DRG provides transitive routing between peered VCNs |
Cross-Region Peering Core Features | Inter-region VPC peering; Transit Gateway peering across regions | Global VNet peering across any Azure regions | VPC peering is automatically global (VPCs are global resources) | Remote Peering Connection via DRG for cross-region |
Pricing Core Features | VPC Peering: data transfer per GB (same-region free); TGW: per attachment + data | VNet Peering: inbound + outbound per GB; global peering higher rates | Same-region peering: free; cross-region: standard egress rates | LPG: free same-region; RPC: inter-region data transfer charges |
Max Peerings per Network Architecture | 125 VPC peering connections per VPC (adjustable) | 500 VNet peerings per virtual network (adjustable) | 25 peering connections per VPC network (adjustable to 35) | 10 LPGs per VCN (adjustable); DRG supports up to 300 attachments |
CIDR Overlap Handling Architecture | No overlapping CIDRs allowed between peered VPCs | No overlapping address spaces allowed between peered VNets | No overlapping subnet CIDRs allowed; partial overlap rejected | No overlapping CIDRs allowed between peered VCNs |
Bandwidth Architecture | VPC Peering: no bandwidth limit (AWS backbone); TGW: 50 Gbps per AZ | VNet Peering: no bandwidth limit (Azure backbone); VM SKU limits apply | No bandwidth limit (Google backbone); VM egress caps apply | LPG: no bandwidth limit; DRG: based on DRG capacity |
Hub-and-Spoke Architecture Architecture | Transit Gateway as hub connecting up to 5,000 VPCs and VPNs | Virtual WAN or hub VNet with peering and NVA routing | Hub VPC with peering + Cloud Router; Network Connectivity Center | DRG as hub with VCN, VPN, and FastConnect attachments |
Cross-Account / Tenant Peering Architecture | Cross-account VPC peering with owner acceptance required | Cross-subscription and cross-tenant VNet peering with authorization | Cross-project VPC peering with Shared VPC or explicit peering | Cross-tenancy peering via DRG and IAM policies |
Route Management Security & Routing | Manual route table entries for peering; TGW route tables with propagation | Peered VNet routes auto-propagated; UDRs for custom routing | Auto-imported subnet routes; custom route exchange configurable | Route table rules pointing to LPG/DRG; auto-propagation in DRG |
Security Controls Security & Routing | Security groups and NACLs; VPC endpoint policies for peering | NSGs and Azure Firewall; allow-forwarded-traffic and allow-gateway-transit flags | Firewall rules apply across peering; export custom routes option | Security lists and NSGs apply; DRG route tables for filtering |
DNS Resolution Security & Routing | Enable DNS resolution in peering; Route 53 Resolver for cross-VPC DNS | Auto DNS resolution in peered VNets; Private DNS zone links | Auto DNS resolution across peered VPCs; Cloud DNS peering zones | DNS views for cross-VCN resolution; private DNS zones |
Traffic Inspection Security & Routing | Route through Network Firewall or NVA in TGW architecture | Route through Azure Firewall or NVA in hub VNet | Route through NVA in hub VPC; Cloud NGFW inspection | Route through Network Firewall in hub VCN via DRG |
Network Segmentation Security & Routing | Multiple TGW route tables for domain-based segmentation | Multiple hub VNets or Virtual WAN secure hubs for segments | Separate VPC networks with selective peering | DRG route tables for VCN segmentation and isolation |
Setup Complexity Operations | VPC Peering: requester-accepter model; TGW: centralized setup | VNet Peering: bilateral configuration; Virtual WAN: portal/CLI wizard | Bilateral peering creation from both VPC networks | LPG: bilateral; DRG: centralized hub attachment model |
Monitoring Operations | VPC Flow Logs; CloudWatch metrics for TGW (bytes, packets, drops) | NSG flow logs; Azure Monitor metrics for peering data transfer | VPC Flow Logs; Firewall Insights for peering traffic | VCN Flow Logs; OCI Monitoring metrics for DRG |
Terraform Support Operations | aws_vpc_peering_connection, aws_ec2_transit_gateway, aws_ec2_transit_gateway_vpc_attachment | azurerm_virtual_network_peering, azurerm_virtual_wan, azurerm_virtual_hub | google_compute_network_peering resource | oci_core_local_peering_gateway, oci_core_remote_peering_connection, oci_core_drg |
Hybrid Connectivity Operations | TGW connects VPN and Direct Connect alongside VPC peering | Virtual WAN integrates VPN, ExpressRoute, and peering | Cloud Router with VPN/Interconnect + peering for hybrid | DRG integrates VPN, FastConnect, and VCN peering |
Limits & Quotas Operations | 125 peerings/VPC; 5,000 VPC attachments/TGW; adjustable via support | 500 peerings/VNet; 8 Virtual WANs/subscription (adjustable) | 25 peerings/VPC (adjustable); 15,500 VM instances per peering group | 10 LPGs/VCN; 300 DRG attachments; adjustable via support request |
Compare VPC/VNet/VCN peering models across AWS, Azure, GCP, and OCI. This tool helps multi-cloud engineers generate valid configurations quickly without consulting documentation, reducing errors and accelerating infrastructure deployment. All processing runs in your browser with no data sent to external servers.
Disclaimer: This tool runs entirely in your browser. No data is sent to our servers. Always verify outputs before using them in production. AWS, Azure, and GCP are trademarks of their respective owners.