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.

Ali Md
已提問 2 個月前檢視次數 515 次
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 個月前

您尚未登入。 登入 去張貼答案。

一個好的回答可以清楚地回答問題並提供建設性的意見回饋,同時有助於提問者的專業成長。

回答問題指南