Question: Why can't I connect to my resources over a Transit Gateway peering connection?

I have inter-Region AWS Transit Gateway peering set up between my source virtual private cloud (VPC) and remote VPC. However, I am unable to connect my VPC resources over the peering connection. How can I troubleshoot this?ResolutionConfirm that the source and remote VPCs are attached to the correct transit gatewayUse the following steps at the source VPC and the remote VPC:Open the Amazon Virtual Private Cloud (Amazon VPC) console.From the navigation pane, choose Transit gateway attachments.Confirm that:The VPC attachments are associated with the correct Transit gateway ID that you used to set up peering.The source VPC and the transit gateway that it's attached to are in the same Region.The remote VPC and the transit gateway that it's attached to are in the the same Region.Find the transit gateway route table that the source and the remote VPC attachments are associated withOpen the Amazon VPC console and choose Transit gateway attachments.Select the VPC attachment.In the Associated route table ID column, note the transit gateway route table ID.Find the transit gateway route table that the source and the remote peering attachments are associated withOpen the Amazon VPC console and choose Transit gateway attachments.Select the Peering attachment.In the Associated route table ID column, note the value transit gateway route table ID.Confirm that source VPC attachment associated with a transit gateway has a static route for remote VPC that points to the transit gateway peering attachmentOpen the Amazon VPC console and choose Transit gateway route tables.Select the Route table. This is the value that you noted in the section Find the transit gateway route table that the source and the remote VPC attachments are associated withChoose the Routes tab.Verify the routes for the remote VPC CIDR block that point to the transit gateway peering attachment.Confirm that remote VPC attachment associated with a transit gateway route table has a static route for source VPC that points to the transit gateway peering attachmentOpen the Amazon VPC console and choose Transit gateway route tables.Select the Route table. This is the value that you noted in the section Find the transit gateway route table that the source and the remote VPC attachments are associated with.Choose the Routes tab.Verify the routes for the source VPC CIDR block that point to the transit gateway peering attachment.Note: To route traffic between the peered transit gateways, add a static route to the transit gateway route table that points to the transit gateway peering attachment.Confirm that the source peering attachment associated transit gateway route table has a route for the source VPC that points to the source VPC attachmentOpen the Amazon VPC console and choose Transit gateway route tables.Select the route table. This is the value that you noted in the section Find the transit gateway route table that the source and the remote peering attachments are associated with.Choose the Routes tab.Verify the routes for the source VPC CIDR block pointing to source VPC attachment.Confirm that the remote peering attachment associated transit gateway route table has a route for the remote VPC that points to the remote VPC attachmentOpen the Amazon VPC console and choose Transit gateway route tables.Select the route table. This is the value that you noted in the section Find the transit gateway route table that the source and the remote peering attachments are associated with.Choose the Routes tab.Verify that there are routes for the remote VPC CIDR block pointing to the remote VPC attachment.Confirm that the routes for the source and remote VPCs are in the VPC subnet route table with the gateway set to Transit GatewayOpen the Amazon VPC console.From the navigation pane, choose Route tables.Select the route table used by the instance.Choose the Routes tab.Under Destination, verify that there's a route for the source/remote VPC CIDR block. Then, verify that Target is set to the Transit Gateway ID.Confirm that source and remote Amazon EC2 instance's security group and network open control list (ACL) allows trafficOpen the Amazon EC2 console.From the navigation pane, choose Instances.Select the instance where you're performing the connectivity test.Choose the Security tab.Verify that the Inbound rules and Outbound rules allow traffic.Open the Amazon VPC console.From the navigation pane, choose Network ACLs.Select the network ACL that's associated with the subnet where your instance is located.Select the Inbound rules and Outbound rules. Verify that the rules allows the traffic needed by your use-case.Confirm that the network ACL associated with the transit gateway network interface allows trafficOpen the Amazon EC2 console.From the navigation pane, choose Network Interfaces.In the search bar, enter Transit gateway. The results show that all network interfaces of the transit gateway appear.Note the Subnet ID that's associated with the location where the transit gateway interfaces were created.Open the Amazon VPC console.From the navigation pane, choose Network ACLs.In the Filter network ACLS search bar, enter the subnet ID that you noted in step 3. This shows the network ACL associated with the subnet.Confirm the Inbound rules and Outbound rules of the network ACL allow traffic to or from the source or remote VPC.