Ability to manually assign a private static IP address from each subnet to an AWS NLB

[ghost]

This issue was originally opened by @mafitconsulting as hashicorp/terraform#24025. It was migrated here as a result of the provider split. The original body of the issue is below.

---

Current Terraform Version

Terraform v0.12.19

Use-cases

AWS allows you to create an internal load balancer, from that, you can manually assign a private IP address from the IPv4 range of each subnet instead of letting AWS assign one. I cannot see any functionality documented which allows the "aws_lb" resource to implement this feature.
AWS docs below

[https://docs.aws.amazon.com/elasticloadbalancing/latest/network/create-network-load-balancer.html]

Attempted Solutions

No solution attempted, because the functionality does not seem to exist. Therefore, the NLB defaults to AWS assigning a random IP from the subnet range

Proposal

Implement new argument for the aws_lb resource to manually assign a private static ip address for each subnet range

References

[ewbankkit]

I think this is the same use case as #11674 and #11044.

[bflad]

Hi folks 👋 This functionality has been merged and will release with version 3.1.0 of the Terraform AWS Provider, next Thursday. Thanks to @kadenlnelson for the implementation. 👍

[mafitconsulting]

Great news cheers

[ghost]

This has been released in version 3.1.0 of the Terraform AWS provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template for triage. Thanks!

[ghost]

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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!