← ../

AWS Direct Connect

is a physical connection to aws

can be a connection provided by an AWS Delivery Partner (hosted) or a dedicated connection from AWS

• datacenter must have aws direct connect available.
  • dedicated connection must be setup between your dc and aws direct connect locations
• increase bandwidth thoughtput, working with large datasets - lower cost
• more consistent network experience - applications using real-time data feeds
• hybrid envs
• support v4 & v6
• private virtual interface
  • need to setup virtual private gateway on your vpc
• public virtual interfaces
  • connect directly to an aws service instead of a virtual private gateway
• to setup direct connect to one or more vpc in many different regions (same account) you must use a direct connect gateway
  • 1 virtual private interface per vpc
  • vpc won’t route via the direct connect Gateway (use peering)
• 2 types
  • dedicated (physical ethernet port dedicated to the customer)
    • 1Gbps, 10Gbps or 100Gbps
  • hosted connections
    • 50Mbps, 500Mbps, up to 10Gbps
    • connection request made via aws direct connect partners
    • capacity can be added or removed on demand
    • 1,2,5,10 Gbps available at select direct connect partners
• take at least a month to setup
• use vpn within private link if you want encryption
• resiliency
  • high : 2 locations with 1 direct connect each
  • maximum : 2 locations with 2 direct connect each
• a cheap backup can be a site-to-site vpn in case the direct connect fails

Direct Connect gateways

• You associate an AWS Direct Connect gateway with either of the following gateways
  • A transit gateway when you have multiple VPCs in the same Region
  • A virtual private gateway