Lecture 125: Private VIF
- 课程：[NEW] AWS Certified Advanced Networking Specialty 2026
- 视频时长：12:12
- 来源：Udemy Lecture 27896610
- Slide 数量：27
- 画面切换：00:14、00:32、00:42、01:15、01:26、02:18、02:38、03:16、06:06、06:31、07:13、07:38、08:39、08:41、08:44、09:00、09:11、09:19、09:28、09:58、10:07、10:12、10:18、10:39、11:10、11:37
扫描说明
逐条检查了 Udemy 页面中的 290 条 Transcript cue，并以每条 cue 对应画面扫描了全长约 12:12 的视频。依据 Private VIF 理论幻灯片的逐步呈现、子网路由传播拓扑、VPC 内资源可达性标注、控制台创建流程和结尾复习页，共划分为 27 个小节。正式截图均在锁定 Lecture 27896610、Autoplay 关闭、视频播放且底部控件隐藏后，按完整媒体边界截取并输出为 1364×770，逐张复核了左右与底部边界。
Transcript 来自 Udemy 页面自带的英文自动字幕，没有使用 ASR。下面保留页面原文，包括其中的语法或识别错误。
1. Private VIF 概览
时间范围：00:00–00:14
总结 / Summary
中文
私有虚拟接口（Private Virtual Interface, Private VIF）通过 AWS Direct Connect 连接本地数据中心与虚拟私有云（Virtual Private Cloud, VPC）中的私有资源。
English
A Private Virtual Interface (Private VIF) uses AWS Direct Connect to connect an on-premises data center with private resources inside a VPC.
Transcript
00:00 Okay. Let's now, let's turn the private VIF.
00:03 And, in case of private VIF, as you know,
00:05 it is used to access the private resources inside the VPC,
00:10 and, that's where, let's see the other properties,
00:12 with respect to the same.
2. 使用私有 IP 访问 VPC 资源
时间范围：00:14–00:32
总结 / Summary
中文
Private VIF 允许本地网络使用私有 IP 地址访问 Amazon EC2、Amazon RDS、Amazon Redshift 等 VPC 内资源，无需走公网。
English
A Private VIF lets the on-premises network reach VPC resources such as Amazon EC2, RDS, and Redshift by private IP address without traversing the public Internet.
Transcript
00:14 So, it enables the network connectivity,
00:16 from your data center,
00:18 and on-premises network to the VPC,
00:20 using private IPs for resources, like EC2, RDS, Redshift.
00:24 All these are part of your VPC,
00:26 and then all these resources,
00:27 you can access using their private IP addresses.
3. 通过 VGW 关联 VPC
时间范围：00:32–00:42
总结 / Summary
中文
先把虚拟私有网关（Virtual Private Gateway, VGW）附加到 VPC，再将 Private VIF 与该 VGW 关联，形成本地到 VPC 的私有路径。
English
A Virtual Private Gateway (VGW) is attached to the VPC and then associated with the Private VIF to form the private on-premises-to-VPC path.
Transcript
00:32 You must attach your VPC to the virtual private gateway,
00:35 and, by creating the private VIF,
00:37 you should then associate that VGW to the private VIF.
4. Private VIF 与 VGW 必须同 Region
时间范围：00:42–01:15
总结 / Summary
中文
直接关联时，Private VIF 与 VGW 必须位于同一 AWS 区域（AWS Region），因此只能访问该区域的 VPC；跨区域连接需使用 Direct Connect 网关（Direct Connect Gateway, DXGW）。
English
With direct VGW association, the Private VIF and VGW must be in the same AWS Region, limiting access to that Region; cross-Region connectivity requires a Direct Connect Gateway.
Transcript
00:42 Now, understand, that private VIF
00:43 and virtual private gateway,
00:46 must be in the same AWS Region.
00:48 And that's one distinction,
00:49 between the public and private VIF,
00:51 that we are talking about.
00:53 You can only access the VPCs in the same Region,
00:56 if you're attaching it,
00:57 to the virtual private gateway, directly.
01:00 Now, lately, AWS has also launched Direct Connect gateways,
01:04 which allows you to access,
01:06 or connect VPCs, across the Region,
01:08 but then we'll park that as of now,
01:09 and let's consider the private VIF connection,
01:12 with virtual private gateway.
5. BGP 交换 VPC 与本地前缀
时间范围：01:15–01:26
总结 / Summary
中文
边界网关协议（Border Gateway Protocol, BGP）会话建立后，客户路由器接收 VPC 前缀，客户侧也可向 AWS 发布本地私有网络前缀。
English
After the BGP session is established, the customer router receives VPC prefixes and can advertise on-premises private-network prefixes to AWS.
Transcript
01:15 Now, when you have set up your BGP session,
01:19 customer router will also receive all the prefixes,
01:23 of your VPCs, right?
6. 最多发布 100 条客户前缀
时间范围：01:26–02:18
总结 / Summary
中文
Private VIF 每个 BGP 会话最多向 AWS 发布 100 条客户前缀，超限可能导致会话中断；启用路由传播（route propagation）后，这些路由可自动进入 VPC 路由表。
English
A Private VIF accepts at most 100 customer prefixes per BGP session; exceeding the limit can bring the session down. With route propagation enabled, learned routes can enter VPC route tables automatically.
Transcript
01:26 Similarly, you can also advertise your side,
01:29 of the prefixes, or the private VIF.
01:32 Now, we understood, that in case of public VIF,
01:34 you can maximum, advertise 1000 prefixes,
01:38 but, in case of private VIF,
01:40 you can only advertise 100 prefixes to the AWS.
01:44 So make sure you don't advertise more than that,
01:46 otherwise BGP session will go down.
01:49 Now, the routes that have been advertised,
01:51 from your end or the customer end,
01:54 these routes can be automatically propagated,
01:57 into the route table subnets,
01:59 if, of course, you have enabled the route propagation,
02:02 enabled at the Subnet level.
02:04 So, in that case,
02:05 all the routes will automatically get into your subnets,
02:08 and any traffic which falls under that IP address ranges,
02:12 will be routed through the private VIF,
02:14 if the traffic is going from AWS,
02:16 to your side of the network.
7. 通过 Route Summarization 控制数量
时间范围：02:18–02:38
总结 / Summary
中文
当本地网络超过 100 个前缀时，可使用路由汇总（route summarization）把多个小网段合并为较大的 CIDR 前缀。
English
When the on-premises network has more than 100 prefixes, route summarization can combine multiple smaller networks into larger CIDR prefixes.
Transcript
02:18 Now, in order to advertise more than 100 prefixes,
02:21 you can do route summarization,
02:23 similar to what we have explained during the public VIF.
02:27 So, instead of having small prefix ranges,
02:30 you can just advertise one large prefix range,
02:34 which, ultimately, covers all those small address ranges.
8. 传播路由优先于默认互联网路由
时间范围：02:38–03:16
总结 / Summary
中文
从 VGW 传播的更具体路由优先于指向互联网网关（Internet Gateway, IGW）的 0.0.0.0/0 默认路由，因此匹配的本地流量会进入 Private VIF。
English
A more specific route propagated from the VGW takes precedence over the 0.0.0.0/0 default route to the Internet Gateway, sending matching on-premises traffic through the Private VIF.
Transcript
02:38 And, note that the propagated routes will take precedence,
02:42 over the default route, into your subnets.
02:44 That means, if you have a route for the internet,
02:47 0.0.0.0,
02:49 is the destination and the target is internet gateway.
02:53 And, if there is,
02:55 a match, happens,
02:57 with your propagated route, for the target,
03:00 which resides in the customer network site,
03:04 then instead of internet gateway,
03:06 it will choose the route through the private VIF,
03:08 because it's a propagated route,
03:10 which your subnet learnt,
03:12 over the BGP session from the customer network site.
9. 子网 Route Table 的路由选择
时间范围：03:16–06:06
总结 / Summary
中文
拓扑示例展示 VPC CIDR、本地 CIDR、VGW、Private VIF 与子网路由表。开启 VGW 路由传播后，本地前缀自动成为传播路由（propagated route）；最长前缀匹配会选中 VGW，而不是 IGW 默认路由。
English
The topology shows the VPC and on-premises CIDRs, VGW, Private VIF, and subnet route table. VGW propagation installs on-premises prefixes as propagated routes, and longest-prefix matching selects the VGW instead of the IGW default route.
Transcript
03:16 And now, let's see, what do I mean by that?
03:19 So, this is the architecture,
03:21 where you have the Direct Connect connection,
03:24 and then you create a virtual private gateway,
03:26 attach it to your VPC,
03:27 and then you have a private VIF,
03:29 attached to the virtual private gateway.
03:32 Now, we have considered that CIDR,
03:34 for your VPC,
03:35 is 10.10.0.0/16,
03:37 and for on-premises,
03:39 it's 192.168.0.0/24,
03:41 for this particular network.
03:43 And then there could be other network,
03:44 inside this data center as well.
03:48 With respect to that, we have now two subnets here,
03:51 and the two EC2 machines inside the subnet,
03:53 and the subnet would also have the route tables,
03:55 and for internet connectivity, we have internet gateway.
03:59 Now, you know that when you create a subnet,
04:02 there is always a local route, right?
04:04 For the local VPC CIDR. And if it is a public subnet,
04:07 you will also add a route of internet destination,
04:11 that is 0.0.0/0.
04:13 And the traffic will roll through the internet gateway.
04:17 And these are both the static type of the routes.
04:20 Now, when you create a private VIF,
04:22 and then you have a virtual private gateway,
04:25 you can modify your subnet,
04:27 and say that all the traffic,
04:30 which goes to the 192.168.0.0/24,
04:33 has to be going through the virtual private gateway, right?
04:38 Now, either you do it statically, into your route table,
04:41 or, as you have attached the virtual private gateway,
04:45 to your VPC, you can just enable the route propagation,
04:49 for this virtual private gateway.
04:50 And then all the routes,
04:52 that it learns from on-premises network,
04:54 will be automatically propagated to your subnet.
04:57 Now, for example, I have shown that,
05:00 if it learned about three such prefixes,
05:07 then, automatically,
05:04 it says the traffic, for this destination,
05:07 should be going through the virtual private gateway,
05:09 and ultimately, through private VIF,
05:11 to the corporate data center.
05:12 And that's where, suppose now,
05:14 you're EC2 is trying to reach to this machine,
05:16 which has an IP address of 192.168.0/10.
05:20 Now, you know that this address,
05:21 does not fall into the local address,
05:24 so, this part will not be taken,
05:26 but then there is an internet gateway,
05:27 which matches all the IP addresses.
05:29 So, technically it matches this IP address,
05:33 but, because there is a propagated route,
05:36 through virtual private gateway,
05:37 for the same IP address range,
05:41 under which this IP address falls, it will take this part.
05:45 So, the traffic from your subnet,
05:47 to this particular IP address,
05:49 will take the path through virtual private gateway,
05:52 and through Direct Connect connection,
05:54 the traffic will flow.
05:55 So, this is what I mean,
05:57 when I say the propagated route will take precedence,
06:01 over the internet gateway routes.
06:03 So, just remember that.
10. MTU 1500 与 Jumbo Frame 9001
时间范围：06:06–06:31
总结 / Summary
中文
Private VIF 默认最大传输单元（Maximum Transmission Unit, MTU）为 1500 字节，也可为传播路由启用 9001 字节巨型帧（jumbo frame）。
English
A Private VIF uses a 1,500-byte MTU by default and can enable 9,001-byte jumbo frames for propagated routes.
Transcript
06:06 And finally,
06:07 the private VIF supports MTU of 1500, by default,
06:11 but then you can enable it,
06:12 to support,
06:14 the jumbo frame,
06:15 of size 9001.
06:17 And, this is applicable only for the propagated routes.
06:21 So, essentially, that is what the private VIF is all about.
06:24 And, just,
06:25 to make it,
06:26 more clear, what you can access inside VPC,
06:29 and what you cannot,
11. Private VIF 的 VPC 可达性边界
时间范围：06:31–07:13
总结 / Summary
中文
Private VIF 可到达 VPC 中的 EC2、数据库和接口端点（interface endpoint），但并非所有 VPC 内建服务都可通过该路径访问。
English
A Private VIF can reach EC2 instances, databases, and interface endpoints in a VPC, but not every VPC-provided service is reachable through this path.
Transcript
06:31 let's look at that.
06:33 So, when you have this connection,
06:35 you have Direct Connect location,
06:37 you have Direct Connect router, here,
06:39 and from there you create a private VIF,
06:41 and you attach to the virtual private gateway.
06:43 Now, inside your VPC,
06:44 you will be having multiple networking components,
06:47 as well as your resources.
06:48 There will be databases, as well as EC2 machine.
06:52 There could be VPC endpoint, gateway endpoint,
06:55 as well as interface endpoint.
06:57 And you know that VPC base address, plus two
07:00 will run the local DNS server,
07:02 which resolves all the DNS queries,
07:05 using the Route 53.
07:07 Now, when this is the case,
07:09 let's understand what you can access,
07:10 from your on-premises network and what you cannot.
12. 不能直接访问 VPC DNS Resolver
时间范围：07:13–07:38
总结 / Summary
中文
本地网络不能通过 Private VIF 直接查询 VPC 基址加 2 的 DNS 解析器（DNS resolver）；私有域名解析需另行使用 Route 53 Resolver。
English
The on-premises network cannot query the VPC DNS resolver at the VPC base address plus two through a Private VIF; private DNS resolution requires Route 53 Resolver.
Transcript
07:13 So, while you can access all EC2 machines,
07:15 and databases, inside your VPC,
07:17 you can't really access this DNS service endpoint.
07:21 That means you can't resolve the DNS,
07:23 the private DNS for your VPC,
07:25 from your corporate data center.
07:28 Now, in order to do that,
07:30 there is a different mechanism.
07:32 You can use a Route 53 resolver,
07:35 but that will be covered in the different section.
13. 不能访问 VPC Gateway Endpoint
时间范围：07:38–08:39
总结 / Summary
中文
网关端点（gateway endpoint）依赖 VPC 路由表且不提供传递路由（transitive routing），因此本地网络不能经 Private VIF 访问它；创建弹性网络接口（Elastic Network Interface, ENI）的接口端点则可访问。
English
A gateway endpoint relies on VPC route-table behavior and does not provide transitive routing, so it cannot be reached from on premises through a Private VIF; an interface endpoint backed by an ENI can be reached.
Transcript
07:38 And the second component you can't access,
07:40 is VPC gateway endpoints.
07:43 Now, if you remember from our earlier discussion,
07:46 VPC provides two types of the endpoints,
07:49 interface endpoints, and the gateway endpoints.
07:51 In case of gateway endpoints, you can access AWS services,
07:54 within the same Region, like S3 and DynamoDB.
07:57 And you have to modify your subnet route table
08:00 to route that traffic through the gateway endpoint.
08:03 And there is another type of the endpoint,
08:04 that is, interface endpoint,
08:05 where it creates an ENI into your VPC,
08:08 and then you can access other AWS services endpoints,
08:11 which are supported by interface endpoint.
08:14 Because, because this is,
08:16 again, not the transitive routing,
08:20 you can't access the gateway endpoint via your private VIF.
08:23 However, because there is ENI created into your VPC,
08:27 you can still access the interface endpoint targets,
08:30 but not the gateway endpoint targets.
08:32 So, remember these two things.
08:34 Just to show you, here.
08:36 So you can, access EC2 machines, databases.
14. EC2 与 Interface Endpoint 可达
时间范围：08:39–08:41
总结 / Summary
中文
图中的绿色标记确认 Amazon EC2 实例和接口端点（interface endpoint）可通过 Private VIF 从本地访问。
English
Green checks confirm that EC2 instances and interface endpoints are reachable from on premises through the Private VIF.
Transcript
08:39 You can access interface endpoint,
15. VPC DNS 不可达
时间范围：08:41–08:44
总结 / Summary
中文
红色标记强调 VPC DNS 解析器（VPC DNS resolver）不能直接通过 Private VIF 访问。
English
A red cross emphasizes that the VPC DNS resolver is not directly reachable through the Private VIF.
Transcript
08:41 but then you can't access DNS,
16. Gateway Endpoint 同样不可达
时间范围：08:44–09:00
总结 / Summary
中文
最终标注同时排除 VPC DNS 解析器和网关端点（gateway endpoint），而 EC2 与接口端点保持可达。
English
The final annotations mark both the VPC DNS resolver and gateway endpoint as unreachable while EC2 instances and interface endpoints remain reachable.
Transcript
08:44 as well as gateway endpoints.
08:47 So, overall, that's what is private VIF
08:50 and understand these restrictions.
08:52 Now, let's try to create a private VIF,
08:55 or at least let's see what parameters it takes,
08:57 while creating the private VIF.
17. 打开 Direct Connect Virtual Interfaces
时间范围：09:00–09:11
总结 / Summary
中文
在 AWS Direct Connect 控制台的虚拟接口（Virtual interfaces）页面开始 Private VIF 创建演示。
English
The Private VIF walkthrough begins on the Virtual interfaces page of the AWS Direct Connect console.
Transcript
09:00 So, I'm into my Direct Connect console again.
09:03 And, as you know, I have one connection,
09:05 and I don't have any virtual interfaces.
09:07 So, this time, let's try to create virtual interfaces,
18. 选择 Private Virtual Interface
时间范围：09:11–09:19
总结 / Summary
中文
在虚拟接口类型（virtual interface type）中选择私有（Private），并为接口填写可识别的名称。
English
Private is selected as the virtual interface type, and the interface is given a descriptive name.
Transcript
09:11 as a private interface.
09:13 First thing, you need to give the interface names.
09:15 So, you can say, MyPrivateInterface,
19. 选择 Connection 与 Owner
时间范围：09:19–09:28
总结 / Summary
中文
选择承载 VIF 的 Direct Connect 连接（connection），并指定当前或其他 AWS 账户为虚拟接口所有者（virtual interface owner）；跨账户场景会形成托管 VIF（hosted VIF）。
English
The carrying Direct Connect connection and virtual interface owner are selected; using another AWS account creates a hosted VIF.
Transcript
09:19 and then you have to select the connection.
09:22 Again, if it's a hosted VIF,
09:23 then you would have to select another AWS account,
09:25 otherwise, it's your own AWS account.
20. 选择 VGW 或 Direct Connect Gateway
时间范围：09:28–09:58
总结 / Summary
中文
Private VIF 可关联虚拟私有网关（Virtual Private Gateway, VGW）或 Direct Connect 网关（Direct Connect Gateway, DXGW）；前者连接已附加的 VPC，后者支持更广泛的跨区域架构。
English
A Private VIF can associate with a Virtual Private Gateway (VGW) or a Direct Connect Gateway (DXGW); the former connects an attached VPC, while the latter supports broader cross-Region designs.
Transcript
09:28 Now, here is the gateway type.
09:30 Now, this option wasn't there for public VIF,
09:32 if you remember,
09:33 but private VIF can be attached,
09:35 to the virtual private gateway.
09:36 And this virtual private gateway,
09:38 needs to be attached to the VPC.
09:41 And then there is a new option,
09:42 to connect your private VIF to the Direct Connect gateway.
09:45 Now, we will see that in the next lecture,
09:47 where we discuss, in detail,
09:48 about the Direct Connect gateway.
09:50 So these are the two options you get.
09:53 Now, if you are selecting the virtual private gateway,
09:55 of course you need to have it created,
09:57 but right now it is not there.
21. 配置 VLAN
时间范围：09:58–10:07
总结 / Summary
中文
设置虚拟局域网标识（Virtual LAN identifier, VLAN ID），用于在 Direct Connect 物理连接上区分 Private VIF 流量。
English
A Virtual LAN identifier (VLAN ID) separates the Private VIF's traffic on the physical Direct Connect connection.
Transcript
09:58 And then, similar to public VIF, you to give the VLAN IDs,
10:04 and the BGP ASN for the customer router.
22. 配置 Private BGP ASN
时间范围：10:07–10:12
总结 / Summary
中文
填写客户路由器的私有边界网关协议自治系统编号（Border Gateway Protocol Autonomous System Number, BGP ASN）。
English
The private BGP Autonomous System Number (ASN) for the customer router is entered.
Transcript
10:07 Now this will be a private BGP ASN,
10:10 and, additionally,
23. 选择 IPv4 或 IPv6 Address Family
时间范围：10:12–10:18
总结 / Summary
中文
在地址族（address family）中选择 IPv4 或 IPv6，以决定 BGP 对等使用的协议版本。
English
IPv4 or IPv6 is selected as the address family for the BGP peering.
Transcript
10:12 you can specify the BGP settings,
10:14 like the BGP peer IPs will be IPV4 or IPV6.
24. 配置 BGP Peer IP
时间范围：10:18–10:39
总结 / Summary
中文
Private VIF 的客户与 Amazon 路由器 BGP 对等 IP（BGP peer IP）可从 169.254.0.0/16 链路本地范围选择；这些字段可留空，由 AWS 自动分配。
English
Customer and Amazon BGP peer IPs for a Private VIF can be selected from the 169.254.0.0/16 link-local range, or left blank for AWS to allocate automatically.
Transcript
10:18 And, in this case, you need to provide the BGP,
10:22 address range, in the range of,
10:23 169.254,
10:26 .0.0/16.
10:28 So, you can provide the range between, this,
10:32 uh, CIDR block,
10:34 for both your side of the router IPs,
10:36 and Amazon's side of the router IPs.
25. 可选 BGP Authentication Key
时间范围：10:39–11:10
总结 / Summary
中文
BGP 身份验证密钥（BGP authentication key）是可选项；若不填写，AWS 会自动生成。Private VIF 的对等 IP 也可自动分配，这与 Public VIF 的公共地址要求不同。
English
The BGP authentication key is optional and AWS generates one when omitted. Private VIF peer IPs can also be auto-assigned, unlike the public-address requirements of a Public VIF.
Transcript
10:39 And then, optionally, you can provide,
10:41 the BGP authentication key.
10:43 If you do not provide it, AWS will generate automatically.
10:46 And remember that all BGP peer IPs,
10:49 are also optional in this case,
10:51 but in case of public VIF,
10:52 either you have to provide the public IP range,
10:56 for your BGP peers,
10:58 and if you do not have it,
10:59 you can ask AWS and then you would have to provide that.
11:02 In case of private VIF, these are optional.
11:04 If you don't provide it, AWS will generate it for you.
11:08 And then finally, you can see here,
26. 启用 Jumbo Frame
时间范围：11:10–11:37
总结 / Summary
中文
控制台默认使用 1500 字节 MTU，也可启用巨型帧（jumbo frame），使传播路由使用 9001 字节 MTU。
English
The console defaults to a 1,500-byte MTU and can enable jumbo frames so propagated routes use a 9,001-byte MTU.
Transcript
11:10 by default, private VIF will support
11:13 the MTU of 1500 byte,
11:16 but you can enable the jumbo frame on this connection.
11:19 And then for propagated routes,
11:21 9001 byte of the MTU will be used.
11:25 So, essentially, those are the parameters for private VIF.
11:28 I'm not going to create it,
11:29 because I don't have the other settings.
11:32 Those are required to do this,
11:34 but, in general, remember all these parameters.
27. Remember：Private VIF 两项要点
时间范围：11:37–12:12
总结 / Summary
中文
记住两点：Private VIF 使用私有 IP 连接本地网络与 VPC 资源；客户每个 BGP 会话最多向 AWS 发布 100 条前缀。
English
Remember two key facts: a Private VIF connects on premises to VPC resources over private IPs, and the customer may advertise at most 100 prefixes to AWS per BGP session.
Transcript
11:37 So the key takeaways from this session.
11:39 That private VIF enables the connectivity,
11:42 between on-premise network and AWS VPC.
11:46 And that's where you can access the VPC resources,
11:49 or the private IPs.
11:51 And thing to remember,
11:52 is that you can announce maximum 100 prefixes from your end.
11:56 Do not advertise more than 100 prefixes.
12:00 Now, with that, in the next lecture,
12:02 we will get into the details of Direct Connect gateways
12:05 and the transit gateways,
12:07 but as of now, that's it about the private VIF.
12:10 So, thanks for watching.
整讲总结 / Overall Summary
中文
Private VIF 通过 AWS Direct Connect 和 VGW 或 DXGW，为本地网络提供到 VPC 私有 IP 资源的专用连接。BGP 会话交换 VPC 与本地前缀，客户最多发布 100 条路由，可借助路由汇总（route summarization）控制数量；传播路由按最长前缀匹配优先于 IGW 默认路由。Private VIF 可访问 EC2、数据库和接口端点，但不能直接访问 VPC DNS 解析器或网关端点。默认 MTU 为 1500，也可启用 9001 字节巨型帧（jumbo frame）。
English
A Private VIF provides dedicated Direct Connect access from on premises to private-IP resources in a VPC through a VGW or DXGW. BGP exchanges VPC and on-premises prefixes, with a 100-prefix customer limit that can be managed through route summarization. Propagated routes win over the IGW default route through longest-prefix matching. EC2 instances, databases, and interface endpoints are reachable, but the VPC DNS resolver and gateway endpoints are not directly reachable. The default MTU is 1,500 bytes, with optional 9,001-byte jumbo frames.
返回顶部 ↑