Lecture 57: Introduction to VPC Endpoint and PrivateLink
- 课程:[NEW] AWS Certified Advanced Networking Specialty 2026
- 视频时长:10:53
- 来源:Udemy Lecture 50324575
- Slide 数量:9
- 画面切换:00:46、02:28、03:25、04:12、05:42、07:18、08:48、10:14
扫描说明
逐条检查了 Udemy 页面中的 163 条 Transcript cue,并对全长 10:53 的视频画面进行扫描。接触表复核后将 Without Endpoints 与 With Endpoints 确认为两张独立架构 Slide,并修正了多个切换边缘,共识别出 9 张 Slide。
Transcript 来自 Udemy 页面自带的英文自动字幕,没有使用 ASR。下面保留页面原文,包括其中的语法或识别错误。
1. VPC Endpoint 与 PrivateLink 导论
时间范围:00:00–00:46
总结 / Summary
中文
VPC 端点(VPC Endpoint)与 AWS PrivateLink 为 VPC 到 AWS 服务或其他 VPC 中托管服务提供私有连接。它们可简化网络、降低成本并减少公网暴露,是 AWS 私有连接架构的核心组件。
English
VPC Endpoints and AWS PrivateLink provide private connectivity from a VPC to AWS services or services hosted in other VPCs. They simplify networking, reduce cost, and limit public exposure, making them central to AWS private-connectivity design.
Transcript
00:00 Hello and welcome to this new section, VPC endpoint and Private link.
00:05 Now in my opinion, this is again one of the most important section because here we are going to talk
00:11 all about the private connectivity from your VPC to other AWS services or the services which are hosted
00:19 in VPC.
00:20 And you will realize that over the time, your network architecture would have more and more of this
00:26 VPC endpoints because it really simplifies your AWS network architecture.
00:32 Also, it reduces cost and also it improves the security of your architecture.
00:38 And that's where it is one of the important topic.
00:42 Okay.
00:42 So the first thing what is VPC endpoint and what is private link.
2. 传统访问 AWS Services:Public IP 或 NAT Gateway
时间范围:00:46–02:28
总结 / Summary
中文
公有 EC2 可通过 IGW 访问 S3、Kinesis 等 AWS 服务;私有子网实例通常经 NAT 网关(NAT Gateway)和 IGW 访问这些公共服务端点。虽然资源都在 AWS 区域内,流量仍采用公网路径模型,并产生 NAT 费用、带宽瓶颈和额外安全控制需求。
English
A public EC2 instance can reach services such as S3 and Kinesis through an IGW, while a private-subnet instance typically uses a NAT Gateway and IGW to reach their public endpoints. Even when all resources are in one AWS Region, this model uses public addressing and introduces NAT cost, bandwidth constraints, and additional security controls.
Transcript
00:46 Right.
00:47 So this is kind of familiar architecture to you.
00:49 Where you have AWS region you have VPCs.
00:52 And in that VPC you might have EC2 instance which hosts some application.
00:57 And then you have AWS services like S3 or Kinesis SDKs.
01:02 These are managed AWS services.
01:04 Now if your application, which is hosted on EC2, needs to connect to this AWS services, typically
01:11 the EC2 instance will make that call over the internet.
01:15 So all that traffic goes over the internet.
01:18 Even though both your EC2 instance and AWS services are part of the same AWS region, right?
01:25 So this works, right?
01:27 But because everything is in AWS, probably we can do a little better here.
01:32 Now this is one use case where EC2 instance is public and then it can directly access the internet.
01:37 But in most of the cases your application servers are in a private subnet, right.
01:42 And in that case if you want to access AWS services, for example, if you want to upload some data
01:47 to S3 or download data from S3, you will need Nat gateway in a public subnet.
01:52 And then instance can connect to those AWS services.
01:56 Right?
01:57 So this works.
01:58 But again, if you see this architecture, all the traffic is within AWS region, but still you are
02:05 paying for the Nat gateway charges and you might have to apply some security policies because traffic
02:10 is going out from the internet.
02:13 And sometimes you might also face the Nat gateway bandwidth challenges if you are downloading or uploading
02:18 huge amount of data, and there are multiple EC2 instances in your VPC.
02:23 Now to exactly address this problem, AWS had launched VPC endpoints.
3. Endpoint 与 PrivateLink 如何建立私有服务连接
时间范围:02:28–03:25
总结 / Summary
中文
VPC Endpoint 是消费者 VPC 中的访问入口,AWS PrivateLink 是支撑接口类端点的底层私有连接能力。它们可连接 AWS 托管服务,也可连接服务提供方 VPC 中的客户服务,且不需要消费者 VPC 配置 IGW 或 NAT Gateway,流量始终留在 AWS 网络内。
English
A VPC Endpoint is the access point in a consumer VPC, while AWS PrivateLink supplies the underlying private connectivity for interface-style endpoints. Together they connect to AWS-managed services or customer services in a provider VPC without requiring an IGW or NAT Gateway in the consumer VPC, keeping traffic on the AWS network.
Transcript
02:28 So VPC endpoints and AWS Privatelink.
02:32 And there is a distinction between these two terms.
02:34 So we'll understand about that.
02:36 But basically both endpoints and privatelink work together to establish a private connection between
02:42 your VPC and AWS services.
02:46 Or you could also host your own services inside a VPC.
02:51 And you can access those services from this consumer VPC privately.
02:55 You don't need, say, Internet Gateway or Nat gateway to access these services.
03:00 So that's essentially is VPC endpoints powered by Privatelink.
03:06 And if you set up this kind of connectivity then all the traffic between your consumer VPC to the provider
03:12 VPC or provider services will be inside AWS.
03:16 It doesn't go over the internet.
03:18 So it's a private connection now right?
03:20 So that's the benefit.
03:22 So let's answer the question why VPC endpoint.
4. 为什么使用 VPC Endpoint
时间范围:03:25–04:12
总结 / Summary
中文
VPC Endpoint 在 AWS 网络内建立私有连接,减少互联网暴露和安全风险,并去除 IGW、NAT 设备等额外网络组件。它既支持大量 AWS 服务,也支持 AWS 客户或合作伙伴托管在 VPC 内的服务。
English
VPC Endpoints establish private connections inside the AWS network, reducing internet exposure and security risk while removing extra components such as IGWs and NAT devices. They support many AWS services as well as customer- or partner-owned services hosted in VPCs.
Transcript
03:25 So the VPC endpoint enables the private connections that we already talked about.
03:30 It reduces your security risk because all the traffic remains now within the AWS region.
03:36 And you don't need additional devices like internet gateway or Nat devices.
03:41 So of course it's a less work for you and you're not exposing your network to the outside world.
03:48 Third, it supports a lot of different AWS services as well as customer owned services, which are hosted
03:54 inside VPC.
03:56 And I will talk shortly.
03:57 What do I mean by that?
03:58 Right.
03:59 So these are the reasons for which you should use VPC endpoints.
04:05 Okay.
04:05 With that now let's look at the different types of endpoints.
04:08 And then we will start with one of the type of endpoint.
5. VPC Endpoint 的主要类型
时间范围:04:12–05:42
总结 / Summary
中文
网关端点(Gateway Endpoint)是独立实现,主要面向 S3 和 DynamoDB。由 PrivateLink 支撑的类型包括接口端点(Interface Endpoint)、网关负载均衡器端点(Gateway Load Balancer Endpoint)、VPC 资源端点(VPC Resource Endpoint)和 VPC Lattice 服务网络端点(Service Network Endpoint)。本节重点是 Gateway 与 Interface Endpoint。
English
Gateway Endpoints use a distinct implementation and primarily serve S3 and DynamoDB. PrivateLink-powered types include Interface Endpoints, Gateway Load Balancer Endpoints, VPC Resource Endpoints, and VPC Lattice Service Network Endpoints. The section focuses mainly on Gateway and Interface Endpoints.
Transcript
04:12 So there are different types of endpoint.
04:14 And the very first is VPC gateway endpoint.
04:17 Now this is a different kind of endpoint from rest of the endpoints that we are going to talk about.
04:23 And that's where we will cover VPC gateway endpoint in its own subsection.
04:27 And rest of the endpoints we will cover separately.
04:32 And this is for the reason that rest of the endpoints are powered by something called Privatelink,
04:39 which basically establishes the private connectivity between VPC and the target network.
04:45 And these endpoints, which are powered by VPC Privatelink, work little differently than how VPC gateway
04:52 endpoint works.
04:53 And in the subsequent lecture, let's understand about those Differences.
04:57 So as of now, if we talk about the VPC private link, then there are different types of the endpoint.
05:03 The fundamental endpoint is VPC interface endpoint.
05:06 And we will spend more time understanding about that.
05:10 But lately AWS has also launched additional type of endpoints.
05:14 So there is a gateway load balancer endpoint.
05:16 There is VPC resource endpoint and VPC lattice service network endpoint.
05:22 And further we are going to also talk about these endpoints in the respective section in this course.
05:27 So in this section we will primarily focus on VPC gateway endpoint and VPC interface endpoint.
05:35 Right.
05:36 So with that now let's understand how these endpoints simplifies your network and what benefits they
05:41 provide.
6. Without Endpoints:私有实例依赖 NAT/IGW
时间范围:05:42–07:18
总结 / Summary
中文
没有 VPC Endpoint 时,私有 EC2 访问 AWS 公共 API、S3/DynamoDB 或服务提供方通常需要 NAT Gateway 与 IGW。对于 S3/DynamoDB,若只需 VPC 内访问,Gateway Endpoint 最简单;如果还需从本地网络或 Peered VPC 访问,则可考虑 Interface Endpoint。
English
Without VPC Endpoints, a private EC2 instance generally needs a NAT Gateway and IGW to reach public AWS APIs, S3 or DynamoDB, or provider services. For S3 and DynamoDB, a Gateway Endpoint is simplest for access originating inside the VPC, while an Interface Endpoint may be used when remote networks or peered VPCs also need private access.
Transcript
05:42 So again VPC with a private subnet and instance with private IP.
05:47 And assume that this instance needs to access AWS services endpoint something like this.
05:53 Or it needs to access other VPC services which are hosted behind a network load balancer, and or it
06:00 needs to access some AWS services APIs, for example API gateways or SQS queue, all those things,
06:06 right?
06:07 Now, one thing that may confuse you here is you can see the S3 and DynamoDB both are here, as well
06:15 as in the bottom side of this architecture right now.
06:19 That's for the reason that for S3 and DynamoDB specifically, you can access that from VPC using either
06:26 VPC gateway endpoint or using VPC interface endpoint.
06:31 And the use case is if you need to access these services from within the VPC, then use a gateway endpoint.
06:37 But otherwise, if you want to enable the access to S3 from the VPC.
06:41 But then this VPC can then further be accessed from some other remote networks, for example on premises
06:47 network or peered VPC.
06:49 Then you will use interface endpoint.
06:52 And in this section we are going to talk in much deeper about all these scenarios, so just hold on
06:57 till we reach there.
06:59 Okay, so let's get back to this topic again.
07:02 So traditionally without VPC endpoints, as I said we need to have Nat gateway and internet gateway.
07:09 And this traffic goes over the internet to these services.
07:13 And that's where all those challenges about the cost and bandwidth comes into play.
07:17 Right.
7. With Endpoints:Gateway Route 与 Interface ENI
时间范围:07:18–08:48
总结 / Summary
中文
Gateway Endpoint 通过更新子网路由表把 S3/DynamoDB 流量私有地导向服务;Interface Endpoint 则在选定子网中创建带私有 IP 的弹性网络接口(Elastic Network Interface, ENI),实例通过该 ENI 访问 AWS 或客户服务。这样可移除不必要的 NAT Gateway 与 IGW。视频指出 Gateway Endpoint 免费,Interface Endpoint 有较小费用且通常低于 NAT 成本。
English
A Gateway Endpoint updates subnet route tables so S3 and DynamoDB traffic reaches the services privately. An Interface Endpoint creates an Elastic Network Interface with a private IP in selected subnets, and instances use that ENI to access AWS or customer services. This can remove unnecessary NAT Gateways and IGWs. The video notes that Gateway Endpoints are free while Interface Endpoints carry a smaller charge that is generally below NAT cost.
Transcript
07:18 But with VPC endpoints, as I said there are different types of the endpoint.
07:23 So the first VPC endpoint type is a gateway endpoint for which you have to update your route table of
07:30 the subnet, and then all the traffic to the S3 or DynamoDB only for these two services, traffic goes
07:36 privately from this instance to this AWS services.
07:40 Right.
07:41 So that's a gateway endpoint.
07:43 Further, as I said there is interface endpoint.
07:46 Now interface endpoint works a little differently where it provisions and Elastic Network interface
07:52 into your subnet.
07:54 Right.
07:55 And that's where it has an IP address.
07:57 And now all the traffic from your this private EC2 instance can be routed through this Eni to this AWS
08:04 services or the customer services which are hosted inside the VPC.
08:10 So traffic goes privately now to this target networks.
08:14 So that's interface endpoint.
08:17 And as you can now see once we have these endpoints we don't really need these Nat gateways and internet
08:24 gateway into your VPC right.
08:27 So I hope it is clear.
08:28 And for the benefits as in gateway endpoint is completely free.
08:32 And interface endpoint has small charge.
08:35 But it is much lower than using Nat gateways.
08:37 Right.
08:38 So it is always beneficial.
08:41 Okay.
08:42 So let's quickly summarize what we understood in this lecture about VPC endpoints and privatelink.
8. VPC Endpoint 与 PrivateLink 要点总结
时间范围:08:48–10:14
总结 / Summary
中文
Endpoint 使用私有网络连接 VPC 资源与 AWS/客户服务,托管组件由 AWS 横向扩展、冗余并高可用。Gateway Endpoint 仅服务特定服务(核心为 S3、DynamoDB);Interface Endpoint 覆盖更广的 AWS 服务和自建服务。还有 GWLB、Resource 与 Service Network 等其他端点类型。
English
Endpoints connect VPC resources to AWS or customer services over private networking, with AWS managing horizontal scaling, redundancy, and high availability. Gateway Endpoints serve a narrow service set centered on S3 and DynamoDB, while Interface Endpoints cover a much broader set of AWS and customer services. GWLB, Resource, and Service Network endpoints extend the model further.
Transcript
08:48 So VPC endpoints allows you to connect to resources in VPCs or AWS services using private network instead
08:55 of public network.
08:57 They remove the need of internet gateways, Nat gateways to access AWS services, and all these devices
09:03 which powers these endpoints are managed by AWS and they are horizontally scaled, redundant and highly
09:10 available.
09:10 So you don't need to worry about, say for example, Nat gateways high availability.
09:14 You have to have multiple Nat gateways in different AZS, but you don't need to worry about that for
09:19 the endpoints.
09:20 Now again, with respect to the types, there is a gateway endpoint which only enables the access to
09:26 Amazon S3 and DynamoDB.
09:28 But otherwise if you need access to other AWS services and customer managed or owned services which
09:35 are deployed inside the VPC, then you will use interface endpoint.
09:40 And further, as I said, AWS launched many other different types of endpoints.
09:45 So there is something called gateway load balancer endpoint VPC resource endpoint VPC lattice service
09:50 network endpoint.
09:52 And maybe in the future there will be additional endpoints as well.
09:55 But our focus will be primarily on the gateway endpoint and the interface endpoint.
10:01 Right.
10:02 So I hope it is clear at the high level what is VPC endpoint and the private link and how they work
10:07 together.
10:08 And with that now let's get started with the VPC gateway endpoint.
9. 从总体架构进入 Gateway Endpoint
时间范围:10:14–10:53
总结 / Summary
中文
本节接下来先学习网关端点(Gateway Endpoint),因为它只面向 S3 和 DynamoDB、概念较集中且没有端点使用费;之后再重点深入接口端点(Interface Endpoint)及 PrivateLink 服务发布模式。
English
The section proceeds first to Gateway Endpoints because they focus on S3 and DynamoDB, are conceptually narrower, and have no endpoint usage charge. It then moves to the deeper Interface Endpoint and PrivateLink service-publication model.
Transcript
10:14 And this is a small topic as compared to the interface endpoint for the reason that it only allows you
10:19 to connect to the Amazon S3 and DynamoDB to only these two services.
10:24 Right?
10:25 And the benefit is it's free.
10:27 There is no charge for using gateway endpoint, and that's what you should always use it in my opinion.
10:32 And we will talk more about that in the following lectures.
10:35 But this is where we will start.
10:37 And then we will spend most of the time in this section for the interface endpoints.
10:43 Okay.
10:43 With that, let's stop for this lecture.
10:45 And now let's see more about VPC gateway endpoint.
10:49 So thanks for watching and stay tuned.
整讲总结 / Overall Summary
中文
VPC Endpoint 消除私有子网访问 AWS 或客户服务时对公网、IGW 和 NAT Gateway 的不必要依赖。Gateway Endpoint 通过路由表服务 S3/DynamoDB;Interface Endpoint 在子网中创建私有 ENI,并由 AWS PrivateLink 把流量送到目标服务。二者共同提升安全性、简化高可用设计并常常降低成本。
English
VPC Endpoints eliminate unnecessary dependence on public networking, IGWs, and NAT Gateways when private subnets access AWS or customer services. Gateway Endpoints use route tables for S3 and DynamoDB, while Interface Endpoints create private ENIs and use AWS PrivateLink to reach target services. Together they improve security, simplify high availability, and often reduce cost.
返回顶部 ↑