[Enhancement]: Support for the new AWS IPAM pool of Amazon supplied public IPs for contiguous Elastic IP (EIP) allocation

[mhaswell-work]

Description

AWS now supports IPAM Pools of Amazon provided contiguous public IPs available to allocate to EC2 Elastic IPs in order to provide a simple range for third party whitelisting.

e.g. using the AWS CLI ( v2.17.42 ):

$ aws ec2 allocate-address --ipam-pool-id ipam-pool-085cda2853ce8a1bb
{
    "PublicIp": "26.96.32.28",
    "AllocationId": "eipalloc-078faaf8e6ffe6a48",
    "PublicIpv4Pool": "ipam-pool-085cda2853ce8a1bb",
    "NetworkBorderGroup": "eu-central-1",
    "Domain": "vpc"
}

Affected Resource(s) and/or Data Source(s)

Elastic Ips are created using (for example):

resource "aws_eip" "new_eips" {
  instance = null
}

Potential Terraform Configuration

Similarly to the existing optional arguments public_ipv4_pool for IPAM pools for VPC Eips, or customer_owned_ipv4_pool for Customer provided IPv4 ranges:

resource "aws_eip" "new_eips" {
  instance = null
  ipam_ipv4_pool = ipam-pool-085cda2853ce8a1bb
}

References

AWS Docs on manually creating a pool and associating it with EC2 instances: https://docs.aws.amazon.com/vpc/latest/ipam/tutorials-eip-pool.html

Would you like to implement a fix?

No

[github-actions]

Community Note

Voting for Prioritization

• Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
• Please see our prioritization guide for information on how we prioritize.
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.

Volunteering to Work on This Issue

• If you are interested in working on this issue, please leave a comment.
• If this would be your first contribution, please review the contribution guide.

[ewbankkit]

@mhaswell-work Thanks for raising this issue.
It has already been noticed in #39080. I'm going to close this one as a duplicate so that we can concentrate discussion in the linked issue.
Please add any additional comments there.

[github-actions]

Warning

This issue has been closed, meaning that any additional comments are hard for our team to see. Please assume that the maintainers will not see them.

Ongoing conversations amongst community members are welcome, however, the issue will be locked after 30 days. Moving conversations to another venue, such as the AWS Provider forum, is recommended. If you have additional concerns, please open a new issue, referencing this one where needed.

[github-actions]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.