We have seen IPSEC Site-to-Site VPN, a nice extension to that is Direct Connect offering. In IPSEC VPN, we connected to AWS VPC securely over the internet, in Direct Connect we have a cable termination onto our Data Center premises which directly connects to AWS Infrastructure and no internet service providers are needed for this to happen.
AWS Direct Connect - Image Credits: :https://docs.aws.amazon.com/directconnect/latest/UserGuide/Welcome.html
Advantages:
We basically start with a Connection, pretty much self-explanatory
A Connection has the below requirements
Requirement | Comment |
---|---|
Connection Type | Fibre |
Fibre Type | Single-Mode |
Transceiver | 1000BASE-LX for1Gbps. 10GBASE-LR for 10Gbps 100GBASE-LR4 for 100Gbps |
802.1Q VLAN | All through the path must be supported |
Protocol | BGP with MD5 authentication |
Optional Protocol | BFD for faster protocol convergence |
MTU | 1522 or 9023 |
Ref: https://docs.aws.amazon.com/directconnect/latest/UserGuide/Welcome.html
Ref:https://docs.aws.amazon.com/directconnect/latest/UserGuide/WorkingWithVirtualInterfaces.htmlSo, once we have a connection setup, everything revolves around VIF - Virtual Interface.
Direct Connect can be divided into two parts
Ref: https://aws.amazon.com/blogs/networking-and-content-delivery/introducing-aws-direct-connect-sitelink/
Requirement - Direct Connect Gateway - Global and Highly available AWS Service
AWS Site Link - Image Credit - https://aws.amazon.com/blogs/networking-and-content-delivery/introducing-aws-direct-connect-sitelink/
In the next post, I shall discuss more about Direct Connect Gateway and certification points.
[https://www.notion.so/Direct-Connect-a61557d18e784e778b4500197168454c] - public share url