IP Address Management (IPAM): Tools and Best Practices
As networks grow, tracking which IP addresses and CIDR blocks are allocated, in use, or available becomes critical. IPAM tools — from spreadsheets to dedicated platforms — prevent conflicts and enable automation.
In a small network, a mental model or a simple spreadsheet tracks your IP allocations adequately. In a network with hundreds of VPCs, multiple cloud accounts, on-premises data centres, and office networks, ad hoc tracking fails fast. IP conflicts, double allocations, and "who owns this /24?" questions become daily occurrences. IPAM — IP Address Management — is the discipline (and tooling) that prevents this.
What IPAM Solves
IPAM provides a single source of truth for your organisation's IP address space:
- Which CIDR blocks have been allocated to which teams, regions, or services
- Which subnets are in use, which are reserved, and which are available
- Which individual IP addresses are assigned to which hosts
- Historical allocation records for auditing
Without IPAM, two teams independently allocate the same /24 for different VPCs, only discovering the conflict when they try to peer them. With IPAM, a VPC CIDR allocation is a request against a managed pool that prevents overlap.
The Spreadsheet Phase
Most organisations start with a spreadsheet. This works for small to medium networks but breaks down quickly: no concurrent editing controls, no validation, no integration with cloud APIs, no audit trail. A well-structured spreadsheet at least tracks: supernet, allocated subnet, assigned team, region, purpose, and date. Use the CIDR calculator to verify boundaries before recording an allocation.
Dedicated IPAM Tools
- NetBox (open source) — the most popular choice for infrastructure teams. Handles IP prefixes, address assignments, racks, devices, and VLANs. Has a REST API and GraphQL interface for automation.
- phpIPAM (open source) — lighter than NetBox, web-based, good for smaller teams.
- AWS VPC IPAM — native AWS tool for managing VPC CIDR allocations across accounts and regions within an AWS Organization. Prevents duplicate VPC CIDRs and provides allocation governance.
- Infoblox / BlueCat — enterprise-grade, integrates with DNS and DHCP, expensive.
AWS VPC IPAM Specifically
If you run multiple AWS accounts (as most organisations should, for isolation), AWS VPC IPAM is worth considering. You define pools — hierarchical CIDR blocks — and teams request VPC CIDRs from those pools. The service enforces uniqueness, tracks allocation history, and integrates with AWS Organizations so you see all allocations across all accounts in one place. See our VPC CIDR selection guide for how to plan the address space before setting up IPAM.
Starting Your IPAM Practice
Start simple: document your supernets (the large blocks like 10.0.0.0/8 you have reserved for infrastructure), then document every subnet you have carved from them. Even if your tool is a shared spreadsheet, the habit of recording allocations before deploying is the most important practice. Migrate to a proper IPAM tool when the spreadsheet becomes a liability — typically around 50–100 subnets.