Open tzahibwix opened 1 year ago
Voting for Prioritization
Volunteering to Work on This Issue
For some added context, there is confusion in ec2 regarding the term "pool" there is both an "ipam public pool" and an "ec2 public pool". Currently you can create an ipv4 ipam public pool, you cannot:
aws ec2 create-public-ipv4-pool
)aws ec2 provision-public-ipv4-pool-cidr
)aws ec2 allocate-address
)aws ec2 advertise-byoip-cidr
)There is some overlap with this issue also: https://github.com/hashicorp/terraform-provider-aws/issues/17425
Unfortunately, I will not be able to implement this feature request because I do not have access to a public ipv4 for testing.
Hi @drewmullen, I will be able to help you and provide a public prefix to test and implement the new resources.
@drewmullen Just FYI, the provision of IPs to the public ec2-public-ipv4-pool allows you to provision any from /32 to /24, but the de-provision process is only /32, that means that if you provisioned /24 to a public ec2 ipv4 pool, to de-provision the subnet you will have to do 255 API calls, one for each /32 address from the /24 prefix.
Usually I can work around missing terraform features by writing cloudformation inside terraform, but I cannot find cloudformation specs for these resources either.
Do others have a good way to implement these as IaC or can point me to the right CloudFormation I could import into my terraform?
Description
As of today, it is not possible to create IPv4 pool, this option available only through AWS CLI and AWS API.
In order to use BYOIP with IPAM, we can create the public IPAM pool with Terraform, but the last steps of creating IPv4 pool in the member account and privosion them to the IPv4 pool, are available only through AWS CLI/API (Steps 8 and 9 in the following AWS doc - https://docs.aws.amazon.com/vpc/latest/ipam/tutorials-byoip-ipam-ipv4.html)
Affected Resource(s) and/or Data Source(s)
aws_vpc_ipam_pool
Potential Terraform Configuration