You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the following diagram, each env VPC will have an attachment to the transit gateway. And each attachment will have an associated route table and choose to propagate its CIDR to other route tables. In the diagram of link below, the Network-Main-Segrated route table should be the associated route table. And Network-Main-Core route table should be the route table each env VPC to propagate its CIDR to.
In the following diagram, each env VPC will have an attachment to the transit gateway. And each attachment will have an associated route table and choose to propagate its CIDR to other route tables. In the diagram of link below, the Network-Main-Segrated route table should be the associated route table. And Network-Main-Core route table should be the route table each env VPC to propagate its CIDR to.
https://github.com/aws-samples/landing-zone-accelerator-on-aws-for-cccs-medium/blob/main/architecture-doc/images/network/high-level-network-VPN.drawio.png
The text was updated successfully, but these errors were encountered: