Lecture 136: DX Connection Resiliency
- 课程：[NEW] AWS Certified Advanced Networking Specialty 2026
- 视频时长：06:47
- 来源：Udemy Lecture 27898780
- Slide 数量：20
- 画面切换：00:48、01:05、01:45、02:55、03:16、03:36、04:03、04:19、04:45、05:16、05:21、05:23、05:28、05:39、05:45、06:01、06:07、06:16、06:25
扫描说明
逐条检查了 Udemy 页面中的 154 条 Transcript cue，并扫描了全长约 6:47 的视频。依据单连接加 VPN 备份、双设备、双位置、High Resiliency、Maximum Resiliency 以及 Direct Connect 控制台 Connection Wizard 的操作画面，共划分为 20 个小节。正式截图均在视频播放、控件隐藏、Transcript 与课程侧栏关闭后按真实媒体边界截取；20 张截图逐张确认无黑边、无右侧或底部裁切、无播放按钮或覆盖层，并统一输出为 1364×770。
Transcript 来自 Udemy 页面自带的英文自动字幕，没有使用 ASR。下面保留页面原文，包括其中的语法或识别错误。
1. Direct Connect 弹性概览
时间范围：00:00–00:48
总结 / Summary
中文
本讲比较 AWS Direct Connect（DX）的多种连接弹性（Connection Resiliency）架构，并说明如何按可用性需求选择方案。
English
This lecture compares AWS Direct Connect connection-resiliency architectures and explains how to choose one for the required availability level.
Transcript
00:00 Hello, and welcome to this lecture.
00:02 Now, let's understand some of the architectures
00:05 with respect to the DX connections.
00:07 Now, having the Direct Connect connection
00:10 from on-premises to AWS does not guarantee
00:13 that this connection will be up 100% of the time.
00:16 You know that the failures can happen.
00:18 Now, there could be a fiber cut,
00:20 there could be some issue with the router,
00:23 your router or AWS router.
00:25 And in that case,
00:26 you can expect downtime over the long period of time.
00:30 In this case, if the network connection between AWS
00:33 and on-premise data center is really critical,
00:35 then you should also design the high availability
00:39 of the Direct Connect connections.
00:40 So in this lecture, let's look at some of those options,
00:44 how you can achieve the high availability
00:46 of your Direct Connect connections.
2. 单条 DX 连接的基础架构
时间范围：00:48–01:05
总结 / Summary
中文
最简单的架构只使用一条 Direct Connect（DX）连接，把企业数据中心连接到 AWS；该连接本身是单点故障（Single Point of Failure）。
English
The simplest architecture uses one Direct Connect link between the corporate data center and AWS, making that link a single point of failure.
Transcript
00:48 So this is the simplest example,
00:50 where you have a single Direct Connect link
00:52 between AWS and on-premise data center.
00:55 Now, if you are cost-conscious and you don't have an option
00:59 to have a second Direct Connect connection,
01:02 then probably you can go with a simpler solution of the VPN
3. 使用 VPN 作为单连接备份
时间范围：01:05–01:45
总结 / Summary
中文
可使用站点到站点 VPN（Site-to-Site VPN）作为 Direct Connect（DX）的备份连接；它能在专线故障时维持连通，但不属于完全冗余的 DX 架构。
English
A Site-to-Site VPN can back up a Direct Connect link and preserve connectivity during a circuit failure, although it is not a fully redundant DX design.
Transcript
01:05 as a backup connectivity.
01:07 So if Direct Connect connection fails,
01:10 then traffic can go over the VPN.
01:12 Now, please understand that
01:14 VPN traffic goes over the internet, which also means that
01:17 you can get the same kind of bandwidth
01:21 and the latency over the VPN.
01:23 So you can expect the higher latency
01:26 than the Direct Connect, and probably the connection
01:28 may not be that stable as the Direct Connector.
01:32 However, it's a good solution.
01:34 It's a cost-effective solution, I would say.
01:37 And again, it is not really recommended
01:39 for critical workloads
01:40 when you are really operating in a hybrid mode.
01:43 So in that case, it is recommended that
4. 双设备上的两条 DX 连接
时间范围：01:45–02:55
总结 / Summary
中文
高可用设计至少使用两条 Direct Connect（DX）连接，并让它们终止在不同的 AWS Direct Connect 设备（DX Devices）和客户设备上，以避免设备级单点故障。
English
A highly available design uses at least two Direct Connect links terminated on different AWS DX devices and customer devices to avoid device-level single points of failure.
Transcript
01:45 you go with at least two direct connections.
01:48 Now, in this case,
01:48 you can leverage a single Direct Connect location,
01:52 and then you can go for two Direct Connect connections
01:56 which are terminated
01:57 at two different Direct Connect devices.
01:59 Now, this is important because
02:01 if both of the connections dominate
02:03 on the same AWS Direct Connect device,
02:05 then the failure in that device will cause, again,
02:08 the disruption of both the connections.
02:11 And while creating the Direct Connect connection,
02:12 you can request AWS
02:14 that you want to leverage another AWS device.
02:18 And even if you don't specify that,
02:19 AWS will always try to find different AWS device
02:24 to terminate your second connection,
02:26 because there is already a mapping between your connections
02:30 and AWS devices being used at the Direct Connect location.
02:34 So, this also provides some kind of higher resiliency.
02:37 But again, if you look at the Direct Connect location,
02:41 there is just one location.
02:43 So for some reason,
02:44 if there is outage at the Direct Connect location,
02:46 then again, both the links will be down.
02:49 This is not that frequent and the probability is very less,
02:53 but still there is a chance, right?
5. 通过设备 ID 验证 VIF 分离
时间范围：02:55–03:16
总结 / Summary
中文
两条虚拟接口（Virtual Interfaces，VIFs）应终止在不同的 AWS 设备；可检查 Direct Connect 控制台中的设备 ID（Device ID）来验证物理分离。
English
The two virtual interfaces should terminate on different AWS devices; verify physical separation by checking the device IDs in the Direct Connect console.
Transcript
02:55 So in this scenario, make sure that both the VIFs
02:58 terminate on different AWS devices.
03:01 And you can check the AWS device ID by
03:04 going through the AWS console.
03:05 And if you look at VIF details,
03:07 it will also show you the AWS device ID.
03:11 Now, as I said,
03:12 if you want to avoid the location level failures,
6. 跨两个位置部署 DX 连接
时间范围：03:16–03:36
总结 / Summary
中文
进一步的弹性来自在两个 Direct Connect 位置（DX Locations）分别部署连接，从而降低单个机房或位置故障的影响。
English
Additional resiliency comes from deploying connections in two Direct Connect locations, reducing the impact of a site or location failure.
Transcript
03:16 in that case,
03:17 you can go with the two Direct Connect locations.
03:18 So first connection is in Direct Connect location one,
03:22 and the second connection in Direct Connect location two.
03:25 Now, this is better than the earlier architecture,
03:28 because it can withstand the failure
03:30 of a single Direct Connect location as well.
03:34 So this is a better architecture,
7. 高弹性架构
时间范围：03:36–04:03
总结 / Summary
中文
在两个位置各部署一条连接，并使用独立的 AWS 与客户设备，可形成高弹性架构（High Resiliency Architecture）。
English
One connection in each of two locations, using separate AWS and customer devices, forms a High Resiliency architecture.
Transcript
03:36 and this is called high resiliency architecture
03:39 in AWS stomps.
03:41 Okay, so far so good. This works well.
03:44 And then you are connected
03:45 to multiple corporate data center sites,
03:48 and this is pretty much good for most of the workloads.
03:52 But as I said, if it's really, really critical workload,
03:56 probably you would also need to have for the redundancy,
04:01 anti Direct Connect location itself.
8. 双位置与连接级备份
时间范围：04:03–04:19
总结 / Summary
中文
若每个位置都部署两条连接并分散到不同设备，则任一位置内仍有连接级备份（Connection Backup），可承受更多组合故障。
English
Deploying two connections on separate devices in each location adds connection-level backup within each site and tolerates more combinations of failures.
Transcript
04:03 That means you'll go with this kind of architecture
04:06 where you have two Direct Connect locations,
04:09 and within that location, you again have two devices
04:13 where the Direct Connect connection terminates.
04:16 So this is called a maximum resiliency architecture
9. 最高弹性架构
时间范围：04:19–04:45
总结 / Summary
中文
两个位置、每个位置两条连接的四连接设计称为最高弹性架构（Maximum Resiliency Architecture），同时提供位置与设备冗余。
English
The four-connection design—two links in each of two locations—is the Maximum Resiliency architecture, providing both location and device redundancy.
Transcript
04:19 for Direct Connect.
04:21 And this is what AWS recommends for your critical workloads.
04:25 So, important that you decide
04:28 what kind of workloads you have,
04:30 can they withstand the network failure,
04:33 then, what is your RTO recovery time for that,
04:38 and what's the cost implication of having
04:40 the multiple Direct Connect connections?
04:42 So now with that, you can also set up these connections
10. 使用 DX 控制台选择弹性模式
时间范围：04:45–05:16
总结 / Summary
中文
AWS Direct Connect 控制台提供经典模式（Classic Mode）和连接向导（Connection Wizard）；向导可按最高弹性、高弹性或开发与测试需求建立连接。
English
The AWS Direct Connect console offers Classic mode and a Connection Wizard, which can build Maximum Resiliency, High Resiliency, or Development and Test designs.
Transcript
04:45 using AWS console as well,
04:48 what AWS provides you some options
04:51 while you set up your Direct Connect connection.
04:53 So there is one that is a Classic setup,
04:56 which is like a single connection creation process.
04:58 But if you want to go with the Connection Wizard,
05:01 then it provides you three options, maximum resiliency,
05:04 high resiliency, and development and test workloads.
05:07 So let's just look at those options in the console,
05:09 and that would give us the overview
05:12 of how the network's setup looks like
05:14 in all these three cases.
11. 进入 Direct Connect 控制台
时间范围：05:16–05:21
总结 / Summary
中文
在 AWS Direct Connect 控制台中可查看连接、虚拟接口（Virtual Interfaces，VIFs）、网关和链路聚合组（Link Aggregation Groups，LAGs）等资源。
English
The AWS Direct Connect console provides access to connections, virtual interfaces, gateways, link aggregation groups, and related resources.
Transcript
05:16 Okay, you can see that I'm in Direct Connect console
05:19 and I'm going to the connections.
12. 打开连接创建流程
时间范围：05:21–05:23
总结 / Summary
中文
从连接（Connections）列表选择创建连接（Create Connection），即可进入新的 Direct Connect（DX）连接配置流程。
English
Selecting Create connection from the Connections list opens the workflow for provisioning new Direct Connect links.
Transcript
05:21 Now, here, you can create a new connection
13. Classic 与 Connection Wizard
时间范围：05:23–05:28
总结 / Summary
中文
创建页面提供经典（Classic）和连接向导（Connection Wizard）两种排序方式；前者创建单连接，后者按弹性目标设计多连接拓扑。
English
The creation page offers Classic and Connection Wizard ordering; Classic provisions a single link, while the wizard designs multiple links for a resiliency target.
Transcript
05:23 and AWS provides you two options,
05:25 either Classic mode or Connection Wizard.
14. Classic 模式连接设置
时间范围：05:28–05:39
总结 / Summary
中文
经典模式（Classic Mode）要求直接填写连接名称、位置、端口速率和服务提供商等单条连接参数。
English
Classic mode directly collects parameters for one connection, including its name, location, port speed, and service provider.
Transcript
05:28 Now, we already saw the Classic mode.
05:30 So it is like creating a single connection,
05:33 and what we are interested is
05:36 in looking the Connection Wizard.
15. 连接向导的三种弹性等级
时间范围：05:39–05:45
总结 / Summary
中文
连接向导（Connection Wizard）提供最高弹性（Maximum Resiliency）、高弹性（High Resiliency）以及开发与测试（Development and Test）三种预设。
English
The Connection Wizard provides three presets: Maximum Resiliency, High Resiliency, and Development and Test.
Transcript
05:39 And Connection Wizard,
05:40 it provides the three options.
05:41 Maximum resiliency, now, that's where you are leveraging
16. 选择 Maximum Resiliency
时间范围：05:45–06:01
总结 / Summary
中文
最高弹性（Maximum Resiliency）预设在两个位置分别创建两条连接，共使用四条连接来抵御位置、设备和链路故障。
English
The Maximum Resiliency preset creates two connections in each of two locations—four total—to withstand location, device, and link failures.
Transcript
05:45 two Direct Connect location,
05:47 and within those locations,
05:48 you are again leveraging two AWS devices.
05:51 So, total four connections here,
05:53 and that's where you get the maximum redundancy
05:56 for your network failures.
05:58 Now, you can also go with higher resiliency model,
17. 选择 High Resiliency
时间范围：06:01–06:07
总结 / Summary
中文
高弹性（High Resiliency）预设在两个位置各创建一条连接，使用两条连接提供位置级冗余。
English
The High Resiliency preset creates one connection in each of two locations, using two links to provide location-level redundancy.
Transcript
06:01 where you have single device
06:02 into every Direct Connect location.
06:05 And then, if it is a development and test enrollment,
18. 选择 Development and Test
时间范围：06:07–06:16
总结 / Summary
中文
开发与测试（Development and Test）预设在同一位置使用两条连接，适合成本更敏感且不要求位置冗余的非生产环境。
English
The Development and Test preset uses two connections in one location for cost-sensitive non-production environments that do not require location redundancy.
Transcript
06:07 then AWS suggests that you have two connections
06:10 probably dominating in the same Direct Connect location.
06:13 So these are the three options that you can choose,
19. 配置多个连接的位置与参数
时间范围：06:16–06:25
总结 / Summary
中文
选择弹性等级后，向导让用户为每条连接配置 Direct Connect 位置（DX Location）、带宽和其他参数，并按所选拓扑创建资源。
English
After a resiliency level is selected, the wizard collects the Direct Connect location, bandwidth, and other settings for each link and creates the chosen topology.
Transcript
06:16 and then accordingly, would select multiple locations.
06:18 Now, we are not going to create these connections,
06:21 but ultimately, that choice is there.
20. 弹性设计选择总结
时间范围：06:25–06:47
总结 / Summary
中文
选择架构时应把业务可用性、故障域（Failure Domain）和成本结合起来：单连接加 VPN 最简单，High Resiliency 跨位置，Maximum Resiliency 则提供最完整的冗余。
English
Architecture selection should balance availability, failure domains, and cost: a single link with VPN is simplest, High Resiliency spans locations, and Maximum Resiliency provides the fullest redundancy.
Transcript
06:25 That's what the resiliency means for Direct Connect.
06:29 So with that, I hope it is clear now
06:31 how to have the multiple Direct Connect connections
06:35 and achieve the required resiliency levels.
06:38 And this is, again, some kind of information
06:41 which will be useful for your exam.
06:43 Thanks for watching, and stay tuned.
整讲总结 / Overall Summary
中文
Direct Connect（DX）弹性设计从单连接加 VPN 备份，逐步提升到双设备、双位置的 High Resiliency，再到两个位置各两条连接的 Maximum Resiliency。关键原则是把连接、客户设备、AWS DX 设备及位置分散到不同故障域（Failure Domains），并通过设备 ID 验证 VIF 的物理分离。AWS 控制台的 Connection Wizard 可按 Maximum Resiliency、High Resiliency 或 Development and Test 预设生成相应拓扑。
English
Direct Connect resiliency progresses from a single link with VPN backup, through dual-device and dual-location High Resiliency, to Maximum Resiliency with two links in each of two locations. The core principle is to distribute links, customer devices, AWS DX devices, and locations across failure domains and verify VIF separation with device IDs. The console's Connection Wizard can create Maximum Resiliency, High Resiliency, or Development and Test topologies.
返回顶部 ↑