Lecture 115: Introduction to AWS Direct Connect
- 课程：[NEW] AWS Certified Advanced Networking Specialty 2026
- 视频时长：09:43
- 来源：Udemy Lecture 27890020
- Slide 数量：7
- 画面切换：00:50、01:49、03:19、04:54、06:17、07:55
扫描说明
逐条检查了 Udemy 页面中的 146 条 Transcript cue，并以每条 cue 对应画面为时间轴扫描了全长约 9:43 的视频。依据标题、混合网络定位、OSI 分层、Direct Connect 基本拓扑、核心收益、全球骨干网与交付特性、完整架构七组独立幻灯片，共划分为 7 个小节。正式截图均从播放中的视频真实画面边界截取为 1364×770，并逐张复核。
Transcript 来自 Udemy 页面自带的英文自动字幕，没有使用 ASR。下面保留页面原文，包括其中的语法或识别错误。
1. AWS Direct Connect 概览
时间范围：00:00–00:50
总结 / Summary
中文
AWS Direct Connect（DX）是混合连接（hybrid connectivity）的核心服务，通过实际物理端口和链路连接企业网络与 AWS。由于需要在 Direct Connect 位置（Direct Connect location）完成物理交付和回程连接，本节以架构和原理为主，无法像 VPC 配置那样直接在线完成端到端实验。
English
AWS Direct Connect is a core hybrid-connectivity service that uses physical ports and links between a corporate network and AWS. Because it requires physical provisioning at Direct Connect locations and connectivity back to an on-premises site, the section focuses on architecture and theory rather than an end-to-end console lab.
Transcript
00:00 Hello and welcome to this section.
00:02 Direct Connect.
00:02 Now, this is the most important section of this entire course because most of the questions are around
00:09 the hybrid connectivity.
00:11 And direct connect is one of the important aspect of the hybrid connectivity.
00:16 Now, we also write direct, connect as as a shorthand.
00:19 So that saves us some time.
00:21 Now, one thing to note that in direct connect, we might not be able to do the labs because it requires
00:26 actual physical network ports to be provisioned in direct connect locations, and it also needs connectivity
00:32 back to your on premise data centers, which is really not possible.
00:36 So this is not like creating just a VPC and routing traffic using the route tables, right?
00:41 You actually need to have physical connections.
00:43 So in this entire sections, we might not be able to do any labs.
00:48 Okay, so let's get started here.
2. 混合网络中的 Dedicated Link
时间范围：00:50–01:49
总结 / Summary
中文
站点到站点 VPN（Site-to-Site VPN）通过互联网承载加密流量，而 Direct Connect 提供企业数据中心到 AWS 的专用网络链路（dedicated network link）。最简单的场景连接一个 VPC，后续还可扩展到多 VPC、多个数据中心以及 SiteLink 等网状连接。
English
Site-to-Site VPN carries encrypted traffic over the internet, whereas Direct Connect supplies a dedicated network link from a corporate data center to AWS. The simplest design reaches one VPC, while later architectures can connect multiple VPCs, multiple data centers, and SiteLink-based meshes.
Transcript
00:50 First of all, you know this picture.
00:53 We have seen most of these services which are connected to VPC.
00:56 And if not, then we will cover that in the next lectures.
01:00 But in this particular lecture, we will be focusing on connecting your VPC to the on premise data center,
01:05 which you see on the right side.
01:07 As of now, we just saw VPN.
01:09 But then if you need to have really a dedicated link, that means a dedicated network between your corporate
01:15 data center and VPC, then direct Connect falls into that place.
01:20 Now with respect to the VPN, it goes over the Internet traffic, but as I said, this is a dedicated
01:25 network and as of now we are just showing here one VPC.
01:29 But as we go into the depth of the topic, we will talk about more vpcs and how to have the full mesh
01:29 kind of connectivity with direct connect.
01:38 In fact, we'll also see how to connect multiple customer data centers directly using the direct connect
01:43 location with the features.
01:44 Something like Sitelink.
01:46 Okay, now let's get started here.
3. Direct Connect 跨越多个 OSI Layer
时间范围：01:49–03:19
总结 / Summary
中文
Direct Connect 不能简单归入单一 OSI 层（OSI layer）：物理层（physical layer）使用单模光纤，数据链路层（data-link layer）依赖以太网和 VLAN 标记（VLAN tagging），网络层（network layer）使用 IP 地址，BGP 路由交换则通过 TCP 179 端口运行。它是跨越多层协议栈的端到端网络服务。
English
Direct Connect does not map to one OSI layer. It uses single-mode fiber at the physical layer, Ethernet and VLAN tagging at the data-link layer, IP addressing at the network layer, and TCP port 179 for BGP route exchange. It is an end-to-end service spanning several layers.
Transcript
01:49 As you know, this is an ozone layer and we talked about this briefly.
01:53 In reality, the real world network protocol doesn't fall neatly into this ozone layer because some
01:59 of the protocol works across the layer.
02:01 And direct connect is not an exception to that.
02:04 So if you talk about direct connect networking, it has a layer from physical layer up to the application
02:09 layer.
02:10 So in the first layer, it has physical single mode, fiber.
02:14 And what is that?
02:15 I'll explain later, but it needs a physical connection, right?
02:19 So there is layer one obviously involved.
02:22 On top of that physical connection, there should be an Ethernet and it should be supporting the VLAN
02:27 tagging.
02:28 Now what is VLAN tagging?
02:29 We'll again understand, but typically it is mapped to the layer two.
02:33 Then it needs IP addresses or IP addresses so that it can set up the BGP session border gateway protocol
02:40 sessions.
02:41 Right.
02:41 And those IPS works at layer three.
02:44 And in order to exchange the BGP routes, it needs a TCP connection on Port 179.
02:51 An actual BGP.
02:51 What it does is basically exchange the routes between the two BGP or two BGP neighbors.
02:58 So if you look at a direct connect from this lens, it works at various layers and that's where it's
03:05 not really appropriate to map, direct, connect to one particular layer.
03:10 And that's where I said the layers are more theoretical and you can't really map 1 to 1 mapping between
03:17 the layers and the protocols.
4. Direct Connect 的三方拓扑
时间范围：03:19–04:54
总结 / Summary
中文
基本拓扑包含 AWS 区域、第三方运营的 Direct Connect 位置（Direct Connect location）和企业数据中心三方。企业需要把私有线路接到就近的 DX 位置，AWS 则已通过 AWS 骨干网（AWS backbone network）把该位置连接到区域；因此 Direct Connect 本质上是从本地到 AWS 的专用网络连接。
English
The basic topology has three parties: an AWS Region, a third-party-operated Direct Connect location, and the corporate data center. The customer extends a private circuit to a nearby DX location, while AWS already connects that location to the Region over its backbone.
Transcript
03:19 Now with that, let's try to get into what is direct connect.
03:24 So if I'm to simplify for you, what is direct connect?
03:28 There are three parties involved right on the left side.
03:30 You can see there is AWS and this is like AWS Cloud, it is AWS region, whatever you call it.
03:37 And on the right side, you have corporate data center.
03:40 Ultimate goal is to connect AWS network to corporate data center using the private network.
03:45 But you can't directly put that private network from your on premise data center to AWS, right?
03:51 You can't lay down those wires there directly for that.
03:55 What AWS has done, AWS has concept like direct connect locations.
03:59 Now this direct connect locations you can consider as like a networking hub.
04:03 Now these are not owned by AWS.
04:05 These are third party locations which are completely managed and owned by third parties.
04:11 And what you have to do is ultimately connect your data center to direct connect location.
04:15 And this direct connect location is already connected to AWS region through AWS Backbone Network.
04:22 Okay, So what is Direct Connect?
04:23 It's a dedicated network connection from on premises to AWS.
04:28 And when we say dedicated, you have to set up a private connection from your data center to AWS direct
04:34 connect location, which is nearest to your data center.
04:37 Now, across the globe, there are more than 100 locations and you have to choose which works best for
04:42 you.
04:42 And there is already a connectivity, as I said, between this location and AWS region.
04:48 So you don't need to set up this connectivity.
04:51 So ultimately it's a three way connection.
5. 低时延、稳定带宽与较低传输成本
时间范围：04:54–06:17
总结 / Summary
中文
专用物理链路可提供较低时延（low latency）和更稳定的带宽（consistent bandwidth），避免互联网路径的波动。与互联网数据传出相比，Direct Connect 的数据传输成本（data transfer cost）通常更低；同一连接既能私下访问 VPC，也能访问 S3、DynamoDB 等 AWS 公共服务端点（public service endpoint）。
English
A dedicated physical path provides lower latency and more consistent bandwidth than an internet route. Direct Connect data-transfer charges are generally lower than internet egress, and the connection can reach both private VPC resources and public AWS service endpoints such as S3 and DynamoDB.
Transcript
04:54 Now, what provides you is the benefit like low latency, because it's a dedicated physical network,
05:01 that means you are not relying on those intermittent Internet networks where the bandwidth could be
05:07 choppy sometimes.
05:08 So you get a direct connectivity which provides low latency and also the consistent bandwidth you get.
05:14 So whatever bandwidth you are getting, like 50 Mbps or one GB, you can assume that this is the same
05:20 bandwidth you will get throughout the time you use direct connect links.
05:25 It also offers you low data transfer cost.
05:28 Now, as you know, if you are taking data out of AWS over the Internet, for example, there is per
05:33 gigabyte data transfer cost.
05:35 Now that is typically $0.09 per GB.
05:40 And if you are taking out a lot of data, then it's a huge cost.
05:43 But if you have the direct connect connection, then this cost is much lower.
05:46 Now actual cost of data transfer will depend on a lot of factors such as from which region you are doing
05:52 the data transfer out to which direct connect location across the globe and charges differs.
05:58 Now, through direct connect, you can access privately your vpcs right?
06:03 You can also access public services like S3 or DynamoDB.
06:07 So that means all the traffic from your data center going to these services is also routed through the
06:13 direct connect connection.
06:14 So overall, that is AWS direct connect.
6. 全球骨干网、第三方机房与交付周期
时间范围：06:17–07:55
总结 / Summary
中文
DX 位置通过高容量 AWS 全球骨干网（AWS Global Backbone）互联，但机房通常由 Equinix 等授权第三方运营商管理。端到端交付涉及端口、交叉连接（cross-connect）和运营商线路，通常需要 4–12 周规划；专用连接可提供 1、10 或 100 Gbps 等带宽，低于 1 Gbps 的速率通常由 Direct Connect 合作伙伴（Direct Connect Partner）提供。
English
DX locations connect through the high-capacity AWS Global Backbone, while authorized third parties such as Equinix typically operate the facilities. Port provisioning, cross-connects, and carrier circuits can take 4–12 weeks. Dedicated connections offer bandwidths such as 1, 10, or 100 Gbps, while sub-1-Gbps options normally come from Direct Connect Partners.
Transcript
06:17 Now moving on, it leverages the AWS global backbone, what it means that all AWS direct connect locations
06:24 and AWS regions are connected by high capacity AWS Global Network, which is called AWS Backbone Network
06:31 as well.
06:32 So definitely it helps you with resiliency of the network backbone.
06:37 Now, DCS locations are not owned by AWS.
06:40 So AWS has partnered with third party service providers like Equinix, for example, or Cdfi, or there
06:46 are many, right?
06:47 So they own the DCS locations, and then you have to work with them in order to set up a connectivity
06:53 to AWS direct connect.
06:55 Now, as of today, there are 115 DCS locations across the world in 31 AWS regions, and this number
07:02 will go on increasing as launches more regions and DCS locations.
07:08 Now, DCS is not a service where you can just go to AWS console and set up end to end connectivity.
07:14 It needs physical port provisioning, cross Connect, and we'll learn more about all that process.
07:18 But it may take up to 4 to 12 weeks overall to set up.
07:22 So you have to plan these things in much advance.
07:25 If you are planning to use direct connect connectivity for your production workloads.
07:31 With respect to the bandwidth, you can get up to 110 or 100 GB bandwidth as a dedicated bandwidth.
07:38 But if you need a lower bandwidth, then you can work with a partner and then they can provide you sub
07:44 one Gbps link, for example, 50 Mbps or 100 Mbps.
07:49 Likewise.
07:50 So depending on what kind of bandwidth you need, there are different options available to you.
7. 完整 Direct Connect 架构与 VIF
时间范围：07:55–09:43
总结 / Summary
中文
完整架构中，客户通过运营商线路把数据中心接到 DX 位置内的客户/合作伙伴路由器，再用交叉连接（cross-connect）连接 AWS 路由器。物理连接之上创建虚拟接口（Virtual Interface, VIF）：公共 VIF（public VIF）访问 AWS 公共服务，私有 VIF（private VIF）经虚拟私有网关（Virtual Private Gateway, VGW）访问 VPC，传输 VIF（transit VIF）则连接 Transit Gateway（TGW）。
English
In the full architecture, a carrier circuit connects the data center to a customer or partner router at the DX location, and a cross-connect links that router to the AWS router. Virtual Interfaces are created on the physical connection: a public VIF for public AWS services, a private VIF for VPC access through a Virtual Private Gateway, and a transit VIF for a Transit Gateway.
Transcript
07:55 Okay, Now let's look at how it looks in the architecture.
07:59 So in the left side you have region and then you might have your VPC, you have S3 and some other AWS
08:05 services.
08:06 You could also have your transit gateways and this is all into your AWS account.
08:10 On the right side, you have your corporate data center from where you want to set up private connectivity
08:16 using the AWS direct connect, right?
08:18 So in the middle you have direct connect location.
08:20 So you will choose the nearest direct connect location to your data center.
08:24 And in this direct connect location, there are two routers.
08:27 One is AWS router and one is your router or your partner's router.
08:32 And we'll talk more about that.
08:33 But then you have to create a cross connect between these two routers.
08:37 You have to set up a physical connectivity from your data center to your router in the direct connect
08:42 location.
08:43 Now this can be by any third party network service provider, right?
08:47 It could be MPLS link, it could be layer two link, and we'll also talk about that.
08:52 So once you set that connectivity, once you have Cross Connect, then you can create a logical connectivity
08:58 on top of this direct connect connection, which is called Waves Virtual Interfaces.
09:02 In order to access public services, you create a public VIF in order to directly connect to the VPC
09:08 using virtual private gateway, you create a private VIF and if you want to connect to a transit gateway,
09:14 then you can create a transit wave.
09:16 So there are three types of the waves you can create on top of this direct connect connection.
09:21 And we'll learn more about all these waves and entire connectivity in more detail.
09:26 But as of now, this is what you need to know.
09:29 Okay, So I hope at least you know now what is direct connect.
09:32 And now let's get into more details about all these components of the direct connect, how they work
09:38 and how you can have the different architectures.
09:40 So thanks for watching and stay tuned.
整讲总结 / Overall Summary
中文
AWS Direct Connect（DX）通过第三方 DX 位置和 AWS 全球骨干网（AWS Global Backbone），为本地网络提供到 AWS 的专用物理连接。它跨越光纤、以太网/VLAN、IP 和 BGP/TCP 多层协议，带来低时延、稳定带宽和较低数据传输成本，并通过不同虚拟接口（Virtual Interface, VIF）访问公共服务、VPC 或 Transit Gateway。
English
AWS Direct Connect provides a dedicated physical path from on-premises networks to AWS through third-party DX locations and the AWS Global Backbone. It spans fiber, Ethernet and VLANs, IP, and BGP over TCP, delivering low latency, consistent bandwidth, and lower transfer costs. Public, private, and transit VIFs provide access to public services, VPCs, and Transit Gateway respectively.
返回顶部 ↑