AWS, Azure and Google, all have similar or same services but how they work, and some of the functionality is different. This is part of an upcoming Mult-Cloud Networking and Security course.
Network Service Comparison DNS and Network
| Specialty | AWS | Azure | Google Cloud | Note: |
| Virtual Networking | VPC | Virtual Network | VPC Network | Basic VLAN or Virtual Networking Environment |
| NAT Gateway | NAT Gateway | Virtual Network NAT | Cloud NAT | Network Address Translation |
| Cross Network Connection | VPN Gateway | VPN Gateway | VPC Network Peering | Connect two or more networks |
| DNS | Route 53 | DNS | Cloud DNS | DNS Services |
| DNS Routing | Route 53 | Traffic Manager | Cloud DNS | |
| Dedicated Private Network | Direct Connect | Express Route | Cloud Interconnect/ Google Private Access | Peering or private connection between the cloud and a location (not internet connected) |
| Layer 4 Load Balancing | Network Load Balancer | Load Balancer | Load Balancer | Network Load Balancing |
| Layer 7 Load Balancing | Application Load Balancer | Application Gateway | Load Balancer | Application load balancing |
| Route Tables | Custom Route Table | User Defined Routes | Routes Static Routes | Private static routes |
| Private Link | Private Link | Azure Private Link | Private Service Connect | Private access to Cloud resources, keeps data on the cloud provider |
| Private PaaS | VPC Endpoints | Private Endpoint | Private Service Connect | Private connectivity to PaaS resources |
| Virtual Network Peering | VPC Peering | VNET Peering | Google Cloud VPC Network Peering | Connect 2 or more Virtual Networks |
| CDN | Cloud Front | Front Door | Cloud CDN | Content Delivery Network |
| Network Monitoring | VPC Flow Logs | Azure Network Watcher | Cloud Monitoring | Monitor the Cloud Network |
I’m still trying to get over the idea that Azure DNS does not support DNSSEC nor Zone Transfers. Read the documentation here: