-
-
Notifications
You must be signed in to change notification settings - Fork 4.5k
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
Create only one private route table when single_nat_gateway is true #82
Comments
I just ran into this myself, I only needed a single NAT instance and therefore assumed that would only create a single routing table across all the private subnets (3 subnets in my case). Unfortunately I was still left with 3 private routing tables. I'd like to see this module support a single private routing table 👍 |
Any update on this? |
@yardensachs I should be able to take a look at this during upcoming weekends. |
Apparently, it will be during next weekends... sorry for the delay! |
Thanks |
What's the use case where you would create multiple private subnets across azs when using only a single nat. |
@mhumeSF because you may want to launch instances across multiple azs |
Sorry, I'm an idiot. I see now. Just be aware that traffic between the nat and instances across AZs will incur cross-az data charges. (A cautionary tale) |
Sorry for the delay, finding time to do a proper review and manual testing is not the easiest part of the work. Patience and nudge usually help :) v1.29.0 has been just released. |
@antonbabenko 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. 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. |
Right now, this module is creating a route table for every subnet even when there is a single NAT Gateway. This is unnecessary, as all the route tables are using the same NAT Gateway, and multiple subnets can be associated with the same route table.
I propose that when the user elects to use a single NAT Gateway, all the private subnets should be associated with just a single private route table.
The text was updated successfully, but these errors were encountered: