Lecture 54: VPC Peering
- 课程：[NEW] AWS Certified Advanced Networking Specialty 2026
- 视频时长：03:48
- 来源：Udemy Lecture 26073692
- Slide 数量：3
- 画面切换：00:22、01:11
扫描说明
逐条检查了 Udemy 页面中的 81 条 Transcript cue，并对全长 03:48 的视频画面进行扫描。画面由标题页切换到 VPC 对等拓扑和特性/限制页，共识别出 3 张不同的 Slide。
Transcript 来自 Udemy 页面自带的英文自动字幕，没有使用 ASR。下面保留页面原文，包括其中的语法或识别错误。
1. VPC Peering 导论
时间范围：00:00–00:22
总结 / Summary
中文
VPC 对等连接（VPC Peering）是连接两个 VPC 的直接私有互联方式，使两端资源可以通过私有 IP 在 AWS 网络上通信。它配置简单，但是否适合取决于 VPC 数量、地址规划和拓扑需求。
English
VPC Peering is a direct private connection between two VPCs that lets resources communicate over private IP addresses on the AWS network. It is simple to configure, but suitability depends on VPC count, address planning, and topology requirements.
Transcript
00:00 Hello, and welcome to this lecture.
00:02 In this lecture,
00:03 we are going to see the first option for
00:05 VPC private connectivity, that is VPC peering.
00:09 VPC peering is the simplest option, I would say,
00:12 where you just set the peering and then two VPCs can
00:15 communicate to each other over a private network.
00:18 And that's the simplest option you can look at to start with
2. 两个 VPC 通过 AWS Backbone 私有通信
时间范围：00:22–01:11
总结 / Summary
中文
对等连接把 VPC-A 与 VPC-B 直接相连，私有实例之间的流量经过 AWS 管理的骨干网络（AWS-managed backbone），不会穿越公共互联网。连接只建立网络邻接关系，实际通信仍需要双方路由表和安全控制允许。
English
A peering connection links VPC-A and VPC-B directly, carrying traffic between private instances across the AWS-managed backbone rather than the public internet. Peering creates the network adjacency, but communication still requires routes and security controls on both sides.
Transcript
00:22 but then you need to understand when it is appropriate to
00:25 use VPC peering and when you would use another option.
00:28 So let's take an example. Suppose there are two VPCs,
00:31 VPC A and B, and as I explained earlier,
00:35 suppose instance in
00:38 VPC A wants to talk to instance in VPC B
00:40 and both these instances are private instances.
00:43 Then the only option you have is to set up some kind of
00:46 private connectivity between these two VPCs.
00:49 That means the traffic should not flow over the internet.
00:53 So far that the option is of course, VPC peering connection.
00:56 What does it mean?
00:56 You connect these two VPCs over a private network,
00:59 which is completely managed by AWS.
01:01 And when the traffic flows through it,
01:03 it is over the AWS managed backbone network.
01:06 That means it is not flowing or through internet.
3. VPC Peering 的范围、要求与限制
时间范围：01:11–03:48
总结 / Summary
中文
VPC Peering 可在同一区域（Region）或跨区域建立，也可跨 AWS 账户。两个 VPC 的 CIDR 块不能重叠，否则无法做出明确路由选择；建立连接后必须在双方路由表（Route Table）中加入指向对端 CIDR、目标为 Peering Connection 的路由。它让两端像同一私有网络中的邻居，但连接本身是点对点关系。
English
VPC Peering can be established within one Region or across Regions and can span AWS accounts. The two VPC CIDR blocks must not overlap, because overlapping address space prevents unambiguous routing. After peering is established, each route table must contain a route to the peer CIDR through the peering connection. The relationship is direct and point to point.
Transcript
01:11 So what does VPC peering mean?
01:13 It connects two VPCs privately using AWS' network.
01:16 As I just said,
01:18 it makes them behave as if they were
01:21 part of the same network.
01:23 So that means any C2 machine from VPC A can talk to
01:27 any C2 machine in the VPC B and the vice versa.
01:30 Now peered VPC can be in same AWS region
01:32 or across AWS regions.
01:35 Now, when AWS introduced VPC peering for the first time
01:38 at that moment,
01:39 it was possible only within the same AWS region.
01:42 So VPCs need to be in the same region,
01:45 but later, now it has been extended in a way such that
01:49 even if you have VPC across different AWS region,
01:52 you can make this VPC peering.
01:54 So this is a great simplification for the network earlier,
01:57 if that was a requirement,
01:59 you had to set up a VPN connection between easy to machine
02:04 and other VPC network. But with the VPC peering,
02:07 even if your instances are across regions,
02:09 you can connect them.
02:11 Now, you can also do VPC peering with another AWS account.
02:14 And that's a common requirement.
02:16 Understand that mostly when you use VPC peering,
02:20 it's possible that the other VPC owner is not you,
02:23 maybe you are consuming some services from your
02:26 service provider, or you are providing services
02:29 to your customers.
02:31 In both these cases, the VPC owners are different, right?
02:35 But then VPC peering can be set up across AWS account.
02:38 And as we just understood, also across AWS regions.
02:43 So few things you need to understand
02:45 while you set up the VPC peering.
02:47 First thing is that the lead pieces that you connect should
02:50 not be having the overlapping CIDRs.
02:52 What that means?
02:54 The address range of VPC should not overlap.
02:57 And that's obvious because
02:59 then you can take a routing decision
03:02 if both the VPC have a similar address range.
03:05 So it should be non-overlapping.
03:06 That means if one VPC uses say 10.10.00/16,
03:11 that another VPC cannot have the same address range.
03:14 It needs to be different.
03:17 And while you set up the VPC peering connection,
03:20 you have to make sure that you update the route tables in
03:23 both the VPCs so that the traffic can go through the
03:27 VPC peering connection.
03:29 And this will be evident when we'll actually see at the demo
03:33 and you will also be able to do the exercise based on that.
03:37 Okay, with that we will now get into the demo
03:40 in the next lecture.
03:42 So as of now,
03:42 this is the basic understanding
03:44 with which we'll move forward. Thanks for watching.
整讲总结 / Overall Summary
中文
VPC 对等连接（VPC Peering）通过 AWS 骨干网络（AWS backbone）为两个 VPC 提供私有 IP 互通，支持跨区域和跨账户。成功通信的三个关键条件是非重叠 CIDR、已接受的 Peering Connection，以及双方路由表（Route Table）中正确的对端路由；安全组和 NACL 仍需允许相应流量。
English
VPC Peering provides private-IP connectivity between two VPCs over the AWS backbone and supports cross-Region and cross-account relationships. The three core requirements are non-overlapping CIDRs, an accepted peering connection, and correct peer routes in both route tables; Security Groups and NACLs must still permit the traffic.
返回顶部 ↑