---
title: "Amazon VPC IPAM and Universal DDI Integration"
canonical: "https://docs.infoblox.com/space/BloxOneDDI/1803780139/Amazon+VPC+IPAM+and+Universal+DDI+Integration"
format: markdown
---
This section provides comprehensive, step-by-step instructions for integrating **Amazon Virtual Private Cloud (VPC) IP Address Manager (IPAM)** with **Infoblox Universal DDI (UDDI)**. This integration establishes a centralized and automated mechanism for managing IP address spaces across hybrid and multi-cloud environments. By synchronizing Amazon VPC IPAM with Infoblox IPAM, network administrators gain unified visibility, address utilization insights, and control over overlapping and fragmented IP address spaces. For more information, see *[Integrate VPC IPAM with Infoblox infrastructure](https://docs.aws.amazon.com/vpc/latest/ipam/integrate-infoblox-ipam.html)* on the Amazon website.

Through this integration, Infoblox acts as a **federated IPAM provider**, enabling Amazon VPCs to request IP space dynamically while ensuring consistent governance, allocation efficiency, and avoidance of conflicts. The guide outlines configuration prerequisites, IAM (Identity and Access Management) permissions, discovery setup, synchronization validation, and IP pool provisioning from both the Infoblox and Amazon sides.

Ultimately, this integration helps enterprises enforce **DDI (DNS, DHCP, IPAM)** consistency between cloud-native and on-prem environments, thereby reducing operational overhead, improving audits, and enhancing automation in network provisioning workflows.

The first part of the process is to create a discovery job that automatically syncs Amazon resources (such as subnets and instances) into the Infoblox Portal. Thereafter, administrators can view and manage pools, CIDR ranges, and allocations directly within the unified IPAM interface. In cases where unused ranges need to be deprovisioned, blocks can be safely recycled, ensuring accurate tracking of available capacity.

A key advantage of this integration is the ability to request unique VPC ranges from a federated hybrid realm. Realms act as central authority domains that aggregate address space discovered from multiple sources, including AWS, GCP, and NIOS-X. By using a scope-based token and the *[Next Appropriate Delegation API](https://csp.infoblox.com/apidoc?url=https%3A%2F%2Fcsp.infoblox.com%2Fapidoc%2Fdocs%2FIpamFederation#/next_appropriate_delegation/next_appropriate_delegationCreateNextAppropriateDelegation)*, administrators can allocate CIDR blocks to AWS scopes with the confidence that these ranges are globally unique and managed under Infoblox’s federated model.

This unified approach streamlines collaboration between network and cloud teams, reduces the risk of overlapping allocations, and provides end-to-end visibility into how address space is consumed across hybrid deployments. Ultimately, Infoblox serves as the authoritative source for allocating and governing IP space, while Amazon IPAM remains the operational interface for VPC and subnet provisioning.

The following diagram shows the process of integration between Amazon VPC IPAM and Universal DDI IPAM:

> Macro (drawio)


> ✅ This chapter is focused on Amazon VPC IPAM. If you are looking for Amazon Route 53, go to *[Amazon Route 53](https://infoblox-docs.atlassian.net/wiki/spaces/UniversalAssetInsights/pages/1501299231)*.

The following sub-topics provide more details:

> Macro (children)