A company is expanding its infrastructure from a single Virtual Private Cloud (VPC) to a multi-VPC environment across multiple AWS accounts. The network engineering team needs to design a solution that satisfies two requirements: First, all VPCs must be connected through a centralized hub to simplify routing management and avoid a complex mesh of point-to-point connections. Second, network traffic entering or leaving specific subnets within each VPC must be filtered in a stateless manner. Which combination of AWS services or features should the company use to meet these requirements?
- AVPC Peering and Security Groups
- AWS Transit Gateway and Network Access Control Lists (Network ACLs)Answer
- CAWS Transit Gateway and Security Groups
- DVPC Peering and Network Access Control Lists (Network ACLs)
Answer
AWS Transit Gateway and Network Access Control Lists (Network ACLs)
The combination of AWS Transit Gateway and Network Access Control Lists (Network ACLs) is correct because AWS Transit Gateway operates as a centralized cloud router to simplify traffic management across multiple VPCs and accounts, while Network ACLs are configured at the subnet level to provide stateless traffic filtering.
Step-by-Step Solution
Key Concept
Using AWS Transit Gateway for centralized multi-VPC routing and Network Access Control Lists (Network ACLs) for stateless subnet-level security filtering.