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년 전672회 조회
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년 전

로그인하지 않았습니다. 로그인해야 답변을 게시할 수 있습니다.

좋은 답변은 질문에 명확하게 답하고 건설적인 피드백을 제공하며 질문자의 전문적인 성장을 장려합니다.

질문 답변하기에 대한 가이드라인

관련 콘텐츠