Skip to content
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

Override DefaultRoute #126

Open
mancinifm opened this issue Aug 19, 2024 · 2 comments
Open

Override DefaultRoute #126

mancinifm opened this issue Aug 19, 2024 · 2 comments
Labels
enhancement New feature or request

Comments

@mancinifm
Copy link

mancinifm commented Aug 19, 2024

We have set DefaultRoute hub parameter to All-Traffic (0/0), however for one of our VPCs we wish to override this so that the tagged subnet RT points to a more specific network.

Is this possible?

@mancinifm mancinifm added the enhancement New feature or request label Aug 19, 2024
@gsingh04
Copy link
Member

Hello @mancinifm thank you for your query.

There is a CloudFormation parameter which you can use to change the default configuration. Review parameter under VPC Route Table Settings, Choose the type of destination for target Transit Gateway. This parameter can be adjusted for Custom-Destinations. With custom destinations, you can provide either CIDR blocks or managed prefix-lists. See more details here.

One thing to note, the change will be applied to all VPCs moving forward.

@mancinifm
Copy link
Author

mancinifm commented Aug 20, 2024

Thank you for the info.

It sounds like STNO intends for all VPCs in the solution to use the same CIDR for the TGW route, and the only way to support having this route differ between VPCs is to set DefaultRoute to Configure-Manually and for each new VPC attached, manually set the route.

What would be nice is if there was an additional tag for tagged subnets called something like tgw-cidr which allows me to override the default value on a per-VPC basis.

However this is not a deal breaker and I am happy for you to close this issue if my understanding of the situation is correct.

Appreciate your response.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants