IP Address Management That Ships the Policy That Enforces It

Amazon VPC IPAM with a top-level pool, a pool per region with netmask bounds and required tags, and optional sharing through AWS RAM. IPAM forces nothing on its own - a VPC can still take a hand-typed CIDR - so the module outputs the SCP AWS documents for requiring a pool. The provider defaults to the Advanced tier, billed per active IP, so the tier has no default here.

This is the operations reference: version drift, dependants and neighbours. For what the module provisions, its inputs and outputs, and how to buy it, see the catalogue entry.

terraformAWSNetworking & VPCv1.0.0static-validated

Provider drift

This artifact declares no Terraform provider requirements, so there is nothing to drift. Provider freshness applies to Terraform and OpenTofu modules.

What depends on this

No reference architecture names this module, so changing it affects only configurations that reference it directly.

Nearest alternatives

Same cloud, same category. These are what you would weigh against it without changing provider.

A Service Network where the Network Is Not the Permission A VPC Peering Accepted in One Apply, with DNS Across It and Routes on Both Sides Client VPN with Per-Group Authorization Cloud Map Service Registry Cloud WAN Global Network and Segments Direct Connect, and the Fact that It Is Not Encrypted NAT Gateways for an Existing VPC, One per Zone, with the Private Routes Written Network ACLs with the Return Rules They Need

The same job on other clouds

This module has no cross-cloud peer set in the catalogue, so there is no portability comparison to draw.

Installing it

module "aws_ipam" {
  source  = "www.iac-bazaar.com/iac-bazaar/aws-ipam/aws"
  version = "1.0.0"
}

A registry token is required for the download itself. Installing through the registry protocol has the two credential steps.