Introduction
Thank you for reading the article!
I was able to verify all the AWS hands-on tests I used in my previous article on Trangit Gateway without any problems. In this article, I would like to discuss the results of testing communications via Trangit Gateway using the VPC Reachabiligy Analyzer.
Hands-on Documents（AWS）
The perspectives I would like to investigate this time are as follows:
- EC2 in Boundary VPC ↔ EC2 in Private VPC1
- EC2 in Boundary VPC ↔ TGW attachment in Private VPC2
- EC2 in Boundary VPC ↔ TGW attachment in Private VPC3
The current Ping communication confirmation results are as follows.
EC2 in Boundary VPC ↔ EC2 in Private VPC1
Setting For VPC Reachability Analyzer
Results
Information
It seems that it is not possible to display the reverse path when communicating via Trangit Gateway.
EC2 in Boundary VPC ↔ TGW attachment in Private VPC2
Setting For VPC Reachability Analyzer
Results
EC2 in Boundary VPC ↔ TGW attachment in Private VPC3
Setting For VPC Reachability Analyzer
Results
Summary
The error TGW_RTB_NO_ROUTE_TO_TGW_ATTACHMENT was commonly displayed, which is thought to be due to the hands-on configuration used this time.
Therefore, it is thought that the cause is that the route was not set in the route table, so detection by the VPC Reachability Analyzer was not possible.
The error content is summarized in the following document, so please refer to it when troubleshooting.
https://docs.aws.amazon.com/vpc/latest/reachability/explanation-codes.html
Furthermore, using Amazon Q to identify and address the cause of this error is expected to improve the speed of troubleshooting.
Personally, I would have liked to analyze the communication settings using Network Access Analyzer, but I will try to verify this next time.
This is a simple verification article, but thank you for reading to the end.
Top comments (0)