Lecture 73: VPC Peering vs VPC Endpoints
- 课程：[NEW] AWS Certified Advanced Networking Specialty 2026
- 视频时长：03:23
- 来源：Udemy Lecture 50324663
- Slide 数量：2
- 画面切换：00:32
扫描说明
逐条检查了 Udemy 页面中的 46 条 Transcript cue，并对全长约 03:23 的视频画面进行扫描。依据标题页与完整对比要点页的画面切换，共划分出 2 个小节。
Transcript 来自 Udemy 页面自带的英文自动字幕，没有使用 ASR。下面保留页面原文，包括其中的语法或识别错误。
1. PrivateLink、VPC Peering 与 Transit Gateway 的选择
时间范围：00:00–00:32
总结 / Summary
中文
本讲比较私有链路（PrivateLink）、VPC 对等连接（VPC Peering）和中转网关（Transit Gateway）的适用场景，重点不是技术定义，而是根据通信范围、扩展性和流量方向选择正确模型。
English
This lecture compares the appropriate use cases for PrivateLink, VPC Peering, and Transit Gateway. The focus is not on definitions but on choosing the correct model based on communication scope, scalability, and traffic direction.
Transcript
00:00 Okay, before we move to the summary, I thought let's talk about this topic quickly because many a
00:07 times a lot of learners ask this question, as in when to use VPC peering and when to use Privatelink,
00:14 or when to use a transit gateway.
00:16 So let's try to, you know, understand that and then we'll go to the summary.
00:22 Now technically speaking you know what is transit gateway.
00:25 What is VPC peering connection and what is privatelink.
00:28 But it is always important to understand when to use what right.
2. PrivateLink vs Peering 的核心差异
时间范围：00:32–03:23
总结 / Summary
中文
当两个 VPC 中大量资源需要双向三层通信（bidirectional Layer 3 communication）时，使用 VPC Peering；需要连接大量 VPC 时，Transit Gateway 提供集中式路由。若只需把单一应用或 SaaS 服务发布给许多使用者 VPC，应使用 PrivateLink：它支持重叠 CIDR（overlapping CIDRs），Endpoint Service 可扩展到数千个 VPC，并且只有服务使用者（service consumer）能发起连接，提供方（service provider）不能反向发起流量。
English
Use VPC Peering when many resources in two VPCs require bidirectional Layer 3 communication, and use Transit Gateway for centralized routing across many VPCs. Use PrivateLink when a single application or SaaS service must be published to many consumer VPCs: it supports overlapping CIDRs, an Endpoint Service scales to thousands of VPCs, and only the service consumer can initiate connections—the provider cannot initiate traffic back toward consumers.
Transcript
00:32 So you can consider VPC peering and transit gateway almost same right.
00:36 They provide, you know, VPC to VPC connectivity.
00:39 So here what we are talking about VPC peering uh also applies mostly to the transit gateway as well
00:45 right.
00:46 So VPC peering is useful when there are many resources that should communicate between the peered VPC.
00:51 So if you have say two VPCs and lot of hosts inside those VPCs needs to communicate with each other.
00:58 So that means you are opening a wide connectivity between VPCs at layer three.
01:02 Then you should use VPC peering connection, right?
01:06 But if there is a one specific service that needs to be accessed from a lot of other say.
01:11 Spoke VPCs or the client VPCs.
01:14 Then you should use Privatelink, right?
01:17 So you should use it when you want to allow access to only a single application hosted inside your VPC
01:22 to other VPCs without peering that VPCs.
01:26 So this works very well for the SaaS kind of applications, where SaaS provider is hosting their SaaS
01:32 service in their VPC.
01:34 And now all the consumers in different VPC can access the same SaaS service.
01:39 Now in that case, SaaS service provider does not need to pair their VPC to all the consumer VPCs.
01:45 They can expose their services through VPC private link.
01:50 Further, when there is overlapping Cidrs, you know that you cannot connect them to the transit gateways
01:56 or VPC peering.
01:58 But in that case, you can use VPC privatelink because overlapping SIDs do not matter to them.
02:04 Further, there are also some limitations when it comes to the VPC peering connection.
02:08 As in you can connect single VPC over, say 125 VPC peering connection only.
02:14 But in case of private link, a single VPC endpoint service can be accessed from thousands of VPCs.
02:22 So it is really ideal for that SaaS kind of environment, as I was saying.
02:27 And finally, VPC peering enables the bidirectional traffic, which means that if two VPCs are peered,
02:33 any host in any VPC can initiate the traffic to the other side of the network, right?
02:39 But in case of private link, there is always service provider and service consumer.
02:44 So only service consumer can initiate the traffic and then return.
02:48 Traffic comes, but it is still unidirectional with respect to who can originate that traffic, which
02:54 means service provider cannot initiate the traffic to the service consumer.
02:59 So in that sense it is one directional.
03:02 So please also remember this difference.
03:06 So these are some of the primary differences.
03:09 And I hope this can help you take decision over selecting the private link over VPC peering connection
03:15 or the transit gateways.
03:17 So with that we'll stop for this lecture.
03:19 And now let's go to the summary section.
03:21 Thank you.
整讲总结 / Overall Summary
中文
选择原则是“网络级互联”还是“服务级暴露”。Peering/TGW 为多个资源提供广泛、双向的 VPC-to-VPC 连通性；PrivateLink 仅暴露特定服务，支持重叠 CIDR、大规模消费者和单向发起模型，因此特别适合 SaaS 与跨账户服务共享。
English
The key decision is network-level connectivity versus service-level exposure. Peering and Transit Gateway provide broad, bidirectional VPC-to-VPC connectivity among many resources, while PrivateLink exposes only a specific service and supports overlapping CIDRs, large consumer scale, and consumer-initiated traffic—making it ideal for SaaS and cross-account service sharing.
返回顶部 ↑