By using AWS re:Post, you agree to the Terms of Use
/What is the best practice and downtime for migrating an existing AWS environment to use the Transit Gateway?/

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!

1 Answers
0
Accepted Answer

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.
EXPERT
answered 2 years ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions