It is important that you specify the ipam_scope_name
attribute to match either "public_default_scope", "private_default_scope", or exact match to your vpc_ipam.scopes.name
input on the first module call. Once you've created your scopes by name, then you can reference by id in subsequent module calls. You may also provide ipam_scope_id
instead of ipam_scope_name
. The two are mutually exclusive, do not provide both.
Managing a hierarchy of pools can be a bit tricky. You'll need to call the module successively to build up the structure, chaining the outputs together.
Name | Version |
---|---|
terraform | >= 1.3 |
aws | >= 4.40.0 |
Name | Version |
---|---|
aws | >= 4.40.0 |
Name | Type |
---|
Name | Description | Type | Default | Required |
---|---|---|---|---|
vpc_ipam | Object of inputs for all IPAM configuration resources | object({ |
n/a | yes |
Name | Description |
---|---|
ipam | Object of all AWS VPC IPAM |
pool_cidr | Map of VPC IPAM Pool Cidrs objects |
pools | Map of VPC IPAM Pool Objects |
scopes | Map of VPC IPAM Scope objects |