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

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

Closed
mafitconsulting opened this issue Feb 4, 2020 · 2 comments

Comments

@mafitconsulting
Copy link

mafitconsulting commented Feb 4, 2020

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

@ghost
Copy link

ghost commented Feb 4, 2020

This issue has been automatically migrated to hashicorp/terraform-provider-aws#11887 because it looks like an issue with that provider. If you believe this is not an issue with the provider, please reply to hashicorp/terraform-provider-aws#11887.

@ghost
Copy link

ghost commented Mar 29, 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 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.

@ghost ghost locked and limited conversation to collaborators Mar 29, 2020
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants