Private Service Connect — access Google services and partner services privately
Multi-Cloud Networking
Challenge
Solution
Connectivity
VPN tunnels between clouds, or use cloud interconnect (AWS-Azure ExpressRoute, GCP-AWS Interconnect)
Consistent Policy
Use overlay tools: Aviatrix, Alkira, Prosimo — unified policy across AWS/Azure/GCP
DNS
Hybrid DNS: forward queries between cloud DNS and on-prem DNS → consistent name resolution
Security
Consistent firewall policies across clouds → use cloud-agnostic tools (Palo Alto CN-Series, Fortinet)
Observability
Unified monitoring across clouds: Datadog, ThousandEyes, Kentik — single pane of glass
IaC
Terraform: single tool for AWS + Azure + GCP → consistent infrastructure definition
ทิ้งท้าย: Cloud Networking = New Skills, Same Principles
Cloud Networking VPC: isolated network, subnets (public/private), route tables, IGW, NAT GW Security: Security Groups (stateful, instance-level) + NACLs (stateless, subnet-level) — least privilege Transit Gateway: hub-and-spoke for multi-VPC → replace VPC peering mesh, VPN/DX on-prem connectivity PrivateLink: access cloud services via private IP → no internet exposure, no peering needed Multi-Cloud: 92% enterprises use multi-cloud → VPN/interconnect between clouds, overlay tools (Aviatrix), Terraform IaC Best Practice: private subnets for most resources, LB only in public, SG per instance, TGW for scale Key: cloud networking = same concepts (subnets, routing, firewalls) in software-defined form — learn cloud-specific implementations