Lecture 151: Connecting Transit Gateway & Direct Connect
- 课程：[NEW] AWS Certified Advanced Networking Specialty 2026
- 视频时长：04:49
- 来源：Udemy Lecture 42504358
- Slide 数量：14
- 画面切换：00:15、01:03、01:14、01:30、01:57、02:02、02:21、02:34、03:12、03:34、03:47、04:00、04:27
扫描说明
逐条检查了 Udemy 页面中的 59 条 Transcript cue，并扫描了全长约 04:49 的视频。该讲包含 AWS Cloud WAN and Transit Gateway、AWS Cloud WAN and Direct Connect (Until 2024) 与 AWS Cloud WAN and Direct Connect (new) 三组逐步展开的课件；每个有意义的拓扑或要点揭示均单独作为小节，去除 4 个无新增内容的过渡重复帧后，共保留 14 个画面阶段。最终截图关闭 Transcript 侧栏和播放器控件，完整保留右侧与底部，无黑边，并统一输出为 1364×770。
Transcript 来自 Udemy 页面自带的英文自动字幕，没有使用 ASR。下面保留页面原文，包括其中的语法或识别错误。
1. Cloud WAN、TGW 与 Direct Connect
时间范围：00:00–00:15
总结 / Summary
中文
本讲比较既有 Transit Gateway 和 Direct Connect 接入 AWS Cloud WAN 的迁移与集成方式。
English
The lecture compares migration and integration options for connecting existing Transit Gateway and Direct Connect networks to AWS Cloud WAN.
Transcript
00:00 Hi, now in this lecture, let's talk about how do you connect your transit gateway to
00:04 the cloud WAN and also what are the ways in which you can connect your existing direct
00:10 connection to the cloud WAN network.
00:12 So let's see how you do that.
2. 现有 Transit Gateway 架构
时间范围：00:15–01:03
总结 / Summary
中文
传统架构使用区域级 Transit Gateway 连接多个 VPC，并通过每个附件对应的 Transit Gateway 路由表（Transit Gateway Route Table）实现网络分段。
English
A traditional design connects multiple VPCs to a Regional Transit Gateway and uses per-attachment Transit Gateway route tables for segmentation.
Transcript
00:15 Now let's imagine a situation where you are not using currently the cloud WAN, but you
00:21 have traditional setup using the transit gateway and you know that transit gateway are regional router.
00:27 So you might have few VPCs which are connected to the transit gateway and then you are managing
00:32 the network segmentation using the transit gateway route table per attachment.
00:38 We have already seen this kind of architecture in the transit gateway section and now as
00:44 you adopt cloud WAN, then possibly you are going to set up fresh new cloud WAN network
00:50 and all new VPCs you will be connecting to your cloud WAN network.
00:55 Now at this moment you have multiple choices with respect to how do you integrate your
00:59 existing VPCs with the cloud WAN network.
3. 方案一：VPC 直接迁移到 Cloud WAN
时间范围：01:03–01:14
总结 / Summary
中文
最直接的迁移方式是重新配置 VPC，使其绕过 Transit Gateway 并直接连接 Cloud WAN 分段（Segment）。
English
The simplest migration reconfigures the VPCs to bypass the Transit Gateway and attach directly to Cloud WAN segments.
Transcript
01:03 So one obvious choice is you don't use the transit gateway and rather reconfigure your
01:08 VPCs to connect to your segment which are there in your new cloud WAN network.
4. 方案二：保留 Transit Gateway
时间范围：01:14–01:30
总结 / Summary
中文
如果不希望扰动既有网络，可以保留 Transit Gateway，并把它整体集成到新的核心网络（Core Network）。
English
When the existing network should remain undisturbed, the Transit Gateway can be retained and integrated with the new Core Network.
Transcript
01:14 But there are some situations where you don't want to disturb your existing network and
01:14 rather you want to integrate your existing transit gateway with your cloud WAN network.
01:26 So for that you have to do some additional steps.
5. 创建 TGW Peering
时间范围：01:30–01:57
总结 / Summary
中文
第一步是在 Transit Gateway 与核心网络（Core Network）之间创建对等连接（Peering）。
English
The first step is to create a peering connection between the Transit Gateway and the Core Network.
Transcript
01:30 Very first thing you have to do is to create a peering connection between the transit gateway
01:35 and your core network.
01:37 Now this peering is little different than the VPC peering that we are seeing because
01:42 this actually does the peering connection at switch level and when you do that it also
01:48 sets up the dynamic routing between the transit gateway and the core network and it also creates
01:53 something called policy table for the transit gateway.
6. Dynamic Routing 与 Policy Table
时间范围：01:57–02:02
总结 / Summary
中文
该对等连接在交换层工作，并自动建立动态路由（Dynamic Routing）及 Transit Gateway 策略表（Policy Table）。
English
The peering operates at the switching layer and automatically establishes dynamic routing and a Transit Gateway policy table.
Transcript
01:57 Now once you have this peering and again you can do that from the cloud WAN console.
7. Transit Gateway Route Tables
时间范围：02:02–02:21
总结 / Summary
中文
Transit Gateway 使用独立路由表（Route Table）隔离 Development、Production 和 Shared 等网络域。
English
The Transit Gateway uses separate route tables to isolate network domains such as Development, Production, and Shared.
Transcript
02:02 Now in your transit gateway routing, you might have different route table for different kind of network.
02:09 For example, you could have your production segment or your development segment and you
02:15 know that in transit gateway you do that by managing the different route table for
02:19 every attachment.
8. Route Table 到 Segment 的映射
时间范围：02:21–02:34
总结 / Summary
中文
将每个 Transit Gateway 路由表附加（Route Table Attachment）到 Cloud WAN 中对应的分段（Segment）。
English
Each Transit Gateway route table is attached to its corresponding Cloud WAN segment.
Transcript
02:21 And now in order to connect your transit gateway network to the core network, you have to map
02:27 the transit gateway route tables to the corresponding segments of your cloud WAN network.
9. 通过 TGW 接入 Cloud WAN
时间范围：02:34–03:12
总结 / Summary
中文
完成 Peering 与路由表附加后，既有 VPC 可通过 Transit Gateway 访问 Cloud WAN，同时保留原有分段结构。
English
After peering and route-table attachments are complete, existing VPCs reach Cloud WAN through the Transit Gateway while preserving their segmentation.
Transcript
02:34 So you will create this route table attachment to the particular segment.
02:41 Now as you do that, you are now actually connecting your VPCs to this cloud WAN network
02:47 through the transit gateway.
02:50 But remember these additional steps out there.
02:54 All right, next I want to talk about how do you connect cloud WAN network with your direct
02:59 connect connection.
03:01 And for this there are two ways.
03:03 So if you just go few months back, AWS did not have direct option to connect your cloud
03:10 WAN network with your direct connect connection.
10. Direct Connect 旧式架构
时间范围：03:12–03:34
总结 / Summary
中文
旧方案无法直接把 Direct Connect 接入 Cloud WAN，必须在两者之间引入 Transit Gateway。
English
The legacy design cannot attach Direct Connect directly to Cloud WAN and therefore requires a Transit Gateway in between.
Transcript
03:12 Rather for this, you had to use a transit gateway in between.
03:17 So if you see on your direct connect connection, you had to use transit with, then connect
03:22 it to the direct connect gateway, then again connect it to the transit gateway.
03:27 And then as we just saw, you have to pair the transit gateway with your core network
03:32 and configure the transit gateway route table.
11. 旧方案的多层连接
时间范围：03:34–03:47
总结 / Summary
中文
完整路径是 Transit VIF → Direct Connect Gateway → Transit Gateway → Core Network Peering，并额外配置 Transit Gateway 路由表。
English
The complete path is Transit VIF to Direct Connect Gateway to Transit Gateway to Core Network peering, plus Transit Gateway route-table configuration.
Transcript
03:34 So until 2024 or 2025, I would say it was a very complex process to connect cloud WAN
03:42 network with your direct connect connection.
03:44 So the steps are similar what we just talked about.
12. 原生 DX Gateway Attachment
时间范围：03:47–04:00
总结 / Summary
中文
AWS 在 re:Invent 2025 推出原生 Direct Connect Gateway Attachment，简化 Direct Connect 与 Cloud WAN 的连接。
English
At re:Invent 2025, AWS introduced a native Direct Connect Gateway attachment that simplifies Direct Connect-to-Cloud WAN connectivity.
Transcript
03:47 And that's where recently in the 2025 re-invent, AWS launched a native direct connect gateway
03:55 attachment to connect cloud WAN network to your direct connect connection.
13. 移除中间 Transit Gateway
时间范围：04:00–04:27
总结 / Summary
中文
新方案让 Direct Connect Gateway 直接附加到 Cloud WAN，不再需要中间 Transit Gateway、Peering 或 TGW 路由表映射。
English
The new design attaches the Direct Connect Gateway directly to Cloud WAN, eliminating the intermediate Transit Gateway, peering, and TGW route-table mapping.
Transcript
04:00 And as you use this attachment, you don't need to have this transit gateways, but rather
04:06 you can directly connect your direct connect gateways with the cloud WAN network.
04:12 So it's a native attachment, but just that in order to create this direct connect gateway,
04:18 you have to use the transit with there, you cannot use the private with.
04:24 So that's the only constraint there.
14. Transit VIF 约束与简化结果
时间范围：04:27–04:49
总结 / Summary
中文
原生附件仍要求 Transit Virtual Interface（Transit VIF），不能使用 Private VIF；除此之外，连接路径显著简化。
English
The native attachment still requires a Transit Virtual Interface rather than a Private VIF, but the overall connectivity path is substantially simpler.
Transcript
04:27 You can see that now the connectivity has been simplified with this direct connect gateway attachment.
04:33 All right, so I hope it is clear how to connect the transit gateway to the cloud WAN network
04:40 and then how to connect your direct connect connection to the cloud WAN network.
04:45 So with that, now let's go to the next lecture.
整讲总结 / Overall Summary
中文
本讲说明如何把既有 Transit Gateway 与 Direct Connect 网络接入 AWS Cloud WAN。对于 Transit Gateway，可选择迁移 VPC 直接连接 Cloud WAN 分段（Segment），或保留既有架构，通过 Transit Gateway Peering 建立动态路由和策略表（Policy Table），再把各 Transit Gateway 路由表（Transit Gateway Route Table）附加到对应分段。对于 Direct Connect，旧方案需要 Transit VIF、Direct Connect Gateway、Transit Gateway 与 Cloud WAN 的多层连接；新方案使用原生 Direct Connect Gateway Attachment，省去 Transit Gateway，但仍要求 Transit Virtual Interface（Transit VIF）。
English
This lecture explains how to integrate existing Transit Gateway and Direct Connect networks with AWS Cloud WAN. For Transit Gateway, VPCs can be migrated to attach directly to Cloud WAN segments, or the existing design can be preserved by creating Transit Gateway peering, dynamic routing, and a policy table, then attaching each Transit Gateway route table to the corresponding segment. For Direct Connect, the legacy design chains a Transit VIF, Direct Connect Gateway, Transit Gateway, and Cloud WAN, while the new native Direct Connect Gateway attachment removes the Transit Gateway but still requires a Transit VIF.
返回顶部 ↑