In AWS, you first access the IPAM via the web-based management console, AWS CLI, SDK, or query API. You then need to configure permissions for the IPAM via the IPAM VPC service to allow for the management and monitoring of networking resources related to AWS organizations and accounts. You then create the “IPAM” (including selecting the operating region). The AWS IPAM has default usage quotas though requests can be made to increase them. The IPAM in Micetro integrates directly with your AWS accounts to give a unified view of your whole cloud and on-premises IP address space. This effectively relieves the need to use the AWS IPAM at all while dramatically simplifying operations in favor of more holistic address management.

In most IPAMs, the UI (User Interface) or an API is used to administer IP addresses, containers, and network ranges. In AWS IPAM, once the IPAM and IAM permissions have been created, CIDR blocks and pools must also be created and provisioned to regional containers before the VPC, and IP pool details can be entered into the IPAM. When using the Micetro IPAM it syncs bidirectionally and automatically with AWS to provide a single pane of glass (or API endpoint) for provisioning IP records and VPCs across your cloud footprint, thus removing the need for, and cost of, the AWS IPAM service.

Unused IP addresses and ranges should always be released and updated in an IPAM to ensure continued and accurate capacity and IP management. Additionally, clean and correct boundaries are required for routing and security to ensure adequate control and continued security intelligence in an IP space. Whether interfaces, devices, or infrastructure ranges are modified or decommissioned, IP records must be kept up to date to avoid operational mistakes, incorrect assumptions, or wasteful allocations.

AWS IPAM is a tool for IP Address Management in relation to the allocation, tracking, and management of IP address space records such as CIDR (Classless Interdomain Routing) blocks. A VPC is a virtual network and provides a container for compute assets and services based on network characteristics and boundaries. The AWS IPAM can be used to track and enforce certain criteria, like using specific IP pools when creating a new VPC.

Rather than configuring the AWS IPAM separately and having multiple teams learn to use it independently (including being subject to additional IAM permissions, costs, and quotas), when configuring the simple Micetro integration to AWS, all the AWS VPC and IP records are automatically and bidirectionally synchronized to Micetro’s IPAM which becomes your single SoT (Source of Truth). Micetro runs as an overlay service and provides a unified view of all your cloud networks' IP space, including your on-premises networks, DNS, and DHCP services. Control all your IP space with a unified and frictionless DDI (DNS, DHCP, IPAM) solution.