29 of 50 in All Controls
aws

Implement Centralized Network Architecture

IDAWS-NET-001
Severity
high
Automation
Auto
Category
network
Enforcementrecommended
Complexity / Impact
high(disruptive impact)
Risk Profile
medium likelihood(low residual)
Cloud Scopeaws:ou
Environments
productionnon-productionsandbox
Target Resources
AWS::EC2::TransitGatewayAWS::RAM::ResourceShareAWS::EC2::TransitGatewayRouteTableAWS::EC2::VPC
Services
ec2transit-gatewayramorganizations
Tags
networktransit-gatewayarchitecturecentralizationlanding-zone
Frameworks
NIST 800-53ISO 27001PCI DSSSOC 2
Governance
Cloud Security (annually)
Created
2026-05-03
Last Updated
2026-11-16

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.

Beta
Framework / StandardMapped Requirements & ControlsControls
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.

Verify Transit Gateway Availability and RAM Resource Sharebash
# 1. Verify Transit Gateway state and route domain isolation options
aws ec2 describe-transit-gateways \
  --query "TransitGateways[?State=='available'].{TransitGatewayId:TransitGatewayId,State:State,OwnerId:OwnerId,DefaultRouteTableAssociation:Options.DefaultRouteTableAssociation,DefaultRouteTablePropagation:Options.DefaultRouteTablePropagation,AmazonSideAsn:Options.AmazonSideAsn}" \
  --output json

# 2. Verify active RAM resource shares and shared Transit Gateway resources
aws ram get-resource-shares \
  --resource-owner SELF \
  --resource-share-status ACTIVE \
  --query "resourceShares[*].{Name:name,Status:status,ResourceShareArn:resourceShareArn,AllowExternalPrincipals:allowExternalPrincipals}" \
  --output json

aws ram list-resources \
  --resource-owner SELF \
  --resource-type ec2:TransitGateway \
  --query "resources[*].{Arn:arn,Status:status,ResourceShareArn:resourceShareArn}" \
  --output json

# 3. Audit Spoke VPC attachments across accounts
aws ec2 describe-transit-gateway-vpc-attachments \
  --filters "Name=state,Values=available" \
  --query "TransitGatewayVpcAttachments[*].{AttachmentId:TransitGatewayAttachmentId,TgwId:TransitGatewayId,VpcId:VpcId,VpcOwnerId:VpcOwnerId,State:State}" \
  --output json

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

  1. Deploy an AWS Transit Gateway in the dedicated Network account with auto-accept shared attachments enabled and default route table association and propagation disabled.
  2. Share the Transit Gateway with the AWS Organization using AWS Resource Access Manager (RAM).
  3. Create isolated Transit Gateway route tables for spoke workloads, core services, and inspection VPCs.
  4. Attach member account VPCs to the shared Transit Gateway in their respective AWS accounts.
  5. Configure VPC route tables in member accounts to direct inter-VPC and default 0.0.0.0/0 traffic toward the Transit Gateway.
Deploy Transit Gateway and Share via AWS RAMbash
# 1. Create Transit Gateway in the Network account with routing domain isolation
tgw_id=$(aws ec2 create-transit-gateway \
  --description "Central Landing Zone Transit Gateway" \
  --options AmazonSideAsn=64512,AutoAcceptSharedAttachments=enable,DefaultRouteTableAssociation=disable,DefaultRouteTablePropagation=disable,DnsSupport=enable,VpnEcmpSupport=enable \
  --tag-specifications 'ResourceType=transit-gateway,Tags=[{Key=Name,Value=Central-LandingZone-TGW},{Key=Environment,Value=Production}]' \
  --query 'TransitGateway.TransitGatewayId' \
  --output text)

# 2. Retrieve the Transit Gateway ARN
tgw_arn=$(aws ec2 describe-transit-gateways \
  --transit-gateway-ids "$tgw_id" \
  --query 'TransitGateways[0].TransitGatewayArn' \
  --output text)

# 3. Share Transit Gateway across the AWS Organization via AWS RAM
aws ram create-resource-share \
  --name "Central-TGW-Org-Share" \
  --resource-arns "$tgw_arn" \
  --principals "arn:aws:organizations::123456789012:organization/o-exampleorgid" \
  --permission-arns "arn:aws:ram::aws:permission/AWSRAMDefaultPermissionTransitGateway" \
  --no-allow-external-principals

# 4. Create isolated Transit Gateway route tables for Spoke and Inspection domains
aws ec2 create-transit-gateway-route-table \
  --transit-gateway-id "$tgw_id" \
  --tag-specifications 'ResourceType=transit-gateway-route-table,Tags=[{Key=Name,Value=TGW-Spoke-RT}]'

aws ec2 create-transit-gateway-route-table \
  --transit-gateway-id "$tgw_id" \
  --tag-specifications 'ResourceType=transit-gateway-route-table,Tags=[{Key=Name,Value=TGW-Inspection-RT}]'

We value your privacy

We use analytics cookies to understand how visitors interact with our site and to improve the user experience. You can choose to accept or decline these cookies.