Hi Faizal,
At the end of the first of the video, as much as I am able to recollect, both Transit Gateway and Direct Connect Gateway are doing similar functions. What exactly is the difference between the two? Please elaborate.
They both serve completely different functions. In AWS, over the years you might see some service functions overlap with each other on certain features but they aren’t intended for the same use cases.
A Transit Gateway was brought in as a replacement for the need to create transit VPCs to enable internal communication between VPCs. This is the primary functions of TGW. Over the years, functionality such as connecting it to your on-prem via VPNs or connecting it to your DX has also been added, but at the core, it’s a service that allows you to communicate between VPCs.
A Direct Connect Gateway on the other hand allows you to interconnect multiple Direct Connect Connections(DX) which is a kind of physical connection you get directly into the AWS network backbone. So you get low latency high speed and high bandwidth connectivity between your on-premises and AWS core network.
I hope this gives a little bit of clarity.
Yes. It does clarify. Thank you.
Hello Sridhar. When you say first video, are you referring to the intro? I believe I go into more depth on these in the VPC section video.
Yes. I had this doubt after going through Module 7 – VPC (Session Video).