-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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
Comments
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
One potential source of problems here will be how to manage both auto-assigned and manually assigned private IPv4 addresses. |
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 ? |
Hello guys, where are we on this feature request? We are suffering right now because of not enough NAT power |
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! |
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. |
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)
Potential Terraform Configuration
References
Would you like to implement a fix?
No
The text was updated successfully, but these errors were encountered: