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

[Enhancement]: NAT Gateway support for Secondary EIP allocation IDs #29471

Closed
adampie opened this issue Feb 17, 2023 · 6 comments · Fixed by #31778
Closed

[Enhancement]: NAT Gateway support for Secondary EIP allocation IDs #29471

adampie opened this issue Feb 17, 2023 · 6 comments · Fixed by #31778
Labels
enhancement Requests to existing resources that expand the functionality or scope. prioritized Part of the maintainer teams immediate focus. To be addressed within the current quarter. service/vpc Issues and PRs that pertain to the vpc service.
Milestone

Comments

@adampie
Copy link

adampie commented Feb 17, 2023

Description

NAT Gateways now support associating up to 8 IPs (1 primary IPv4 address and 7 secondary IPv4 addresses) to increase the concurrent connection limit to a single destination.

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

  • aws_nat_gateway

Potential Terraform Configuration

resource "aws_nat_gateway" "example" {
  allocation_id            = aws_eip.example.id
  secondary_allocation_ids = []
  subnet_id                = aws_subnet.example.id

  tags = {
    Name = "gw NAT"
  }

  # To ensure proper ordering, it is recommended to add an explicit dependency
  # on the Internet Gateway for the VPC.
  depends_on = [aws_internet_gateway.example]
}

References

Would you like to implement a fix?

No

@adampie adampie added enhancement Requests to existing resources that expand the functionality or scope. needs-triage Waiting for first response or review from a maintainer. labels Feb 17, 2023
@github-actions
Copy link

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.

@github-actions github-actions bot added the service/vpc Issues and PRs that pertain to the vpc service. label Feb 17, 2023
@johnsonaj johnsonaj removed the needs-triage Waiting for first response or review from a maintainer. label Feb 23, 2023
@ewbankkit
Copy link
Contributor

One potential source of problems here will be how to manage both auto-assigned and manually assigned private IPv4 addresses.

@arko95
Copy link

arko95 commented Mar 21, 2023

Secondary IP added to the NAT GW are EIP so this is public IPv4 address and not private . can we create a new ressource "aws_nat_gateway_secondary_ip" that will allow adding those secondary IP ?

@jtomaszon
Copy link

Hello guys, where are we on this feature request? We are suffering right now because of not enough NAT power

@breathingdust breathingdust added the prioritized Part of the maintainer teams immediate focus. To be addressed within the current quarter. label Jul 25, 2023
@justinretzolk justinretzolk added this to the v5.10.0 milestone Jul 27, 2023
@github-actions
Copy link

This functionality has been released in v5.10.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. Thank you!

@github-actions
Copy link

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 27, 2023
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. prioritized Part of the maintainer teams immediate focus. To be addressed within the current quarter. service/vpc Issues and PRs that pertain to the vpc service.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants