33 of 50 in All Controls
aws

Implement IP Address Management (IPAM)

IDAWS-NET-005
Severity
medium
Automation
Auto
Category
network
Enforcementrecommended
Complexity / Impact
medium(low impact)
Risk Profile
low likelihood(low residual)
Cloud Scopeaws:root
Environments
productionnon-productionsandbox
Target Resources
AWS::EC2::IPAMAWS::EC2::IPAMPoolAWS::EC2::IPAMScope
Services
ec2vpc-ipamorganizations
Tags
networkipamip-managementvpclanding-zone
Frameworks
NIST 800-53ISO 27001PCI DSSSOC 2
Governance
Cloud Security (annually)
Created
2026-05-03
Last Updated
2026-11-16

Specification & Description

Deploy AWS VPC IPAM with delegated administration from the Management account to the Network account, enforcing structured CIDR pool allocation and preventing IP overlap across the AWS Organization.

Technical Specifications

Manual IP address assignment in spreadsheets causes address exhaustion, CIDR collisions, and complex routing workarounds when interconnecting VPCs via Transit Gateway. AWS VPC IPAM centralizes IPv4 and IPv6 address planning across the organization. Delegating IPAM administration to the Network account enables the network team to manage address space without requiring management account access. Defining top-level pools and regional child pools with netmask constraints guarantees that new workload VPCs allocate deterministic, non-overlapping CIDRs directly through automated pipelines.

Security Rationale

Centralized IPAM eliminates IP overlap across member accounts and maintains an authoritative inventory of allocated address space. Automated CIDR assignment through IPAM pools accelerates VPC provisioning and ensures compliance with corporate network boundary standards.

Business & Security Impact

Overlapping CIDR allocations between accounts prevent direct Transit Gateway or private connection routing, requiring complex double-NAT workarounds or expensive VPC renumbering projects during multi-account expansion.

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
CM-8CM-2SC-7
3
ISO 27001:2022ISO 27001
A.8.9A.8.20
2
PCI DSS v4.0PCI DSS
1.2.3
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 IPAM administration is delegated to the Network account in AWS Organizations, audit IPAM instances and operational states across regions, and verify pool allocation boundaries and utilization metrics.

Verify Delegated Admin, IPAM Instance, and Pool Allocationsbash
# 1. Verify delegated IPAM administrator in AWS Organizations
aws organizations list-delegated-administrators \
  --service-principal ipam.amazonaws.com \
  --query "DelegatedAdministrators[*].{Id:Id,Arn:Arn,Status:Status}" \
  --output json

# 2. Describe IPAM instances and operating regions
aws ec2 describe-ipams \
  --query "Ipams[*].{IpamId:IpamId,State:State,Tier:Tier,OperatingRegions:OperatingRegions[*].RegionName}" \
  --output json

# 3. Audit IPAM pools and netmask allocation limits
aws ec2 describe-ipam-pools \
  --query "IpamPools[*].{PoolId:IpamPoolId,AddressFamily:AddressFamily,State:State,Locale:Locale,DefaultNetmask:AllocationDefaultNetmaskLength}" \
  --output json

Remediation Guide & Automation

Delegate IPAM administration to the Network account from the Management account. In the Network account, create an IPAM instance across all active operating regions, establish private scope pools with netmask allocation rules, and require member accounts to provision VPC CIDRs directly from delegated IPAM pools.

Step-by-Step Instructions

  1. Enable IPAM organizational delegation from the AWS Organizations Management account to the dedicated Network account.
  2. Create an advanced tier IPAM instance in the Network account configured with all operational regions.
  3. Create a top-level IPv4 pool in the default private scope and provision the organization CIDR block.
  4. Create regional child pools with allocation netmask constraints (minimum /24, maximum /20, default /22).
  5. Provision VPCs using --ipv4-ipam-pool-id to automate conflict-free CIDR assignment.
Delegate IPAM Admin and Provision Hierarchical IPAM Poolsbash
# 1. From Management Account: Delegate IPAM administration to the Network account
aws ec2 enable-ipam-organization-admin-account \
  --delegated-admin-account-id "123456789012"

# 2. From Network Account: Create IPAM instance across operating regions
ipam_id=$(aws ec2 create-ipam \
  --description "Central Landing Zone IPAM" \
  --operating-regions RegionName=us-east-1 RegionName=eu-central-1 \
  --tier advanced \
  --tag-specifications 'ResourceType=ipam,Tags=[{Key=Name,Value=Central-LandingZone-IPAM},{Key=Environment,Value=Production}]' \
  --query 'Ipam.IpamId' \
  --output text)

# 3. Retrieve default private scope ID
scope_id=$(aws ec2 describe-ipams \
  --ipam-ids "$ipam_id" \
  --query 'Ipams[0].PrivateDefaultScopeId' \
  --output text)

# 4. Create top-level private IPv4 pool
pool_id=$(aws ec2 create-ipam-pool \
  --ipam-scope-id "$scope_id" \
  --address-family ipv4 \
  --description "Enterprise Root IPv4 Pool" \
  --query 'IpamPool.IpamPoolId' \
  --output text)

# 5. Provision top-level CIDR to the pool
aws ec2 provision-ipam-pool-cidr \
  --ipam-pool-id "$pool_id" \
  --cidr "10.0.0.0/8"

# 6. Create regional child pool with netmask allocation rules
child_pool_id=$(aws ec2 create-ipam-pool \
  --ipam-scope-id "$scope_id" \
  --source-ipam-pool-id "$pool_id" \
  --address-family ipv4 \
  --locale us-east-1 \
  --allocation-min-netmask-length 24 \
  --allocation-max-netmask-length 20 \
  --allocation-default-netmask-length 22 \
  --description "USEast1 Workloads Pool" \
  --query 'IpamPool.IpamPoolId' \
  --output text)

# 7. Provision CIDR to regional child pool
aws ec2 provision-ipam-pool-cidr \
  --ipam-pool-id "$child_pool_id" \
  --cidr "10.10.0.0/16"

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.