A company has deployed applications across 50 VPCs in multiple AWS accounts and needs to implement a network architecture that allows all VPCs to communicate with each other transitively while minimizing connection complexity. Additionally, the company must implement a stateless firewall mechanism at the boundary of each subnet to restrict traffic from specific IP ranges. Which combination of AWS services and features should the company use to meet these requirements?
- AWS Transit Gateway to interconnect the VPCs, and Network Access Control Lists (Network ACLs) for subnet-level stateless filtering.Answer
- BA full mesh of VPC Peering connections to interconnect the VPCs, and Network Access Control Lists (Network ACLs) for subnet-level stateless filtering.
- CAWS Transit Gateway to interconnect the VPCs, and Security Groups for subnet-level stateless filtering.
- DA full mesh of VPC Peering connections to interconnect the VPCs, and Security Groups for subnet-level stateless filtering.
Answer
AWS Transit Gateway to interconnect the VPCs, and Network Access Control Lists (Network ACLs) for subnet-level stateless filtering.
The correct option combines AWS Transit Gateway and Network ACLs. AWS Transit Gateway acts as a central hub to connect VPCs transitively, which is highly scalable for a 50-VPC setup. Network ACLs operate at the subnet boundary and are stateless, meeting the requirement to block traffic from specific IP ranges without tracking connection state.
Step-by-Step Solution
Key Concept
AWS Transit Gateway provides transitive routing for scaling multi-VPC architectures, while Network ACLs offer stateless security filtering at the subnet boundary.