A company is extending its on-premises corporate office to AWS using a AWS Direct Connect connection. The corporate network needs to access workloads deployed across different Virtual Private Clouds (VPCs) in the same AWS Region. Additionally, the security team requires that any incoming traffic from the on-premises network to the VPCs' database subnets be filtered at the subnet boundary to permit only a specific range of administrative IP addresses. Which AWS networking solution and security feature should the company implement to meet these requirements?
- AVPC Peering to interconnect all VPCs to a central hub VPC connected to Direct Connect, and Network ACLs on the database subnets to filter incoming traffic.
- AWS Transit Gateway to route traffic from the Direct Connect gateway to the VPCs, and Network ACLs on the database subnets to filter incoming traffic.Answer
- CAWS Transit Gateway to route traffic from the Direct Connect gateway to the VPCs, and Security Groups on the database instances to filter traffic at the subnet boundary.
- DVPC Peering to interconnect all VPCs to a central hub VPC connected to Direct Connect, and Security Groups on the database instances to filter traffic at the subnet boundary.
Answer
AWS Transit Gateway combined with Network ACLs on the database subnets.
The solution utilizing AWS Transit Gateway for routing and Network ACLs for filtering is correct. AWS Transit Gateway acts as a cloud router, enabling transitive routing between the on-premises network connected via Direct Connect and all VPCs. Network ACLs operate at the subnet boundary, fulfilling the security requirement to filter incoming database subnet traffic based on source IP ranges.
Step-by-Step Solution
Key Concept
VPC Transitive Routing and Subnet-Level Filtering