Default Route (All-Traffic (0/0)) not propagating to respective attached subnet's route table

aws-solutions / network-orchestration-for-aws-transit-gateway

The Network Orchestration for AWS Transit Gateway solution automates the process of setting up and managing transit networks in distributed AWS environments. It creates a web interface to help control, audit, and approve (transit) network changes.

https://aws.amazon.com/solutions/implementations/serverless-transit-network-orchestrator/

Apache License 2.0

121 stars 52 forks source link

Default Route (All-Traffic (0/0)) not propagating to respective attached subnet's route table #10

Closed mariomic-maker closed 4 years ago

mariomic-maker commented 4 years ago

Hi,

I have setup the hub and spoke successfully. However when attaching an existing subnet of an associated VPC to the transit gateway (using the Attach-to-tgw tag) , the route table of that subnet is not updated to point all traffic to the TGW (as set in the parameters on the hub stack creation i.e. All-traffic (0/0)

Am I missing something here?

Would appreciate if something can assist with this please.

groverlalit commented 4 years ago

@mariomic-maker Thanks for reaching out to us. Can you please confirm that the subnet you tagged didn't already have an existing default route in the the associated route table? By design, the solution does no overwrite existing default routes.

maykays commented 4 years ago

Closing issue. Please confirm that the subnet you tagged didn't already have an existing default route in the the associated route table, and re-open if the issue persists.