Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support manually providing a private IPv4 address for an internal network load balancer #12329

Closed
arnogeurts opened this issue Mar 10, 2020 · 4 comments · Fixed by #11404
Closed
Assignees
Labels
enhancement Requests to existing resources that expand the functionality or scope. service/elbv2 Issues and PRs that pertain to the elbv2 service.
Milestone

Comments

@arnogeurts
Copy link

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • 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
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

AWS supports manually providing a private IPv4 address to the NLB[1], however, this is not yet supported in this Terraform provider. It would be nice if the field "private_ipv4_address" would be added to the "subnet_mapping" block in the "aws_lb" resource.

New or Affected Resource(s)

  • aws_lb

Potential Terraform Configuration

resource "aws_lb" "lb_test" {
  name               = "my-network-load-balancer"
  load_balancer_type = "network"
  internal           = true

  subnet_mapping {
    subnet_id            = aws_subnet.private.id
    private_ipv4_address = "10.0.0.11"
  }
}

References

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

  • #0000
@arnogeurts arnogeurts added the enhancement Requests to existing resources that expand the functionality or scope. label Mar 10, 2020
@ghost ghost added the service/elbv2 Issues and PRs that pertain to the elbv2 service. label Mar 10, 2020
@github-actions github-actions bot added the needs-triage Waiting for first response or review from a maintainer. label Mar 10, 2020
@bflad bflad removed the needs-triage Waiting for first response or review from a maintainer. label Jun 24, 2020
@bflad bflad self-assigned this Jun 24, 2020
@bflad bflad added this to the v2.68.0 milestone Jun 24, 2020
@breathingdust breathingdust modified the milestones: v2.68.0, v2.69.0, v2.70.0 Jun 25, 2020
@breathingdust breathingdust modified the milestones: v2.70.0, v3.1.0 Jul 9, 2020
@bflad
Copy link
Contributor

bflad commented Jul 31, 2020

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. 👍

@ghost
Copy link

ghost commented Aug 7, 2020

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
Copy link

ghost commented Aug 30, 2020

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!

@ghost ghost locked and limited conversation to collaborators Aug 30, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement Requests to existing resources that expand the functionality or scope. service/elbv2 Issues and PRs that pertain to the elbv2 service.
Projects
None yet
4 participants