Direct Connect Connection Ownership Transfer

0

My customer has got 2 Direct Connect connections(active/passive) setup in payer master account. The current state network architecture is like :-

DxCon(inside payer master) --> PrivateHostedVIF(hosted VIF to member account) --> DxGWY(inside member account)--> VGW -->VPC

AWS has been engaged to deploy the LZ solution. We would like to transfer ownership of "DxCons" from payer master to a new network account(created via ALZ/CT).

As per the publicly available doco "DxCon transfer" can be done by opening AWS support cases. I would like to understand the impact of this DxCon transfer on current VIFs. My understanding is that VIFs have to be recreated under new network account.

Has anyone done something similar in the past ? What would be the recommended DxCon migration strategy with minimal impact on customer workloads.

Current Org Setup Details At present, The customer has got 9 accounts in total with 1 Payer master and 8 member accounts. Out of the 8 member accounts, 2 accounts are prod having live workloads

AWS
質問済み 4年前395ビュー
1回答
0
承認された回答

You don't need to do anything with Hosted VIFs. They remain as is. From your own doco link:

"Note: This ownership transfer is only for the DX connection. Any virtual interfaces associated with the DX connection are not part of the transfer, and remain associated with the AWS account for which they were created."

Done similar in the past and it is a standard procedure

profile pictureAWS
エキスパート
回答済み 4年前

ログインしていません。 ログイン 回答を投稿する。

優れた回答とは、質問に明確に答え、建設的なフィードバックを提供し、質問者の専門分野におけるスキルの向上を促すものです。

質問に答えるためのガイドライン

関連するコンテンツ