v2 to v3 upgrade and providing existing global network id

[Andreas Zoellner]

What were you initially searching for in the docs?

I'm working through upgrading from v2 to v3. This mentions to copy over the global network id and the existing transit gateway id, however, since I have the stack deployed in multiple regions as part of a Custom Control Tower Configuration [1], I have multiple global network ids and transit gateway ids. It is unclear if I need to now split the stackset deployment in one per region or add a mapping to the CF template to pick the right global network fo reach region.

Provide the existing global network id: copy the global network created by v2 deployment (leave blank if v2 did not create global network).

Is this related to an existing part of the documentation? Please share a link
https://docs.aws.amazon.com/solutions/latest/serverless-transit-network-orchestrator/update-the-stack.html
Describe how we could make it clearer
Cover multi region scenario for STNO upgrade path
If you have a proposed update, please share it here

[1] https://controltower.aws-management.tools/automation/cfct/#setup-central-networking-using-serverless-transit-network-orchestrator-stno-advanced-lab

[Lalit Grover]

Thanks for raising this issue. Closing this duplicate issue as it was already raised in #50. We plan to update the documentation in the next release.