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

Private IP address selection for internal NLBs #11044

Closed
ewbankkit opened this issue Nov 27, 2019 · 3 comments · Fixed by #11404
Closed

Private IP address selection for internal NLBs #11044

ewbankkit opened this issue Nov 27, 2019 · 3 comments · Fixed by #11404
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

@ewbankkit
Copy link
Contributor

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 "me too" comments, 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

You can now select the private IPv4 address that is used for your internal-facing Network Load Balancer, on a per-subnet basis.

New or Affected Resource(s)

Potential Terraform Configuration

# Copy-paste your Terraform configurations here - for large Terraform configs,
# please use a service like Dropbox and share a link to the ZIP file. For
# security, you can also encrypt the files using our GPG public key.

References

Blog post.

Requires AWS SDK v1.25.42:

@ewbankkit ewbankkit added the enhancement Requests to existing resources that expand the functionality or scope. label Nov 27, 2019
@github-actions github-actions bot added the needs-triage Waiting for first response or review from a maintainer. label Nov 27, 2019
@bflad bflad added service/elbv2 Issues and PRs that pertain to the elbv2 service. and removed needs-triage Waiting for first response or review from a maintainer. labels Jan 2, 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
Development

Successfully merging a pull request may close this issue.

3 participants