STNO Routes propagation to Route tables as part of vpc creation

[sai337]

We have been using the STNO in our organization since 2020 and the version is v2.0.0.

Here the issue is we will add the stno tags to vpc and subnets as part of our vpc automation which will create 3 public 3 private with route tables for each of the subnet.

We have 500 + accounts in org and its gonna increase in near future

Once a subnet get created it comes with stno tags, as the 3 subnets get created almost at the same time the TGW attachment is not able get the 3 subnets for its attachment hence the routes are not propagating to route tables properly.

We also observed that after two subnets propagation in to TGW attachment vpc of the account spoke account getting a tag as VPC has been attached to the Transit Gateway before having the 3rd subnet propagation and its getting tag as vpc is already attached to TGW.

We used to do this (adding tags to subnets in spoke account ) manually subnet by subnet after the routes propagated each route table successfully which was working fine but wanted to automate this process and added those tags in cloudformation vpc template.

we thought of adding some custom logic that routes has to propagate after successful attachment of subnet by subnet but thought check here before doing it.

Is there any best practice or issue reported on this by other users, how can we get this resolved to get those added and propagated without human intervention.

[gockle]

Hi @sai337

Thanks for providing the details of the issue, we are looking into this issue.