-
-
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
Support unique route table for outpost routes #697
Comments
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 |
Hi, I need to have a separate route table for the Outpost. Can we reopen this issue Thanks |
hi all, this should be addressed in the next version which is under development here https://github.com/clowdhaus/terraform-aws-vpc-v4/tree/main/modules/subnets |
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?
No
Is your request related to a problem? Please describe.
Outpost support is currently available in the module, however the shared use of the private route table makes using the local gateway in an outpost problematic.
https://docs.aws.amazon.com/outposts/latest/userguide/outposts-networking-components.html
Describe the solution you'd like.
Options
In either case, also add an output for the outpost route table id's.
Describe alternatives you've considered.
Create the outpost subnets outside of this module.
Additional context
I see in #542 a discussion about the difficulties in testing the outpost feature. Perhaps this is a good reason to look into creation of the subnet outside of this vpc module.
The text was updated successfully, but these errors were encountered: