Why aren't the subnet network ACLs in my VPC allowing traffic through the transit gateway?
"I allowed inbound SSH traffic on the network access control list (ACL) for the subnet of my destination Amazon Elastic Compute Cloud (Amazon EC2) instance. However, traffic is still blocked. Why aren't the subnet network ACLs in my virtual private cloud (VPC) allowing traffic through the transit gateway?"
"I allowed inbound SSH traffic on the network access control list (ACL) for the subnet of my destination Amazon Elastic Compute Cloud (Amazon EC2) instance. However, traffic is still blocked. Why aren't the subnet network ACLs in my virtual private cloud (VPC) allowing traffic through the transit gateway?ResolutionWhen you create a transit gateway attachment and then associate a subnet in your VPC, a transit gateway interface is created in that subnet. The transit gateway interface routes traffic from the Amazon EC2 instance's elastic network interface to the transit gateway. The elastic network interface for the Amazon EC2 instance and the transit gateway might be in the same subnet. However, you must consider them as separate entities when configuring the network ACLs.In the network ACL associated with the transit gateway interface at the destination's VPC, add an inbound rule to allow custom TCP on the ephemeral port. With this rule configured, return traffic on the ephemeral port is allowed.Confirm that traffic is flowing as intended by reviewing the VPC Flow Logs on the transit gateway network interface.Note: To learn more about Flow Logs, see Learn From your VPC Flow Logs with additional meta-data.Network ACL inbound and outbound rules are applied differently based on whether Amazon EC2 and the transit gateway are in the same subnet or different subnets. For more information, see How network ACLs work with transit gateways.Related informationVPC Flow Logs - Log and view network traffic flowsFollow"