Provide a way to configure other set of default routes to TGW on the spoke subnets about network-orchestration-for-aws-transit-gateway HOT 6 CLOSED

+1 for this, we are currently adding routes manually because default ones do not fit our needs. We have deployed STNO into multiple regions within Landing Zone solution and need different default routes per region. Having an additional route type that allows customization by region would be ideal.

from network-orchestration-for-aws-transit-gateway.

Thanks for opening this feature request. We have added this our backlog.

from network-orchestration-for-aws-transit-gateway.

Actually for us, the ideal would be that the routes added to the spoke subnets would be the propagated routes on the transit gateway route table that they are associated with.

from network-orchestration-for-aws-transit-gateway.

With the release of shared prefix lists, I would prefer this feature uses those to set up the routes to transit gateway so if propagated routes are updated, then we can simply update the prefix list.

from network-orchestration-for-aws-transit-gateway.

We release v2.0 yesterday that now supports custom routes, prefix lists to be added to the VPC route tables (associated with tagged subnets).

from network-orchestration-for-aws-transit-gateway.

Actually for us, the ideal would be that the routes added to the spoke subnets would be the propagated routes on the transit gateway route table that they are associated with.

@alFReD-NSH This seems to be a new feature request unrelated to the original issue. It would great if you could close this issue and open a new issue with this feature request. Thanks.

from network-orchestration-for-aws-transit-gateway.