Implement Centralized Network Architecture
Specification & Description
Establish a centralized network architecture using a dedicated Network account with AWS Transit Gateway and AWS Resource Access Manager to govern inter-VPC and on-premises traffic.
Technical Specifications
Operating separate network environments in every account creates routing fragmentation, redundant external connectivity, and inconsistent firewall policy enforcement. A centralized network design places AWS Transit Gateway in a dedicated Network core account and shares it across the AWS Organization using AWS Resource Access Manager (RAM). Member account VPCs attach to the shared Transit Gateway, directing inter-VPC, egress, and on-premises traffic through centrally administered route tables and inspection VPCs.
Security Rationale
A centralized network architecture establishes consistent routing policies, eliminates VPC peering meshes, and provides a single administrative boundary for network inspection. Centralizing Transit Gateway in the Network account ensures infrastructure teams enforce routing isolation between environments while simplifying multi-account network operations.
Business & Security Impact
Decentralized network configurations cause route sprawl, redundant transit connectivity costs, and inconsistent security perimeter enforcement across member accounts. Uncontrolled VPC peering increases exposure to lateral movement during an account compromise.
Compliance Framework Mappings (4)
Regulatory baselines and industry standards mapped to this control specification.
| Framework / Standard | Mapped Requirements & Controls | Controls |
|---|---|---|
NIST 800-53 Rev 5NIST 800-53 | AC-4SC-7 | 2 |
ISO 27001:2022ISO 27001 | A.8.20A.8.22 | 2 |
PCI DSS v4.0PCI DSS | 1.2.1 | 1 |
SOC 2SOC 2 | CC6.6 | 1 |
* Compliance framework mappings are provided for informational architectural reference. Always verify control alignment against your organization's formal audit requirements.
Automated Detection & Rule Logic
Detection Engine: aws-api • Automated: Yes
Verify that an available Transit Gateway exists in the Network account with expected route table isolation settings, and confirm that an active AWS RAM resource share shares the gateway across the organization without allowing external principals.
Remediation Guide & Automation
Deploy an AWS Transit Gateway in the dedicated Network account with default route table propagation and association disabled for routing domain isolation. Share the Transit Gateway across the AWS Organization via AWS Resource Access Manager, attach member account VPCs, and route egress and inter-VPC traffic through dedicated inspection route tables.
Step-by-Step Instructions
- Deploy an AWS Transit Gateway in the dedicated Network account with auto-accept shared attachments enabled and default route table association and propagation disabled.
- Share the Transit Gateway with the AWS Organization using AWS Resource Access Manager (RAM).
- Create isolated Transit Gateway route tables for spoke workloads, core services, and inspection VPCs.
- Attach member account VPCs to the shared Transit Gateway in their respective AWS accounts.
- Configure VPC route tables in member accounts to direct inter-VPC and default 0.0.0.0/0 traffic toward the Transit Gateway.