IP Address Management (IPAM)¶
Prerequisites
This section assumes familiarity with Before You Start, AWS Organizations, Amazon VPC, and CIDR Planning. Review those pages first if you're new to AWS networking fundamentals.
AWS IPAM (IP Address Management) is the control plane for your organization's IP address space. It replaces spreadsheets, Confluence pages, and tribal knowledge with a centralized, policy-driven system that plans, allocates, tracks, and monitors IP addresses across every account and Region in your AWS Organization. Without IPAM, IP address management degrades into a coordination bottleneck: teams file tickets for CIDR blocks, networking engineers manually check for overlaps, and nobody has confidence that the next VPC won't conflict with an existing one. IPAM eliminates that friction by making allocation automatic, overlap-free, and auditable.
The service operates through a hierarchy of pools — collections of CIDR ranges organized by Region, environment, or business unit — with allocation rules that enforce sizing, tagging, and locality constraints. When a team creates a VPC, they request a CIDR from the appropriate pool, and IPAM guarantees a non-overlapping allocation that complies with your organizational standards. No tickets, no manual checks, no spreadsheet updates.

IPAM pool hierarchy — Drawio Source
Key capabilities¶
-
Hierarchical pool management
Organize IP address space into nested pools by Region, environment, and workload type. Pools inherit constraints from parents and enforce allocation rules at every level.
-
Overlap prevention
Every allocation is validated against the entire pool hierarchy. IPAM guarantees that no two VPCs receive conflicting CIDR blocks, eliminating the most common networking mistake in multi-account environments.
-
Utilization monitoring
Real-time visibility into how much address space is allocated, used, and available across every pool, Region, and account. Alerts when pools approach exhaustion.
-
Allocation rules
Enforce minimum and maximum CIDR sizes, required tags, and locale restrictions on every allocation. Rules prevent teams from requesting inappropriately sized blocks or deploying in unauthorized Regions.
-
Organizations integration
Delegate IPAM administration to a networking account, share pools across the Organization via RAM, and monitor compliance across all member accounts automatically.
-
Compliance auditing
Continuous monitoring detects VPCs with manually assigned CIDRs that violate your allocation rules, overlap with managed pools, or lack required tags.
When to use AWS IPAM¶
IPAM becomes essential the moment your AWS environment grows beyond what a single engineer can track mentally. The threshold is lower than most teams expect.
Use IPAM when:
- You operate more than 5-10 VPCs across any number of accounts. Manual tracking breaks down quickly, and the cost and operational complexity of connecting overlapping networks exceed the cost of IPAM for years.
- Multiple teams create VPCs independently. Without centralized allocation, teams will choose CIDRs that conflict with each other or with on-premises networks.
- You need to connect VPCs to each other or to on-premises networks. IPAM prevents overlaps that block VPC Peering and complicate Transit Gateway, Cloud WAN, and hybrid connectivity.
- Compliance frameworks require you to demonstrate IP address governance and audit trails.
- You plan to use Infrastructure as Code for VPC provisioning. IPAM pools integrate directly with CloudFormation and Terraform, enabling fully automated, conflict-free VPC creation.
You can defer IPAM when:
- You have a single account with 1-2 VPCs and no hybrid connectivity. Even here, setting up IPAM early avoids retrofitting later.
- You're running isolated sandbox accounts that will never connect to production networks.
Key insight: The cost of not using IPAM is invisible until an overlap affects connectivity. CIDR overlaps are often discovered when you try to peer VPCs, attach them to Transit Gateway or Cloud WAN, or establish hybrid connectivity. At that point, the available remedies require either workload migration or ongoing translation and address-management overhead. IPAM prevents that complexity before deployment.
Best Practices¶
Pool hierarchy design¶
Design pools top-down: Organization → Region → Environment → Workload¶
The pool hierarchy should mirror your organizational structure and reflect how you want to govern address space. Start with your entire range at the top, subdivide by Region (to enable route summarization), then by environment (to enforce isolation), and optionally by workload type (to apply different sizing rules). Build it for IPv4 and IPv6 together, before the first dual-stack VPC: the same levels, the same allocation rules and required tags, and one compliance view of both address families per VPC.
A well-designed hierarchy for a typical enterprise:
| Level | IPv4 | IPv6 |
|---|---|---|
| Top-level pool | 10.0.0.0/8 — your entire private address space |
Your BYOIP block, or a private IPv6 ULA/GUA range for internal-only addressing. Amazon-provided contiguous space starts at the Regional pool |
| Regional pools | /12 per Region — 1,048,576 addresses, enough for thousands of VPCs |
A contiguous block carved from the top-level BYOIP or private range, or an Amazon-provided block (/52 to /40) |
| Environment pools | /13 or /14 per environment within a Region — separates production from non-production |
A slice of the Regional block per environment |
| Workload pools (optional) | /16 or larger per workload type — applies different allocation rules to EKS clusters vs. standard VPCs |
Same split, where allocation rules differ |
This structure enables route summarization at every level, in both families. Your on-premises network can route to 10.0.0.0/12 and one IPv6 prefix for all of us-east-1, rather than maintaining individual routes for every VPC. That summarization reduces route table size on your on-premises routers and simplifies firewall rules, and it holds only while every VPC in the Region allocates from inside its Regional pool, which locale restrictions guarantee.
Choose the IPv6 source before creating the pools. An Amazon-provided contiguous block must be provisioned to a pool with a Region locale, so that hierarchy starts at the Regional pool. BYOIP provides publicly routable organization-wide space and address portability. A private ULA or privately used GUA range can instead provide an organization-wide hierarchy for internal-only addressing; private GUA space must be owned by your organization and cannot later be advertised publicly from AWS. VPCs that request an Amazon-provided IPv6 CIDR outside IPAM get unrelated prefixes that cannot be summarized, and fixing that later means re-addressing every dual-stack workload.
Size regional pools generously — address space is not a scarce resource¶
The most common IPAM mistake is creating regional pools that are too small. A /16 regional pool gives you only 256 /24 VPCs or 16 /20 VPCs. That sounds like enough until you account for production, staging, development, and sandbox environments across dozens of accounts.
Use /12 for regional pools if your top-level pool is a /8. This gives each Region 16 /16 blocks or 256 /20 blocks — enough for years of growth. If you're constrained to a smaller top-level range (for example, 10.0.0.0/10 because the rest is used on-premises), allocate at least a /14 per Region.
The cost of oversizing a pool is zero — unused address space in a pool costs nothing. The cost of undersizing is a pool restructuring that requires reallocating every VPC beneath it.
Create separate pool branches for production and non-production¶
Production and non-production workloads should draw from different pool branches, not different allocations within the same pool. This separation enables:
- Different allocation rules (production VPCs get
/16, development VPCs get/20) - Different sharing policies (production pools shared only with production OUs)
- Independent utilization monitoring (production pool exhaustion is a different severity than dev pool exhaustion)
- Route summarization by environment (useful for firewall rules that treat production traffic differently)
Key insight: Your pool hierarchy is your IP governance model expressed as infrastructure. A flat hierarchy with one pool per Region gives you overlap prevention but nothing else. A deep hierarchy gives you governance, summarization, environment isolation, and differentiated allocation rules — all enforced automatically.
Allocation rules¶
Set minimum and maximum CIDR sizes on every pool¶
Every pool that teams allocate from should have explicit size constraints. Without them, a team can request a /16 from a development pool (wasting address space) or a /28 for a production workload (creating expansion problems immediately).
Recommended sizing rules:
| Pool type | Min CIDR | Max CIDR | Rationale |
|---|---|---|---|
| Production | /20 |
/16 |
Production VPCs need room for growth, multiple subnet tiers, and IP-hungry services (EKS, ECS) |
| Non-production | /24 |
/20 |
Dev/test VPCs need less space but should still accommodate basic subnet tiers |
| Sandbox | /26 |
/24 |
Sandbox VPCs are ephemeral and small; conserve address space |
| EKS workloads | /16 |
/16 |
EKS with VPC CNI consumes IPs aggressively; undersizing causes pod scheduling failures |
Require tags on every allocation¶
Allocation rules can mandate specific tags before a CIDR is granted. At minimum, require:
Environment(production, staging, development, sandbox)TeamorCostCenter(for accountability)Application(for traceability)
Required tags serve two purposes: they enforce governance at allocation time (teams must classify their VPCs before getting address space), and they enable IPAM's compliance monitoring to identify untagged or mistagged resources later.
Use locale restrictions to prevent cross-Region allocation mistakes¶
Each pool can be restricted to a specific AWS Region. A pool designated for us-east-1 will reject allocation requests from us-west-2. This prevents a common mistake where teams accidentally allocate from the wrong regional pool, consuming address space intended for a different Region and breaking your summarization strategy.
Set the locale on every pool below the top level. The top-level pool spans all Regions; regional pools and below should always have a locale set.
Key insight: Allocation rules are not bureaucracy — they're guardrails that prevent the three most expensive IPAM mistakes: oversized allocations that waste space, undersized allocations that require VPC recreation, and cross-Region allocations that break route summarization.
Scopes: private vs. public¶
Use the private scope for internal IPv4 and IPv6 address management¶
The private scope manages RFC 1918 ranges (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16), RFC 6598 shared address space (100.64.0.0/10, commonly used for EKS pod networking), and private IPv6 ULA/GUA ranges. Private IPv6 ranges support internal and hybrid connectivity but cannot be advertised to the internet from AWS. Every organization needs the private scope; it is the core IPAM use case.
Use the public scope for publicly routable address management¶
The public scope manages public IPv4 and IPv6 blocks brought to AWS through BYOIP, and Amazon-provided contiguous public IPv6 blocks. AWS-assigned public IPv4 addresses and Elastic IP addresses remain outside IPAM pools. For an IPv6 hierarchy without an organization-owned block, provision an Amazon-provided contiguous block directly to a Regional pool in the public scope.
Delegated administration¶
Delegate IPAM to your centralized networking account¶
IPAM should be administered from a dedicated networking account (or shared-services account), not the Organization management account. Delegated administration keeps the management account clean (it should only handle Organizations, billing, and SCPs) while giving the networking team full IPAM control.
The delegated administrator account can:
- Create and manage all IPAM pools and allocation rules
- Monitor compliance across the entire Organization
- Share pools with other accounts via RAM
- View IP address usage in all member accounts
Share pools at the OU level, not individual accounts¶
When sharing IPAM pools via AWS RAM, share with Organizational Units rather than specific accounts. This ensures that new accounts added to an OU automatically gain access to the appropriate pools without manual intervention. Your account vending process creates an account in the correct OU, and IPAM pool access follows automatically.
Structure your sharing to match your pool hierarchy:
- Production OU → access to production pools
- Development OU → access to non-production pools
- Sandbox OU → access to sandbox pools
Key insight: Delegated administration + OU-level sharing creates a self-service model where teams get the right address space automatically. The networking team defines the rules once; every subsequent VPC creation follows those rules without human intervention.
Compliance monitoring¶
Enable IPAM compliance monitoring across your Organization¶
IPAM continuously monitors all VPCs in your Organization and flags those that:
- Have CIDRs that overlap with managed pool allocations
- Were created with manually assigned CIDRs outside any IPAM pool
- Lack required tags defined in allocation rules
- Violate locale restrictions
This monitoring catches VPCs created before IPAM was deployed, VPCs created by teams that bypassed IPAM (using hardcoded CIDRs in their templates), and VPCs in accounts that were recently added to the Organization.
Treat compliance violations as high-priority findings¶
A non-compliant VPC is a ticking time bomb. It might work fine in isolation, but the moment you try to connect it to your network (Transit Gateway, Cloud WAN, peering), an overlap will surface. Address compliance violations proactively:
- Identify the non-compliant VPC and its owner
- Determine if the CIDR actually conflicts with your managed space
- If it conflicts, plan a migration to a compliant CIDR. Use permanent address translation only as a documented exception when re-IPing is not practical.
- If it doesn't conflict, import the CIDR into IPAM to bring it under management
Import existing CIDRs into IPAM before they cause problems¶
If you're adopting IPAM in an environment with existing VPCs, import their CIDRs into your pool hierarchy. This registers them as known allocations, preventing future allocations from overlapping with them. Importing doesn't change the VPC — it just tells IPAM "this space is taken."
Use IPAM to enforce dual-stack adoption¶
IPAM compliance monitoring can identify VPCs that have IPv4 allocations but no IPv6 allocation — useful for tracking your dual-stack adoption progress. As your organization moves toward IPv6-first, IPAM provides the visibility to know which VPCs still need IPv6 enablement.
Key insight: IPAM compliance monitoring is your early warning system. Every non-compliant VPC is a potential connectivity failure waiting to happen. The cost of ignoring it is a production incident when you discover an overlap during a connectivity change.
Integration with Infrastructure as Code¶
Reference IPAM pools in CloudFormation using Ipv4IpamPoolId¶
CloudFormation supports IPAM-allocated CIDRs natively. Instead of hardcoding a CIDR in your VPC template, reference the IPAM pool and let IPAM assign a non-overlapping block:
Resources:
MyVPC:
Type: AWS::EC2::VPC
Properties:
Ipv4IpamPoolId: !Ref IpamPoolId
Ipv4NetmaskLength: 16
Tags:
- Key: Environment
Value: production
- Key: Application
Value: my-app
This approach means your VPC template is reusable across accounts and Regions — the CIDR is determined at deployment time based on which pool is available in that context.
Use the aws_vpc_ipam_pool_cidr_allocation resource in Terraform¶
Terraform's AWS provider supports IPAM through the aws_vpc_ipam_pool_cidr_allocation data source and the ipv4_ipam_pool_id argument on aws_vpc:
resource "aws_vpc" "main" {
ipv4_ipam_pool_id = var.ipam_pool_id
ipv4_netmask_length = 16
tags = {
Environment = "production"
Application = "my-app"
}
}
Both approaches eliminate hardcoded CIDRs from your IaC templates, which is the single most impactful change you can make for IP address governance. Hardcoded CIDRs in templates are the primary source of overlaps in organizations that use IaC — teams copy templates, forget to change the CIDR, and create conflicting VPCs.
Store pool IDs in SSM Parameter Store or Terraform remote state¶
IPAM pool IDs are the bridge between your IaC templates and your address space governance. Store them in AWS Systems Manager Parameter Store (accessible cross-account via RAM) or in Terraform remote state so that templates can reference the correct pool without hardcoding pool IDs.
Key insight: The combination of IPAM pools + IaC templates that reference those pools is what transforms IP address management from a manual coordination problem into an automated, self-service capability. Teams deploy VPCs without knowing or caring what CIDR they'll get — they just know it will be correct, non-overlapping, and compliant.
Hybrid connectivity and on-premises integration¶
Import on-premises CIDR ranges into IPAM as non-allocatable reservations¶
Your on-premises networks occupy address space that AWS IPAM must know about to prevent overlaps. Import these ranges into your top-level pool as manual allocations (or into a dedicated "on-premises" pool) so that IPAM's overlap detection accounts for them.
This is critical for organizations using RFC 1918 space on-premises. If your data center uses 10.0.0.0/16 through 10.15.0.0/16, those ranges must be reserved in IPAM before any AWS pool can allocate from the same space. Without this reservation, IPAM might allocate 10.5.0.0/16 to a new VPC — which will fail the moment you try to route between that VPC and on-premises.
Common mistakes to avoid¶
Mistake: Creating pools that are too small¶
A /16 regional pool seems large until you realize it supports only 16 /20 VPCs or a single /16 VPC. Organizations that start with small pools hit exhaustion within months and face a painful restructuring. Always size pools for 5-10 years of growth.
Mistake: No regional hierarchy (flat pool structure)¶
A single pool for all Regions prevents route summarization and makes locale-based governance impossible. Even if you operate in one Region today, create a regional pool beneath your top-level pool. Adding a second Region later is trivial with the hierarchy in place; retrofitting it requires reallocating existing VPCs.
Mistake: No allocation rules on leaf pools¶
Pools without allocation rules are just CIDR containers — they prevent overlaps but don't enforce governance. Teams can request any size, skip tags, and deploy in any Region. Add rules to every pool that teams allocate from directly.
Mistake: Not importing existing VPCs before enabling compliance monitoring¶
If you enable compliance monitoring without first importing existing VPC CIDRs, every pre-existing VPC will appear as non-compliant. This creates alert fatigue and makes it impossible to distinguish genuinely problematic VPCs from legacy ones. Import first, then enable monitoring.
Mistake: Sharing pools too broadly¶
Sharing your production pool with all accounts (including development and sandbox) means any account can consume production address space. Share pools only with the OUs that should use them. This is governance, not restriction — it ensures the right teams get the right address space.
Key insight: Every IPAM mistake has the same root cause: treating IP address management as a one-time setup rather than an ongoing governance system. IPAM works best when the pool hierarchy, allocation rules, and sharing policies are designed together as a coherent system — not bolted on incrementally as problems arise.
Combining IPAM with other services¶
IPAM is a governance layer that integrates with every service that consumes or manages IP address space. Understanding these integrations helps you build a coherent address management strategy.
| Combination | IPAM provides | Other service provides | Integration pattern |
|---|---|---|---|
| IPAM + Organizations | Centralized IP governance across all member accounts | Account structure, OUs, SCPs, delegated administration | Delegate IPAM admin to networking account; share pools at OU level; monitor compliance org-wide |
| IPAM + RAM | Pool definitions and allocation rules | Cross-account resource sharing | Share IPAM pools with OUs so member accounts can allocate CIDRs without networking team involvement |
| IPAM + Transit Gateway | Non-overlapping CIDRs across all connected VPCs | Regional hub-and-spoke routing | IPAM guarantees every VPC attached to TGW has a unique CIDR; enables route summarization in TGW route tables |
| IPAM + Cloud WAN | Conflict-free address space with regional summarization | Global policy-driven network backbone | Regional pools align with Cloud WAN segments; summarized routes use routing policies |
| IPAM + VPC | Automated CIDR allocation at VPC creation time | The network construct that consumes the allocated CIDR | VPCs reference IPAM pool IDs instead of hardcoded CIDRs; IPAM assigns the next available block |
| IPAM + CloudFormation / Terraform | Pool IDs and allocation APIs | Infrastructure deployment automation | IaC templates reference pool IDs; CIDRs are determined at deploy time, not authoring time |
Key insight: IPAM is not a standalone service. It is the address governance layer that makes every other networking service work correctly at scale. It keeps allocations non-overlapping and summarizable, preventing connectivity failures, re-IPing, and permanent translation workarounds before deployment.
IPAM pricing and cost considerations¶
IPAM is offered in two tiers:
- Free Tier: a single account and Region. Covers BYOIP, Amazon-provided contiguous IPv6 blocks, and Public IP Insights, at no charge.
- Advanced Tier: two or more accounts or Regions. Required for everything this page recommends across an organization: private IPv4 pools, pools in Regions other than the IPAM home Region, sharing pools with other accounts, and Organization-wide monitoring of private addresses.
The Advanced Tier bills hourly per active IP address, private or public:
- An active address is an IP address or prefix on a network interface attached to a resource.
- IPAM charges for every active address it monitors, including addresses outside any pool.
- Unused space in a pool or VPC CIDR costs nothing, so cost grows with running workloads, not with the size of your address plan.
Enabling IPAM Organization-wide brings every member account's addresses into the bill. To keep cost aligned with what you govern:
- Exclude organizational units you don't manage, such as sandbox OUs.
- Limit operating Regions to the ones you use.
- Enable cost distribution to charge each member account for its own active addresses instead of the IPAM owner.
Check the IPAM tab on the Amazon VPC pricing page for current rates and the full tier comparison.
Documentation¶
-
What is IPAM?
Complete service documentation covering concepts, pool management, allocation rules, scopes, and compliance monitoring.
-
How IPAM works
Detailed explanation of IPAM architecture, pool hierarchies, allocation mechanics, and monitoring behavior.
-
IPAM tutorials
Step-by-step guides for creating pools, setting allocation rules, sharing with Organizations, and monitoring compliance.
-
IPAM with AWS Organizations
How to configure delegated administration, cross-account monitoring, and Organization-wide compliance.
-
BYOIP with IPAM
Managing your own public IPv4 address blocks through IPAM's public scope.
-
IPAM launch blog post
Architecture overview and use cases from the original service announcement.
How IPAM relates to the rest of the Foundation¶
IPAM is the governance layer that sits between your CIDR planning strategy and the actual VPC deployments across your Organization. It enforces the addressing decisions you've made and prevents the drift that inevitably occurs when multiple teams manage infrastructure independently.
Relationship to other Foundation topics:
- CIDR Planning: CIDR planning defines your addressing strategy — which ranges to use, how to subdivide them, and how to enable summarization. IPAM implements and enforces that strategy through pools and allocation rules. Without CIDR planning, IPAM has no coherent structure to enforce. Without IPAM, CIDR plans exist only on paper.
- Amazon VPC: VPCs are the primary consumers of IPAM allocations. Every VPC should get its CIDR from an IPAM pool rather than a hardcoded value. IPAM's allocation rules determine what sizes and tags are acceptable for VPC CIDRs.
- Subnets: While IPAM manages VPC-level CIDR allocation, subnet design within the VPC is a separate concern. IPAM ensures the VPC has enough address space; your subnet strategy determines how that space is divided.
- AWS Organizations: Organizations provides the account structure that IPAM governs. Delegated administration, OU-level pool sharing, and cross-account compliance monitoring all depend on a well-structured Organization.
- Regions and Availability Zones: Your Region strategy determines how many regional pools you need and how address space is distributed geographically. IPAM's locale restrictions enforce that distribution.
Relationship to Connectivity:
- Connectivity Within AWS: Transit Gateway and Cloud WAN route between your VPCs; IPAM prevents overlaps so those networks connect without address workarounds.
- Hybrid & Multi-Cloud: On-premises CIDR ranges must be imported into IPAM to prevent AWS allocations from conflicting with existing networks. IPAM's hybrid awareness is essential for any organization with Direct Connect or VPN connectivity.