When an instance loses access to a destination, draw one concrete connection. Write down the source subnet and address, the destination address and port, and the expected route back. Repeat the drawing when the destination changes. A working connection to a neighbor says little about how an external connection will leave the subnet.

Find the table in use

Look for an explicit route table association for the source subnet. If there is none, use the VPC’s main table. Within the table, the most specific matching destination normally wins. A route for a narrow network can therefore take precedence over the default route.

Distinguish route targets

  • An internet gateway is one piece of an IPv4 public subnet setup. An instance also needs a public address or an appropriate frontend and rules that allow the connection.
  • A public NAT gateway can provide outbound IPv4 access for private subnets. Follow its own subnet route as well as the workload subnet route.
  • An S3 gateway endpoint affects the route tables associated with that endpoint. Check which table was selected and whether the endpoint policy allows the request.

Once the route makes sense, check security groups at the endpoints and network ACLs at the subnets. Security groups are stateful. Network ACLs are stateless, so the return path needs its own allowance. Distinguish TCP reachability from an HTTPS authorization failure before broadening access.

References