Support secondary ip addresses for nat gateway #1108
Labels
Comments
|
Duplicate #1005? |
|
I'm also waiting for this for a while. I see it being worked on here: #1109 but not moving forward. This is actually a big pain point for us right now ;-( |
|
@bryantbiggs @AlexisColes Is there something that can be done to unblock the merge? The current issue with the computed values as keys in maps could maybe be fixed in another way? Thanks |
|
This issue has been automatically marked as stale because it has been open 30 days |
|
This issue was automatically closed because of stale in 10 days |
|
Please re-open this issue. This is really needed. Thanks. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your request related to a new offering from AWS?
The functionality is there, I don't know when it was introduced, but I presume for at least a year.
Is your request related to a problem? Please describe.
We are being rate limited by github based on IP address from one of our aws accounts, in order to work around this problem we added secondary ip addresses to our natgateways. We have no way of configuring the vpc module to reflect this desired configuration.
Describe the solution you'd like.
Expose configuration for secondary ip addresses to allow more than 1 ip address to be configured per nat-gateway
Describe alternatives you've considered.
configuring the nat-gateway outside of this module.
Additional context
The text was updated successfully, but these errors were encountered: