Orchestration for multiple TGWs and multiple regions

[chrystalis]

There does not seem to be a clear solution for how to use STNO in an environment with multiple TGWs and/or multiple regions. The documentation points out the regional nature of some of the services, and notes that the templates all need to be deployed in the same region. Is the expectation, then, that a separate, full STNO deployment would be required for every region with a TGW to manage? And, if there are multiple TGWs in the same region, can a separate STNO be deployed for each? Is this even possible? Even if so, it would likely be unwieldy and cumbersome.

I would like to see STNO natively support multiple TGW hubs and regions. For example, when there are multiple TGWs in the same region, the attachment orchestration could perhaps be done by specifying a TGW ID in the value to the 'Attach-to-tgw' tag. Or, maybe each TGW could have a optional prefix in order to distinguish the route tables - e.g. TGW1_Flat vs TGW2_Flat. These should be able to interface with a single web interface for approvals and audit history, with filtering to optionally show all records or only those related to a single TGW.

For multiple region support, I would like to be able to deploy just one global template for the hub components, with a single web interface and set of rules etc. Specifying the regions to deploy to could be done via parameters (allowing for an environment to grow over time). Alternately, perhaps the regional components could be split out into a separate template that could be deploy as a stack set.

[rakshb]

Thanks for your request. We will add this to the backlog and evaluate it for a future release