A company has a hybrid network with an AWS Direct Connect connection to a VPC. They also have a site-to-site VPN connection as a backup. The VPC routing tables are configured with a route to the on-premises CIDR via the virtual private gateway. The network engineer notices that traffic from the VPC to on-premises is not using the Direct Connect connection even when it is healthy. What is the most likely cause?
Trap 1: The VPN connection is down
If the VPN is down, traffic would be routed via Direct Connect if the route exists.
Trap 2: The VPN connection is attached to a Customer Gateway
The AWS Site-to-Site VPN connection uses a virtual private gateway or transit gateway, not a Customer Gateway as the target.
Trap 3: The Direct Connect virtual interface is in the 'Down' state
The Direct Connect virtual interface must be in the 'Available' state to pass traffic.
- A
The VPC route table has a more specific route pointing to the VPN connection
If the VPN BGP route is more specific (e.g., /24 vs /16), it will take precedence over the static route to Direct Connect.
- B
The VPN connection is down
Why wrong: If the VPN is down, traffic would be routed via Direct Connect if the route exists.
- C
The VPN connection is attached to a Customer Gateway
Why wrong: The AWS Site-to-Site VPN connection uses a virtual private gateway or transit gateway, not a Customer Gateway as the target.
- D
The Direct Connect virtual interface is in the 'Down' state
Why wrong: The Direct Connect virtual interface must be in the 'Available' state to pass traffic.