Understanding Latency Implications of Direct Connect Connection Across AWS Regions

0

Hello AWS Experts,

I am seeking clarification regarding Direct Connect connection regions and their potential latency implications. Here's the scenario:

We currently have a Direct Connect connection established in the US EAST 1 region, utilizing a Transit VIF and DX gateway. However, the majority of our resources, specifically our VPCs, are hosted in the US EAST 2 region. To interconnect these VPCs, we are leveraging a Transit Gateway (TGW) within the US EAST 2 region.

1.My primary concern revolves around the potential latency introduced by this setup. Specifically, I am curious about the impact of utilizing a Direct Connect connection from the US EAST 1 region to connect VPCs located in the US EAST 2 region via the TGW.

I would greatly appreciate your guidance. Thank you for your assistance in advance.

1개 답변
0
수락된 답변

Direct Connect Gateway is a global presence that allows you to use a Direct Connect location to access any other public regions (excluding China) as all networking traffic remains on the AWS global network backbone. Does your setup introduce additional latency compared with having the Direct Connect location in the same region (US-EAST-2)? It sure does. But the question is how significant impact it has on your application which really comes down to the latency requirement of your application. Also if this hybrid connection is business critical, you should consider having multiple direct connect connections in the location, adding additional direct connect locations in the same region for resiliency or even adding additional region for failover. You can find more information regarding Direct Connect resiliency here.

profile pictureAWS
전문가
답변함 2달 전
profile picture
전문가
검토됨 2달 전
profile picture
전문가
검토됨 2달 전

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

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

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