Many VPCs must reach shared services.
Reduce the growing route-management burden of individual peerings and centralize the network design.
Which design is most appropriate?
Use AWS Transit Gateway as a central hub for VPC attachments and manage connectivity in Transit Gateway route tables.
Detailed explanation
Connection and route counts grow rapidly with each VPC and increase operational work.
Connection and route counts grow rapidly with each VPC and increase operational work.
Transit Gateway centralizes VPC attachments and routing instead of requiring a full mesh of peerings.
Transit Gateway centralizes VPC attachments and routing instead of requiring a full mesh of peerings.
DNS records resolve names but do not forward network packets.
DNS records resolve names but do not forward network packets.
S3 stores objects and is not a network routing control plane.
S3 stores objects and is not a network routing control plane.
Check official documentation
Compare the following points with the official documentation.
AWS Transit Gatewayのルーティングと接続料金の公式説明を確認する。
What to confirm
VPC数と運用負担に応じたハブ型ネットワークを設計できる。
Key points
- AWS Transit Gateway
- VPC attachment
- Centralized routing
Notes
- Environment: AWS公式Transit Gatewayドキュメントの確認
- Confirm current AWS pricing and service behavior in the official documentation.
Foundation review
Topology scaling
A hub-and-spoke model avoids the connection explosion of a full mesh.
Routing plane
Transit Gateway route tables forward packets; DNS records only resolve names.