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년 전

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

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

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