localstack
feature request: Support VPC IP Address Manager (IPAM)
Is there an existing issue for this?
- [X] I have searched the existing issues
Feature description
Amazon VPC IP Address Manager (IPAM) is a VPC feature that makes it easier for you to plan, track, and monitor IP addresses for your AWS workloads. You can use IPAM automated workflows to more efficiently manage IP addresses.
- https://docs.aws.amazon.com/vpc/latest/ipam/what-it-is-ipam.html
Supporting IPAM in LocalStack would remove one of the few remaining cases where we have to provide a fundamentally different config for LocalStack vs production, rather than just passing in a few different config values.
Here is the list of available operations: https://docs.aws.amazon.com/AWSEC2/latest/APIReference/operation-list-ipam.html
A minimum implementation may require following operations:
AllocateIpamPoolCidr
AssociateIpamResourceDiscovery
CreateIpam
CreateIpamPool
CreateIpamScope
CreateIpamResourceDiscovery
CreatePublicIpv4Pool
DescribeIpamPools
DescribeIpams
DescribeIpamResourceDiscoveries
DescribeIpamResourceDiscoveryAssociations
DescribeIpamScopes
DescribePublicIpv4Pools
For our specific use case we’re using the following Terraform resources with private IP scope only:
aws_vpc_ipamaws_vpc_ipam_poolaws_vpc_ipam_pool_cidraws_vpc_ipam_pool_cidr_allocationaws_vpc_ipam_pooldata.aws_vpc_ipam_pool
🧑‍💻 Implementation
No response
Anything else?
No response
Hello 👋! It looks like this issue hasn’t been active in longer than five months. We encourage you to check if this is still an issue in the latest release. In the absence of more information, we will be closing this issue soon. If you find that this is still a problem, please feel free to provide a comment or upvote with a reaction on the initial post to prevent automatic closure. If the issue is already closed, please feel free to open a new one.
Hello 👋! It looks like this issue hasn’t been active in longer than five months. We encourage you to check if this is still an issue in the latest release. In the absence of more information, we will be closing this issue soon. If you find that this is still a problem, please feel free to provide a comment or upvote with a reaction on the initial post to prevent automatic closure. If the issue is already closed, please feel free to open a new one.
For a minimum complete implementation we also require these API operations.
ProvisionIpamPool
ProvisionPublicIpv4PoolCidr
EnableIpamOrganizationAdminAccount
DisableIpamOrganizationAdminAccount
+1 this is a big blind spot for infrastructure teams trying to test IPAM allocations.
Hello 👋! It looks like this issue hasn’t been active in longer than five months. We encourage you to check if this is still an issue in the latest release. In the absence of more information, we will be closing this issue soon. If you find that this is still a problem, please feel free to provide a comment or upvote with a reaction on the initial post to prevent automatic closure. If the issue is already closed, please feel free to open a new one.