AWS · Advanced Networking Specialty

网络课程笔记

Lecture 127 · 47 张幻灯片

幻灯片、双语总结及 Transcript · 图片已内嵌,可离线阅读。

原文默认收起
lecture-127.md

Lecture 127: Direct Connect Gateway with Private VIF and VGW

  • 课程:[NEW] AWS Certified Advanced Networking Specialty 2026
  • 视频时长:11:54
  • 来源:Udemy Lecture 27896616
  • Slide 数量:47
  • 画面切换:00:20、00:27、00:49、01:07、01:23、01:52、01:55、02:00、02:17、02:48、03:05、03:49、03:51、04:08、04:27、04:38、04:42、05:00、05:03、05:22、05:31、05:58、06:01、06:13、06:29、06:30、06:38、06:41、06:45、06:51、07:09、07:14、07:20、07:23、07:24、07:26、07:31、07:42、07:47、07:54、08:54、09:42、10:09、10:13、10:17、10:54

扫描说明

逐条检查了 Udemy 页面中的 209 条 Transcript cue,并以每条 cue 对应画面扫描了全长约 11:54 的视频。依据幻灯片切换、要点渐显、架构图标注和 AWS 控制台操作状态,共划分为 47 个小节。正式截图均在锁定 Lecture 27896616、Autoplay 关闭、关闭 Transcript 与课程侧栏、隐藏底部播放器控件后,按完整媒体边界截取并输出为 1364×770;逐张复核了右侧、底部和左侧边界。

Transcript 来自 Udemy 页面自带的英文自动字幕,没有使用 ASR。下面保留页面原文,包括其中的语法或识别错误。

1. DXGW、Private VIF 与 VGW

时间范围:00:00–00:20

Direct Connect Gateway with Private VIF and Virtual Private Gateway title slide

总结 / Summary

中文

本讲聚焦 Direct Connect 网关(Direct Connect Gateway, DXGW)通过私有虚拟接口(Private Virtual Interface, Private VIF)连接虚拟私有网关(Virtual Private Gateway, VGW)的架构。

English

This lecture focuses on using a Direct Connect Gateway (DXGW) with a Private VIF and Virtual Private Gateways (VGWs).

Transcript

00:00 Hi.

00:01 So now in this lecture, let's understand more about DX gateways.

00:05 And you know that DX Gateway can be attached to the private VIF or a Transit VIF.

00:10 But in this lecture, let's understand DX Gateway with private VIF.

00:14 And in the next video, we will see

00:17 DX Gateway with Transit VIF.

2. 为什么需要 Direct Connect Gateway

时间范围:00:20–00:27

Why Direct Connect Gateway title slide

总结 / Summary

中文

Direct Connect 网关(Direct Connect Gateway, DXGW)主要用于让一条 Direct Connect 连接扩展到多个虚拟私有云(Virtual Private Cloud, VPC)。

English

A Direct Connect Gateway is primarily used to extend one Direct Connect connection to multiple VPCs.

Transcript

00:20 OK. So very first question, why to use DX gateways?

00:23 I know that you already understood that. But just to reiterate,

3. 多 VPC 访问问题

时间范围:00:27–00:49

Problem accessing multiple VPCs over the same Direct Connect connection

总结 / Summary

中文

如果不使用 Direct Connect 网关(Direct Connect Gateway, DXGW),每个虚拟私有云(Virtual Private Cloud, VPC)通常都需要独立的私有虚拟接口(Private Virtual Interface, Private VIF)和边界网关协议(Border Gateway Protocol, BGP)会话。

English

Without a DXGW, each VPC generally needs its own Private VIF and BGP session.

Transcript

00:27 if you want to access multiple VPCs over the same DX connection,

00:32 then you can use DX gateways because without that,

00:36 you would have to create multiple private VIFs

00:39 which connects to the virtual private gateways (VGW).

00:43 And then you would have to have as many BGP sessions as your number of VPCs.

4. DXGW 解决方案

时间范围:00:49–01:07

AWS Direct Connect Gateway solution bullet

总结 / Summary

中文

AWS Direct Connect 网关(Direct Connect Gateway, DXGW)解决了多虚拟私有云(Virtual Private Cloud, VPC)共享同一 Direct Connect 连接的问题,并支持跨区域连接。

English

AWS Direct Connect Gateway solves the shared-connectivity problem and supports VPC connectivity across Regions.

Transcript

00:49 Now, in order to solve that problem, AWS had introduced DirectConnect Gateway.

00:54 Another benefit is that

00:56 with DX gateways, you can connect VPCs from different AWS regions,

01:01 which wasn't possible using just the private

01:04 VIFs to the virtual private gateways.

5. 单个 DXGW 的连接范围

时间范围:01:07–01:23

A single Direct Connect Gateway can connect multiple VPCs across Regions and accounts

总结 / Summary

中文

单个 Direct Connect 网关(Direct Connect Gateway, DXGW)可使用虚拟私有网关(Virtual Private Gateway, VGW)或传输网关(Transit Gateway, TGW)连接同一区域或不同区域、同一账户或不同账户中的多个虚拟私有云(Virtual Private Cloud, VPC)。

English

One DXGW can connect multiple VPCs in the same or different Regions and accounts through VGWs or TGWs.

Transcript

01:07 So a

01:08 single DirectConnect Gateway can be connected to multiple

01:11 VPCs in the same or different AWS regions

01:14 and in the same or different AWS accounts using the VGW or TGW

01:21 and we will talk about that.

6. 不使用 DXGW 的跨区域限制

时间范围:01:23–01:52

Private VIF architecture without Direct Connect Gateway

总结 / Summary

中文

私有虚拟接口(Private Virtual Interface, Private VIF)直接连接虚拟私有网关(Virtual Private Gateway, VGW)时,需要为多个虚拟私有云(Virtual Private Cloud, VPC)创建多个 VIF,并受单一区域连接范围限制。

English

When Private VIFs connect directly to VGWs, multiple VPCs require multiple VIFs and the design is limited to one Region.

Transcript

01:23 So this is an architecture with

01:26 private VIF. Here, we are not using the DX gateways.

01:30 And as you can see, you have to have as many private VIFs as your

01:34 number of VPCs

01:36 and then you are restricted to single AWS Region.

01:40 But here in this case,

01:42 if you want to connect to different AWS Region VPCs,

01:45 then you cannot with just the private VIF. So the solution is using the DX gateways.

7. DXGW 是全局资源

时间范围:01:52–01:55

Direct Connect Gateway global network device bullet

总结 / Summary

中文

Direct Connect 网关(Direct Connect Gateway, DXGW)是可从所有 AWS 区域(AWS Region)访问的全局网络设备。

English

A Direct Connect Gateway is a global network device accessible in all AWS Regions.

Transcript

01:52 So these are accessible in all AWS Region

8. Private VIF 与 Transit VIF 集成

时间范围:01:55–02:00

Direct Connect integrates through Private VIF or Transit VIF

总结 / Summary

中文

Direct Connect 网关(Direct Connect Gateway, DXGW)可通过私有虚拟接口(Private VIF)或传输虚拟接口(Transit VIF)接入 Direct Connect。

English

A DXGW can integrate with Direct Connect through either a Private VIF or a Transit VIF.

Transcript

01:55 and you can integrate DX Gateway with private VIF or a Transit VIF.

9. DXGW 多区域拓扑

时间范围:02:00–02:17

Direct Connect Gateway connecting VPCs in multiple Regions

总结 / Summary

中文

私有虚拟接口(Private Virtual Interface, Private VIF)先连接 Direct Connect 网关(Direct Connect Gateway, DXGW),再由 DXGW 关联多个区域中的虚拟私有网关(Virtual Private Gateway, VGW)和虚拟私有云(Virtual Private Cloud, VPC)。

English

The Private VIF terminates on the DXGW, which then associates with VGWs and VPCs across multiple Regions.

Transcript

02:00 So the architecture looks something like this. Now,

02:04 instead of private VIF connecting directly to the VGW,

02:07 you connect it to the DX Gateway first

02:10 and then this DX Gateway can be connected to

02:13 multiple VPCs across AWS regions.

10. BGP 会话位置

时间范围:02:17–02:48

BGP session between the customer router and Direct Connect Gateway

总结 / Summary

中文

边界网关协议(Border Gateway Protocol, BGP)会话建立在客户路由器(Customer Router)与 Direct Connect 网关(Direct Connect Gateway, DXGW)之间。

English

The BGP session is established between the customer router and the Direct Connect Gateway.

Transcript

02:17 And there is a BGP session between

02:20 customer router and the DX Gateway.

11. 账户所有权规则

时间范围:02:48–03:05

Direct Connect Gateway ownership rules

总结 / Summary

中文

私有虚拟接口(Private VIF)与 Direct Connect 网关(Direct Connect Gateway, DXGW)必须属于同一 AWS 账户;关联的虚拟私有云(Virtual Private Cloud, VPC)、虚拟私有网关(Virtual Private Gateway, VGW)或传输网关(Transit Gateway, TGW)可以属于其他账户。

English

The Private VIF and DXGW must share an AWS account, while associated VPCs, VGWs, or TGWs may be owned by different accounts.

Transcript

02:48 Now, with respect to the AWS account ownership,

02:51 the VIFs and the DX gateways must be owned by same AWS account.

02:56 However,

02:56 the VPCs that you attach to the DX Gateway

03:01 or Transit Gateway can be in a different AWS account.

12. 跨账户拓扑示例

时间范围:03:05–03:49

Direct Connect Gateway topology with different AWS account labels

总结 / Summary

中文

拓扑图说明 Direct Connect 连接和虚拟私有云(Virtual Private Cloud, VPC)可分属不同账户,但私有虚拟接口(Private VIF)和 Direct Connect 网关(Direct Connect Gateway, DXGW)必须同账户。

English

The topology shows that the connection and VPCs may be in different accounts, but the Private VIF and DXGW must be in the same account.

Transcript

03:05 Now, what I mean by that is

03:07 if this is the architecture,

03:09 then

03:10 your VPCs

03:11 could be in different accounts and your DX

03:14 connection could be in different account as well.

03:18 But the DX Gateway and the private VIF should be in the same AWS account.

03:24 Now,

03:25 you understood the Dedicated connection and the Hosted connection.

03:29 In that case,

03:30 the underlying DX connection can still be owned by either

03:34 yourself or it could be owned by the partner.

03:37 But when you create a VIF,

03:39 that VIF and the DX Gateway should be in the same AWS account.

03:43 So that's the restriction so far

03:45 with respect to the ownership of the DX gateways.

13. DXGW 限制概览

时间范围:03:49–03:51

Direct Connect Gateway restrictions title slide

总结 / Summary

中文

将多个虚拟私有云(Virtual Private Cloud, VPC)关联到同一 Direct Connect 网关(Direct Connect Gateway, DXGW)时,需要遵守路由与地址范围限制。

English

Associating multiple VPCs with one DXGW introduces routing and address-range restrictions.

Transcript

03:49 So moving on

14. VPC CIDR 不得重叠

时间范围:03:51–04:08

Overlapping VPC CIDRs are not allowed

总结 / Summary

中文

关联到同一 Direct Connect 网关(Direct Connect Gateway, DXGW)的虚拟私有云(Virtual Private Cloud, VPC)无类别域间路由(Classless Inter-Domain Routing, CIDR)范围不能重叠。

English

VPC CIDR ranges associated with the same DXGW must not overlap.

Transcript

03:51 now, there are certain restrictions

03:54 and this is obvious because you are connecting multiple VPCs to the same DX Gateway.

04:00 So the VPC CIDR should not be overlapping.

04:03 If they are overlapping, you can't associate them with the same DX Gateway.

15. DXGW 不提供 VPC 间路由

时间范围:04:08–04:27

VPC to VPC communication is not allowed through Direct Connect Gateway

总结 / Summary

中文

Direct Connect 网关(Direct Connect Gateway, DXGW)不允许虚拟私有云到虚拟私有云(VPC-to-VPC)通信;它用于 VPC 与本地网络(on-premises network)之间的连接。

English

A DXGW does not provide VPC-to-VPC communication; it is intended for VPC-to-on-premises connectivity.

Transcript

04:08 And again,

04:10 there is no VPC to VPC communication allowed via the DX Gateway,

04:15 unlike the Transit Gateway, which allows that communication,

04:18 DX Gateway doesn't allow that,

04:20 which means VPC can communicate to

04:22 on-premises

04:23 network, but inter VPC communication is not allowed.

16. DXGW 路由拓扑

时间范围:04:27–04:38

Direct Connect Gateway routing topology

总结 / Summary

中文

路由拓扑展示多个不重叠的虚拟私有云(Virtual Private Cloud, VPC)网段通过 Direct Connect 网关(Direct Connect Gateway, DXGW)连接本地网络(on-premises network)。

English

The routing topology shows multiple non-overlapping VPC prefixes connected to an on-premises network through a DXGW.

Transcript

04:27 So first of all, all these CIDR which you allocate to VPCs should be different.

04:33 And then this communication via the DX Gateway is not allowed.

17. 重叠 CIDR 被拒绝

时间范围:04:38–04:42

Routing diagram marking overlapping VPC CIDRs as invalid

总结 / Summary

中文

图中的红色叉号强调:具有重叠无类别域间路由(Classless Inter-Domain Routing, CIDR)的虚拟私有云(Virtual Private Cloud, VPC)不能同时关联到同一个 Direct Connect 网关(Direct Connect Gateway, DXGW)。

English

The red X emphasizes that VPCs with overlapping CIDRs cannot be associated with the same DXGW.

Transcript

04:38 OK. So moving on

18. IPv4 与 IPv6 路由上限

时间范围:04:42–05:00

Maximum one hundred IPv4 and IPv6 routes advertised from on premises

总结 / Summary

中文

从本地网络(on-premises network)经 Direct Connect 网关(Direct Connect Gateway, DXGW)向 AWS 通告的 IPv4 和 IPv6 路由各最多 100 条;该上限与私有虚拟接口(Private VIF)和传输虚拟接口(Transit VIF)一致。

English

Up to 100 IPv4 routes and 100 IPv6 routes may be advertised from on premises to AWS through a DXGW.

Transcript

04:42 with respect to the routes, the maximum 100 routes each for IPv4

04:47 addresses and IPv6

04:48 addresses can be advertised from

04:51 on-premises to AWS over the DX Gateway.

04:54 Now, this limit is ultimately same as the private VIF or Transit VIF limit.

04:59 So

19. DXGW 路由交换拓扑

时间范围:05:00–05:03

Direct Connect Gateway routes base topology

总结 / Summary

中文

该拓扑用于说明本地网络(on-premises network)与 AWS 虚拟私有云(Virtual Private Cloud, VPC)前缀如何通过边界网关协议(Border Gateway Protocol, BGP)双向交换。

English

This topology introduces bidirectional BGP route exchange between on-premises networks and AWS VPC prefixes.

Transcript

05:00 when you associate this connection

20. 本地路由通告

时间范围:05:03–05:22

On-premises prefixes advertised toward AWS

总结 / Summary

中文

客户路由器(Customer Router)向 Direct Connect 网关(Direct Connect Gateway, DXGW)通告本地网络(on-premises network)的路由前缀。

English

The customer router advertises on-premises prefixes toward the Direct Connect Gateway.

Transcript

05:03 from AWS side, you will publish all the routes from your VPCs.

05:08 So DX Gateway will learn about those routes.

05:10 And as the BGP session is established between DX Gateway and the customer router,

05:16 it will advertise all the VPC prefixes, right?

05:19 And at the same time from corporate data center,

21. VPC 路由通告

时间范围:05:22–05:31

VPC prefixes advertised toward the customer router

总结 / Summary

中文

Direct Connect 网关(Direct Connect Gateway, DXGW)学习已关联虚拟私有云(Virtual Private Cloud, VPC)的前缀,并通过边界网关协议(Border Gateway Protocol, BGP)将其通告给客户路由器(Customer Router)。

English

The DXGW learns associated VPC prefixes and advertises them to the customer router through BGP.

Transcript

05:22 you will advertise your side of the CIDR ranges.

05:26 Now, you can't publish more than 100 routes each for IPv4

22. 超限风险与路由聚合

时间范围:05:31–05:58

Route limit callout on Direct Connect Gateway routing diagram

总结 / Summary

中文

通告超过 IPv4 或 IPv6 的 100 条路由上限可能导致边界网关协议(Border Gateway Protocol, BGP)会话中断;可使用路由聚合(route aggregation)减少前缀数量。

English

Advertising more than the 100-route limit can bring down the BGP session, so route aggregation should be used where possible.

Transcript

05:31 and then 100 routes for IPv6

05:33 addresses.

05:34 And if you do that,

05:35 that means if you

05:37 advertise more than 100 routes, then your BGP session

05:40 may go down,

05:42 right? So you have to take care of that.

05:44 And one of the ways to do that is aggregating your routes.

05:47 So instead of sending multiple smaller prefixes,

05:51 you just combine it into a larger prefix if it

05:54 is possible and then just advertise limited number of routes.

23. DXGW 的 VPC 数量限制

时间范围:05:58–06:01

Direct Connect Gateway VPC limits title slide

总结 / Summary

中文

Direct Connect 网关(Direct Connect Gateway, DXGW)可关联的虚拟私有网关(Virtual Private Gateway, VGW)和虚拟私有云(Virtual Private Cloud, VPC)数量受服务配额限制。

English

The number of VGWs and VPCs that can be associated with a DXGW is governed by a service quota.

Transcript

05:58 Now, with respect to the limits as of today,

24. 当前最多 20 个 VGW

时间范围:06:01–06:13

Single Direct Connect Gateway can connect to twenty Virtual Private Gateways

总结 / Summary

中文

课程录制时,单个 Direct Connect 网关(Direct Connect Gateway, DXGW)最多可连接 20 个虚拟私有网关(Virtual Private Gateway, VGW),也就是 20 个虚拟私有云(Virtual Private Cloud, VPC);该数字可能变化。

English

At recording time, one DXGW could connect to up to 20 VGWs, corresponding to 20 VPCs, but the quota may change.

Transcript

06:01 you can associate maximum 20 virtual private gateways,

06:05 which means ultimately VPCs to the same DX Gateway

06:09 and this limit may change in the future. So always

25. 以最新 AWS 文档为准

时间范围:06:13–06:29

Callout to check AWS documentation for the latest limits

总结 / Summary

中文

设计架构时应始终查阅最新 AWS 文档和服务配额(Service Quotas),不要把课程中的数量视为永久固定值。

English

Architecture decisions should always use current AWS documentation and Service Quotas rather than treating recorded limits as permanent.

Transcript

06:13 refer to the AWS documentation for any limit numbers.

06:17 Now, typically in the exam,

06:18 you won't be asked about these numbers because they are ever changing.

06:22 But just for your understanding,

06:24 when you design the architecture, you need to consider those limits

26. 创建 DXGW 演示

时间范围:06:29–06:30

Creating Direct Connect Gateway walkthrough title slide

总结 / Summary

中文

接下来演示如何在 AWS 管理控制台(AWS Management Console)中创建 Direct Connect 网关(Direct Connect Gateway, DXGW)。

English

The walkthrough demonstrates how to create a Direct Connect Gateway in the AWS Management Console.

Transcript

06:29 moving on.

27. 打开 Direct Connect 控制台

时间范围:06:30–06:38

AWS Direct Connect console landing page

总结 / Summary

中文

在 AWS 管理控制台(AWS Management Console)进入 Direct Connect 服务,然后选择 Direct Connect 网关(Direct Connect Gateway)页面。

English

Open the Direct Connect service in the AWS Management Console and navigate to Direct Connect gateways.

Transcript

06:30 Now, quickly, let's look how to create the DirectConnect Gateway.

06:34 So I'm into my AWS console and if you go to the DirectConnect Gateway,

28. Direct Connect Gateways 列表

时间范围:06:38–06:41

Direct Connect gateways list in AWS console

总结 / Summary

中文

Direct Connect 网关(Direct Connect Gateway)是全局服务,可从列表页查看现有网关并启动创建流程。

English

Direct Connect Gateway is a global service; the list page shows existing gateways and provides the create action.

Transcript

06:38 you can see that this is a Global service again

29. 创建 Direct Connect Gateway

时间范围:06:41–06:45

Create Direct Connect gateway form

总结 / Summary

中文

创建表单要求提供 Direct Connect 网关(Direct Connect Gateway, DXGW)名称和 Amazon 侧自治系统编号(Amazon-side Autonomous System Number, ASN)。

English

The creation form requires a DXGW name and an Amazon-side Autonomous System Number (ASN).

Transcript

06:41 and you can just say create DirectConnect Gateway and say my

30. 填写网关名称

时间范围:06:45–06:51

Direct Connect gateway name entered in creation form

总结 / Summary

中文

为 Direct Connect 网关(Direct Connect Gateway, DXGW)填写可识别的名称,例如 “MyDXGW”。

English

Enter a recognizable name for the Direct Connect Gateway, such as “MyDXGW.”

Transcript

06:45 DX Gateway.

06:47 And then you have to provide the Amazon side of the ASN.

31. 配置 Amazon 侧 ASN

时间范围:06:51–07:09

Amazon side ASN entered for Direct Connect Gateway

总结 / Summary

中文

为 Direct Connect 网关(Direct Connect Gateway, DXGW)填写 Amazon 侧自治系统编号(Amazon-side Autonomous System Number, ASN),可使用允许范围内的私有 ASN,例如 64512。

English

Provide an allowed private Amazon-side ASN for the DXGW, such as 64512.

Transcript

06:51 Now,

06:51 there are no other settings here because most of

06:53 the settings will be taken from your private VIF.

06:56 That means what is required here is just an Amazon side of the ASN

07:00 and then you can provide a private ASN in the range that is given here.

07:04 So I can take like 64512 as it is given there

32. DXGW 创建完成

时间范围:07:09–07:14

New Direct Connect Gateway displayed in the gateways list

总结 / Summary

中文

创建完成后,新 Direct Connect 网关(Direct Connect Gateway, DXGW)会出现在全局网关列表中并显示可用状态。

English

After creation, the new DXGW appears in the global gateway list with an available status.

Transcript

07:09 and just create the DirectConnect Gateway.

07:11 Now, if you remember while we created Private Virtual Interface,

33. 进入 Virtual Interfaces

时间范围:07:14–07:20

Virtual interfaces list in AWS Direct Connect console

总结 / Summary

中文

随后进入虚拟接口(Virtual Interface, VIF)列表,创建用于连接该 Direct Connect 网关(Direct Connect Gateway, DXGW)的私有虚拟接口(Private VIF)。

English

Next, open the Virtual Interfaces list to create a Private VIF for the Direct Connect Gateway.

Transcript

07:14 it was asking like whether it has to be

07:16 connected to the VGW or a DirectConnect Gateway.

34. 创建虚拟接口

时间范围:07:20–07:23

Create virtual interface page in AWS console

总结 / Summary

中文

在创建虚拟接口(Virtual Interface, VIF)页面选择接口类型,并准备填写连接、所有者、网关与边界网关协议(Border Gateway Protocol, BGP)参数。

English

On the Create virtual interface page, choose the interface type and prepare the connection, owner, gateway, and BGP settings.

Transcript

07:20 And that's where now when your direct connect Gateway is created.

35. 选择 Private VIF

时间范围:07:23–07:24

Private virtual interface type selected

总结 / Summary

中文

选择私有虚拟接口(Private Virtual Interface, Private VIF),以便将 Direct Connect 连接接入私有 AWS 网络。

English

Select a Private Virtual Interface to connect Direct Connect to private AWS networking.

Transcript

07:23 So

36. 填写 VIF 名称与连接

时间范围:07:24–07:26

Private virtual interface name and connection fields

总结 / Summary

中文

在私有虚拟接口(Private VIF)设置中填写 VIF 名称,并选择它所使用的 Direct Connect 连接(Direct Connect Connection)。

English

In the Private VIF settings, enter the VIF name and select the Direct Connect connection it will use.

Transcript

07:24 you can see that

37. 设置 VIF 所有者

时间范围:07:26–07:31

Private virtual interface owner account settings

总结 / Summary

中文

选择虚拟接口所有者(Virtual Interface Owner);若使用当前账户,则私有虚拟接口(Private VIF)与 Direct Connect 网关(Direct Connect Gateway, DXGW)可满足同账户要求。

English

Choose the Virtual Interface Owner; using the current account keeps the Private VIF and DXGW in the same account.

Transcript

07:26 my private VIF would allow me to connect to that particular DirectConnect Gateway.

38. 选择 Direct Connect Gateway

时间范围:07:31–07:42

Direct Connect Gateway selected as the Private VIF gateway type

总结 / Summary

中文

将网关类型(Gateway Type)设为 Direct Connect 网关(Direct Connect Gateway),控制台会自动列出当前账户中可关联的 DXGW。

English

Set the Gateway Type to Direct Connect Gateway, and the console automatically lists eligible DXGWs in the account.

Transcript

07:31 So here if you select DirectConnect Gateway, then it is automatically populated.

07:35 So this is how you create a direct connect Gateway and then

07:38 create a private VIF and attach it to the DirectConnect Gateway.

39. 配置 Private VIF 网络参数

时间范围:07:42–07:47

Lower Private VIF settings including VLAN and BGP

总结 / Summary

中文

继续配置虚拟局域网(Virtual LAN, VLAN)、对等点 IP 地址和边界网关协议(Border Gateway Protocol, BGP)等私有虚拟接口(Private VIF)参数。

English

Complete the Private VIF configuration with VLAN, peer IP addresses, and BGP settings.

Transcript

07:42 So with that, now let's move to the next part of this lecture.

40. DXGW 架构示例

时间范围:07:47–07:54

Direct Connect Gateway architectures title slide

总结 / Summary

中文

后半部分比较多 Direct Connect 网关(Direct Connect Gateway, DXGW)和多客户站点(customer site)的常见部署方式。

English

The second half compares common architectures using multiple DXGWs and multiple customer sites.

Transcript

07:47 So let's look at a few DX Gateway architecture

07:51 while you associate that with the private VIF.

41. 多个 DXGW 共用一条连接

时间范围:07:54–08:54

Multiple Direct Connect Gateways on one Direct Connect connection

总结 / Summary

中文

一条 Direct Connect 连接可通过不同私有虚拟接口(Private VIF)接入多个 Direct Connect 网关(Direct Connect Gateway, DXGW),从而突破单个 DXGW 可关联虚拟私有网关(Virtual Private Gateway, VGW)数量的限制。

English

One Direct Connect connection can use separate Private VIFs for multiple DXGWs, allowing the design to scale beyond one DXGW's VGW association quota.

Transcript

07:54 So this is one architecture where you can have multiple DX gateways and you can

08:00 associate that on the same DX connection

08:03 using different private VIFs. Now the question is why you will do that.

08:07 Typically, this is required if you want to go beyond the limit,

08:11 how many number of VGWs you can associate with a single DX gateways.

08:16 as you know, this limit is 20 currently, which might increase.

08:19 But if more than 20 VPCs you want to connect,

08:22 then you can go with this kind of the architecture.

08:26 Now, there is other architectures like using Transit gateways.

08:30 But we'll talk about that shortly.

08:33 There are reasons for using it and not to use it.

08:37 But in case where Transit Gateway is not recommended,

08:41 you can then use multiple DX gateways in this fashion.

08:46 So this will allow the connectivity between all these VPCs across AWS Region

08:51 to your corporate data center.

42. 多个客户站点共用一个 DXGW

时间范围:08:54–09:42

One Direct Connect Gateway connected to multiple customer sites

总结 / Summary

中文

全球分布的多个客户站点(customer site)可在不同 Direct Connect 位置建立连接,并通过多个私有虚拟接口(Private VIF)汇聚到同一个全局 Direct Connect 网关(Direct Connect Gateway, DXGW)。

English

Multiple globally distributed customer sites can use different Direct Connect locations and Private VIFs while converging on one global DXGW.

Transcript

08:54 Similarly,

08:55 if you have multiple customer sites and all needs

08:59 to communicate with your VPCs in AWS,

09:02 then you can associate multiple private VIFs to a same DX Gateway.

09:07 Right?

09:08 Again,

09:08 this is a very common architecture where customer has

09:12 a Global presence and sites across the world.

09:15 And customer will use multiple DX location depending on where that site is located.

09:21 But ultimately, all this DX connection

09:24 can get into the same DX Gateway, which is a Global Gateway.

09:29 And then you associate all your VPCs across the Region to this DX Gateway.

09:34 However,

09:35 one thing to remember again is that you can't have

09:38 VPC communicate to each other through this DX Gateway.

43. VPC 与本地站点可互通

时间范围:09:42–10:09

Full routing between VPCs and on-premises sites through Direct Connect Gateway

总结 / Summary

中文

Direct Connect 网关(Direct Connect Gateway, DXGW)允许虚拟私有云(Virtual Private Cloud, VPC)与本地站点(on-premises site)之间进行完整路由,但不提供 VPC 间传输。

English

The DXGW supports full routing between VPCs and on-premises sites, but it does not provide VPC-to-VPC transit.

Transcript

09:42 And we will see that while looking at

09:44 the Transit Gateway with DX Gateway architectures,

09:48 OK.

09:49 Another thing is that even this corporate

09:51 data center network cannot communicate with each other

09:55 over this DX Gateway. That means if site A is not connected to

10:00 site B directly,

10:01 but they are attached to the DX Gateway in this fashion,

10:05 they cannot also route the traffic between them through this DX Gateway.

44. 客户站点间传输受限

时间范围:10:09–10:13

Red dashed paths indicating disallowed routing between customer sites

总结 / Summary

中文

红色虚线表示不能把 Direct Connect 网关(Direct Connect Gateway, DXGW)当作客户站点到客户站点(site-to-site)的传输路由器。

English

The red dashed paths show that a DXGW cannot be used as a transit router between customer sites.

Transcript

10:09 And later, we will see how to solve this problem.

45. 客户站点之间无路由

时间范围:10:13–10:17

No routing between customer sites through Direct Connect Gateway

总结 / Summary

中文

即使多个客户站点都连接到同一个 Direct Connect 网关(Direct Connect Gateway, DXGW),它们也不能经由 DXGW 相互路由。

English

Even when multiple customer sites attach to the same DXGW, they cannot route traffic to each other through it.

Transcript

10:13 OK.

10:13 So no Routing between the customer sites.

46. Private VIF + DXGW 总结

时间范围:10:17–10:54

Direct Connect Gateway and Private VIF feature summary

总结 / Summary

中文

Direct Connect 网关(Direct Connect Gateway, DXGW)是全局资源,支持本地网络(on-premises network)与多区域、多账户虚拟私有云(Virtual Private Cloud, VPC)的私有连接;VPC 的无类别域间路由(CIDR)不得重叠,且 DXGW 不提供 VPC 间通信。私有虚拟接口(Private VIF)与 DXGW 必须属于同一账户。

English

A DXGW provides global private connectivity from on premises to VPCs across Regions and accounts. VPC CIDRs must not overlap, VPC-to-VPC transit is unsupported, and the Private VIF and DXGW must share an account.

Transcript

10:17 Again, the summary,

10:18 while using the DX Gateway with private VIF DX gateways are globally accessible,

10:24 they allow the connectivity between the

10:26 om-premise network and AWS VPC.

10:29 As of today, you can connect 20 VGWs to a single DX Gateway. But this limit can change

10:35 for connecting VGW,

10:37 the VPC CIDRs should not be overlapping, VPC to VPC communication is not allowed

10:44 via the DX Gateway.

10:46 And then with respect to the account ownership,

10:48 the DX Gateway and the private WAF should be created in the same AWS account.

47. DXGW 成本模型

时间范围:10:54–11:54

Direct Connect Gateway and Private VIF cost summary

总结 / Summary

中文

Direct Connect 网关(Direct Connect Gateway, DXGW)本身不收费;仍需支付 Direct Connect 端口小时费(port-hour charge)以及从远端 AWS 区域(AWS Region)流出的适用数据传输费(egress data transfer charge)。

English

There is no separate charge for a DXGW, but Direct Connect port-hour charges and applicable egress data-transfer charges from the source Region still apply.

Transcript

10:54 With respect to the cost. DX Gateway doesn't have their own cost, they come free.

11:01 But as the traffic flows through the DX Gateway, and we are talking about the

11:06 ingress and

11:07 egress traffic.

11:08 So for ingress, there is no particular cost with respect to the data transfer.

11:13 But as the traffic goes out of the DX Gateway to your

11:17 on-premises

11:17 network, again, the standard

11:19 DirectConnect

11:20 egress charge will be applicable.

11:22 And at all the time, the DX

11:24 port hour charges will be applicable.

11:26 Now, these are not the charges which are directly associated with the DX Gateway,

11:31 but these are the charges for DX connection,

11:33 which anyways you will pay whether you use DX Gateway or not.

11:38 So those are the few other things that you need to remember.

11:42 So that's it for this lecture.

11:43 We learned about using DX Gateway with private VIF.

11:47 And now let's look at using DX Gateway with the Transit VIF.

11:51 So thanks for watching.

整讲总结 / Overall Summary

中文

Direct Connect 网关(Direct Connect Gateway, DXGW)让一条 Direct Connect 连接通过私有虚拟接口(Private VIF)服务多个区域或账户中的虚拟私有云(Virtual Private Cloud, VPC)。Private VIF 与 DXGW 必须位于同一 AWS 账户,关联的 VPC 无类别域间路由(CIDR)不能重叠,DXGW 不支持 VPC 到 VPC 或客户站点到客户站点的传输路由。本地侧可向 AWS 通告的 IPv4 与 IPv6 路由各有 100 条上限,超限时应使用路由聚合(route aggregation)。DXGW 本身免费,但 Direct Connect 端口小时费和出口数据传输费仍然适用。

English

A Direct Connect Gateway (DXGW) lets one Direct Connect connection serve VPCs across multiple Regions or accounts through a Private VIF. The Private VIF and DXGW must share an AWS account, associated VPC CIDRs cannot overlap, and the DXGW does not provide VPC-to-VPC or customer-site-to-customer-site transit. Up to 100 IPv4 and 100 IPv6 routes may be advertised from on premises, so route aggregation is important. The DXGW itself has no separate charge, but Direct Connect port-hour and egress data-transfer charges still apply.

返回顶部 ↑