-
-
Notifications
You must be signed in to change notification settings - Fork 233
Support multiple route tables for a single tgw #139
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
Comments
@ronaldour I don't think so; this PR includes additional vpc routes but not more tgw route tables. I also would like to create multiple tgw route tables for a single tgw, I'm working on creating a single exit point VPC architecture. |
@marcelomanchester sorry wrong PR number, looks like 113 has a big refactor of the module with breaking changes and potentially solving multiple issues |
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 |
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. |
Is your request related to a new offering from AWS?
Is this functionality available in the AWS provider for Terraform?
I assume we've always been able to associate more than one tgw route table with a tgw?
Is your request related to a problem? Please describe.
We want to associate multiple tgw route tables to a single tgw. We also want to manage routes for each of the tgw route tables.
Within our network account we want to create a tgw per region. Within the region we will create "environment" VPCs, eg prod, nonprod, uat. Each VPC will attach to the tgw but each environment will be routed using a table dedicated to the environment. Thus each tgw will have four route tables, the default, prod, nonprod, and uat.
Describe the solution you'd like.
It would be great if we could create n tgw route tables for a tgw and associate attachments with one of the tgw route tables.
Describe alternatives you've considered.
A main module and then one module instance per "environment".
This is unworkable, because tgw route tables are only managed when
create_tgw
andcreate_tgw_routes
are bothtrue
.Additional context
The text was updated successfully, but these errors were encountered: