Common Cloud Network Issues
Security group misconfiguration: the most common cloud connectivity problem. A cloud instance cannot be reached because an inbound security group rule is missing or incorrect. Security groups are stateful — outbound traffic automatically allows return traffic. Check: inbound rules allow the required port from the correct source, correct security group is attached to the instance.
VPC/subnet routing: traffic cannot flow between subnets or from a subnet to the internet. Check: route table for the subnet includes the correct routes (internet gateway route for public subnets, NAT gateway route for private subnets). Verify the internet gateway is attached to the VPC. Verify the NAT gateway has an elastic IP.
Network ACL issues (cloud): cloud NACLs are stateless and applied at the subnet level. Both inbound AND outbound rules must permit the traffic (unlike security groups). Check NACLs if security groups are correct but traffic still fails — NACLs may be blocking return traffic.
Hybrid Connectivity Troubleshooting
VPN to cloud: on-premises resources cannot reach cloud VPC. Check: VPN tunnel status (both Phase 1 and Phase 2), route propagation (cloud side must have routes to on-premises subnets and vice versa), security group rules on cloud instances must permit traffic from on-premises subnets.
Direct Connect / ExpressRoute: dedicated private circuit to cloud provider. If the circuit is up but traffic fails, check: BGP session status (the circuit uses BGP for route exchange), route filters (some providers require explicit route filters), VLAN configuration on the customer router.
DNS in cloud: VPC DNS resolver must be enabled for instances to resolve DNS. Hybrid environments need DNS forwarding rules: on-premises DNS forwards cloud domain queries to the cloud resolver; cloud DNS forwards corporate domain queries to on-premises DNS. Missing DNS forwarding rules break name resolution in hybrid environments.
Cloud Diagnostic Tools
Cloud provider tools: VPC Flow Logs (AWS/Azure) capture metadata about traffic flowing through VPC — source/destination IP, port, protocol, action (ACCEPT/REJECT). Essential for diagnosing security group and NACL issues. AWS Reachability Analyzer: tests network path between two resources and shows where traffic is blocked. Azure Network Watcher: similar — connection troubleshoot, packet capture, topology view.
On-instance testing: SSH or RDP into a cloud instance and run the same diagnostic tools as on-premises — ping, traceroute, curl, netstat. The instance's perspective confirms whether traffic issues are inbound (reaching the instance) or outbound (from the instance).