What is the best practice and downtime for migrating an existing AWS environment to use the Transit Gateway?

0

What is the best practice and downtime for migrating an existing AWS environment to use the Transit Gateway?
For example, if there are currently separate VPCs, each with access to the Internet, which will be migrating to use the Transit Gateway with traffic sent through a central egress VPC to the Internet, what is the best practice for migrating this environment and the downtime involved? Thanks!

已提问 4 年前664 查看次数
1 回答
0
已接受的回答

You can accomplish this migration with zero downtime.

Steps:

  1. Setup the TGW, attach the desired VPCs and configure the TGW route tables. (Don't update the VPC route tables yet)
  2. Setup the central egress VPC to the Internet
  3. (Optional) Create a test VPC, attach it to the TGW and test that the central egress functionality works as expected
  4. Change the old VPC route tables and point 0.0.0.0/0 to the TGW instead of wherever it points today. The trick here is that you cannot create a second 0.0.0.0/0 entry. (Therefore create 0.0.0.0/1 and 128.0.0.0/1 and point them both to the TGW, then delete the old 0.0.0.0/0 route, create the new 0.0.0.0/0 entry and last but not least delete the two x/1 entries.)
  5. (Optional) Remove any VPC peering that you no longer need.
profile pictureAWS
专家
已回答 4 年前

您未登录。 登录 发布回答。

一个好的回答可以清楚地解答问题和提供建设性反馈,并能促进提问者的职业发展。

回答问题的准则