Lecture 163: CloudFront Overview
- 课程：[NEW] AWS Certified Advanced Networking Specialty 2026
- 视频时长：05:08
- 来源：Udemy Lecture 28556129
- Slide 数量：22
- 画面切换：00:12、00:29、00:43、00:58、01:11、01:28、01:41、01:57、02:10、02:25、02:39、02:52、03:08、03:22、03:34、03:47、04:03、04:17、04:35、04:47、04:58
扫描说明
逐条读取了 Udemy 页面中的 130 条英文 Transcript cue，并按时间轴扫描全长约 05:09 的视频。按每 6 条 cue 截取 22 个候选画面；联系表显示这些画面分别对应项目逐步出现、用户/Edge/Regional Cache 请求路径变化或 CloudFront Components 新增内容，没有纯重复帧，因此全部保留。所有截图均关闭 Transcript 侧栏并隐藏播放器控件，依据 video 元素计算真实 16:9 媒体区域；最终 22 张图片无弹窗、无黑边、无右侧或下方裁切，统一为 1364×770。
Transcript 来自 Udemy 页面自带的英文自动字幕，没有使用 ASR。下面保留页面原文，包括其中的语法或识别错误。
1. AWS CloudFront 与 CDN
时间范围：00:00–00:12
总结 / Summary
中文
CloudFront 是内容分发网络（Content Delivery Network, CDN），目标是提升读取性能并把内容缓存到全球边缘。
English
CloudFront is a content delivery network designed to improve read performance by caching content at the edge.
Transcript
00:00 Okay. So, let's do a short overview
00:02 of CloudFront.
00:03 So, CloudFront is a Content Delivery Network or CDN.
00:07 And the idea is that by using CloudFront,
00:08 you're going to get a better read performance,
00:10 and the content is going to be cached
2. Points of Presence
时间范围：00:12–00:29
总结 / Summary
中文
CloudFront 在全球拥有 225+ 接入点（Point of Presence），其中约 215+ 是边缘站点（Edge Location），另有区域边缘缓存（Regional Edge Cache）。
English
CloudFront has more than 225 global points of presence, including over 215 edge locations and a smaller number of regional edge caches.
Transcript
00:12 at the edge of the world.
00:14 So, they are 225 plus Points of Presence globally in AWS
00:20 about 215 plus are Edge Locations
00:23 and 13 are Regional Edge Caches.
00:26 So, if we have a look at the map of the world,
00:27 this is something you can get from the internet.
3. Global User 到最近 Edge Location
时间范围：00:29–00:43
总结 / Summary
中文
即使源内容位于澳大利亚的 S3 Bucket，加拿大用户也会先连接附近的边缘站点（Edge Location），而不是直接跨洲访问源站（Origin）。
English
Even when the content resides in an S3 bucket in Australia, a user in Canada first connects to a nearby edge location instead of accessing the origin across continents.
Transcript
00:29 The idea of CloudFront is that, for example,
00:30 you have your content in an S3 Buckets in Australia
00:33 but your users are trying to access that content globally.
00:36 So, if you have a user, for example, in Canada,
00:38 trying to access it, maybe there will be
00:40 a Edge Location available next to that user
4. 首次 Fetch 与后续 Cache Hit
时间范围：00:43–00:58
总结 / Summary
中文
边缘站点（Edge Location）首次从 S3 源站（Origin）取回并缓存对象；同一区域的后续用户可直接命中缓存（Cache Hit），无需每次访问 S3。
English
The edge location fetches and caches the object from the S3 origin on the first request. Subsequent nearby users get a cache hit without another S3 request.
Transcript
00:43 and the Edge Location is going to cache that content,
00:45 but first fetch it to the S3 bucket.
00:48 That means that any other user in Canada
00:49 will also get that content locally from the Edge Location
00:53 and the Edge Location does not have to go
00:55 to the S3 bucket every time to get the data.
5. 全球分布与就近访问
时间范围：00:58–01:11
总结 / Summary
中文
全球用户会被引导到各自附近的边缘站点（Edge Location），从而让同一源内容在世界各地分布和缓存。
English
Users around the world are directed to nearby edge locations, distributing and caching the same origin content globally.
Transcript
00:58 So, you have a lot of Edge Locations around the world.
01:01 So, for example, a user in Russia,
01:02 could get to an Edge Location near China,
01:05 and then get access to the S3 bucket content as well.
01:08 So, you content is going to be distributed
01:09 and cached globally.
6. DDoS Protection 与 AWS Shield
时间范围：01:11–01:28
总结 / Summary
中文
全球缓存可以吸收重复请求、减轻源站压力，并为分布式拒绝服务攻击（DDoS Attack）增加保护层；CloudFront 还与 AWS Shield 集成。
English
Global caching absorbs repeated requests and reduces origin pressure, adding a layer of DDoS protection. CloudFront also integrates with AWS Shield.
Transcript
01:11 So, using a CDN is very helpful because it can give you
01:14 a layer of protection against a DDoS attack
01:17 because content is cached all around the world
01:19 and in case the requests are repeated,
01:22 then your origin is not under attack.
01:25 CloudFront has integration with shield for DDoS protection
7. AWS WAF、Route 53 与 HTTPS
时间范围：01:28–01:41
总结 / Summary
中文
CloudFront 可结合 AWS WAF 实施 Web 防火墙规则，结合 Route 53 管理 DNS，并向客户端提供加密的 HTTPS Endpoint。
English
CloudFront integrates with AWS WAF for web firewall rules, Route 53 for DNS, and HTTPS endpoints for encrypted client connections.
Transcript
01:28 that has integration with WAF for firewalls
01:30 and Route 53 for DNS names.
01:33 You can expose an external HTTPS endpoint using CloudFront.
01:36 So, you can encrypt connections
01:37 between the clients and your CDN
01:39 and then CloudFront can also
8. HTTPS Origin 与 WebSocket
时间范围：01:41–01:57
总结 / Summary
中文
CloudFront 与源站（Origin）之间也可使用 HTTPS，形成端到端加密；同时支持 WebSocket，使其兼容更多实时 Web Application。
English
CloudFront can use HTTPS to the origin for end-to-end encryption and supports WebSocket for real-time web applications.
Transcript
01:41 access your origins using HTTPS.
01:44 There's also support for the WebSocket protocol.
01:46 So, the idea is that CloudFront should be compatible
01:48 with many web applications.
01:50 Now, what are the inner workings of CloudFront?
01:54 Well, you have Edge Locations and Regional Edge Caches
9. 两级缓存层次
时间范围：01:57–02:10
总结 / Summary
中文
CloudFront 在源站（Origin）前提供两层：区域边缘缓存（Regional Edge Cache）和边缘站点（Edge Location）。源站可以是 S3 Bucket 或本地 HTTP Endpoint。
English
CloudFront places two layers in front of the origin: regional edge caches and edge locations. The origin can be an S3 bucket or an HTTP endpoint such as an on-premises server.
Transcript
01:57 and the idea is that your origin can have,
02:00 for example, an S3 Buckets, or an HTTP endpoint,
02:03 for example, on-premise servers, a server
02:05 and then you're gonna have two layers in CloudFront.
02:07 You're gonna have the Regional Edge Cache
02:08 and the Edge Locations.
10. 用户请求先到 Edge Location
时间范围：02:10–02:25
总结 / Summary
中文
用户请求 logo.jpg 时，DNS/CloudFront 把请求引导到附近的边缘站点（Edge Location）；若本地没有对象，就开始回源链路。
English
When a user requests logo.jpg, CloudFront directs the request to a nearby edge location. If the object is absent, the origin-fetch path begins.
Transcript
02:10 So, how does it work as a whole?
02:12 Well, you have your users all around the world
02:15 and say they want to fetch a logo from your website,
02:17 so they will go and hit the URL.
02:19 The users will get redirected to the Edge Location.
02:23 The Edge Location does not have that logo.
11. Edge Miss → Regional Miss → Origin
时间范围：02:25–02:39
总结 / Summary
中文
边缘缓存未命中（Edge Cache Miss）后查询区域边缘缓存（Regional Edge Cache）；若仍未命中，请求继续转发到源站（Origin）。
English
After an edge-cache miss, the request checks the regional edge cache. If that also misses, CloudFront forwards the request to the origin.
Transcript
02:25 So, the Edge Location will ask the Regional Edged Cache
02:28 if that logo exists in the cache
02:30 and the Regional Edge Cache does not have it,
02:31 therefore, it will go
02:33 and forward the request to the origin.
02:36 Now, the origin does have this logo, so the logo comes back.
12. 对象写入两级 Cache
时间范围：02:39–02:52
总结 / Summary
中文
源站响应先写入区域边缘缓存（Regional Edge Cache），再写入边缘站点（Edge Location），最后返回用户；两级缓存都可复用该对象。
English
The origin response is stored first in the regional edge cache and then in the edge location before reaching the user, making it reusable at both levels.
Transcript
02:39 It gets sent back to the Regional Edge Cache,
02:41 which puts the image into its cache.
02:44 Then the Regional Edge Cache sends it back
02:45 to the Edge Location, which will also cache it as well,
02:48 and then the user will get back the logo.
02:51 So, why this hierarchy?
13. 同一区域用户直接 Edge Hit
时间范围：02:52–03:08
总结 / Summary
中文
同一地理区域的后续用户从边缘站点直接获得缓存命中（Cache Hit），响应更快且不再访问上游。
English
A later user in the same geography receives an immediate edge-cache hit, avoiding all upstream requests.
Transcript
02:52 Well, because when a user from a similar geography
02:56 as the first users will request the same logo,
02:59 it will just query the Edge Location
03:01 and the Edge Location already has that logo cached,
03:03 so the logo comes back right away.
03:06 Now, if some users a bit more further away
14. 第二 Edge Location 复用 Regional Cache
时间范围：03:08–03:22
总结 / Summary
中文
更远用户可能连接第二个边缘站点（Edge Location）；该站点可从共享的区域边缘缓存（Regional Edge Cache）取得对象，而无需访问源站。
English
A farther user may use a second edge location, which can retrieve the object from the shared regional edge cache without contacting the origin.
Transcript
03:08 are requesting it from a second Edge Location.
03:11 Well, if that Edge Location is geographically close
03:14 to the Regional Edge Cache,
03:15 then the Edge Location will ask
03:17 the same Regional Edge Cache before for the file,
03:19 and the logo will be sent right away back
15. 一次 Origin Request 服务多用户
时间范围：03:22–03:34
总结 / Summary
中文
一个源站请求（Origin Request）即可填充 Regional Cache 和多个 Edge Cache，从而服务多个用户并显著降低源站负载。
English
A single origin request can populate the regional cache and multiple edge caches, serving many users while greatly reducing origin load.
Transcript
03:22 by the Regional Edge Cache and then back to the user.
03:25 So, the idea here is that you can see,
03:27 the origin only gets one request,
03:29 and we were able to serve multiple users
03:31 and multiple Edge Locations.
03:33 So, the Edge Locations allow you
16. Edge Location 缓存热门内容
时间范围：03:34–03:47
总结 / Summary
中文
边缘站点（Edge Location）离用户最近，负责快速响应并缓存最热门的内容；区域边缘缓存（Regional Edge Cache）则面向多个 Edge Location。
English
Edge locations sit closest to users, serve requests quickly, and cache the most popular content, while regional edge caches serve multiple edge locations.
Transcript
03:34 to serve content directly and quickly to the users,
03:37 because they're really close to them
03:38 and they will cache the most popular content
03:41 whereas the Regional Edge Caches
03:43 will serve content directly to the Edge Location.
03:46 There are bigger caches,
17. Regional Cache 更大且保留更久
时间范围：03:47–04:03
总结 / Summary
中文
区域边缘缓存（Regional Edge Cache）容量更大，可保存较冷门但可能突然升温的对象，并让对象驻留时间更长。
English
Regional edge caches are larger, retain less-popular objects that may suddenly become popular, and keep objects longer.
Transcript
03:47 so they will cache less popular contents
03:49 in case some maybe suddenly, it will become more popular.
03:53 And yes, because of the cache is larger,
03:55 then the objects remain longer into this cache.
03:58 It's used to improve performance
04:00 and again, gives you a second level of reduction
18. 减少 Origin Load 与 Dynamic Content
时间范围：04:03–04:17
总结 / Summary
中文
两级缓存进一步降低源站负载（Origin Load）；需要实时生成的动态内容（Dynamic Content）可能直接请求源站，不进入长期缓存。
English
The two-level hierarchy further reduces origin load. Dynamic content that must be generated per request may go directly to the origin instead of being cached.
Transcript
04:03 of load on your origin.
04:05 Now, in case you have dynamic content
04:07 that is premium requested by users,
04:09 it goes directly into your origins,
04:11 it does not pass through the Edge Cache.
04:14 Now, for the components of CloudFronts, we have three.
19. Component 1：Distribution
时间范围：04:17–04:35
总结 / Summary
中文
分配（Distribution）是 CloudFront 的顶层资源，由 cloudfront.net 域名标识，用户可直接使用该域名访问站点。
English
A distribution is CloudFront's top-level resource and is identified by a cloudfront.net domain name that users can access directly.
Transcript
04:17 We have the distribution, which is identified by domain name
04:20 and then, you can use this distribution name
04:24 to access the websites, okay?
04:25 You can also, if you wanted to apply a Route 53 CNAME
04:28 for the non-root URLs in your domain name
04:32 or an Alias for root and non-root URLs,
20. Route 53 CNAME 与 Alias
时间范围：04:35–04:47
总结 / Summary
中文
Route 53 可用 CNAME 指向非根域名，或用 Alias 同时支持根域名与非根域名，把自定义域名映射到 Distribution。
English
Route 53 can use a CNAME for non-root names or an Alias for both root and non-root names to map a custom domain to the distribution.
Transcript
04:35 which will point to the distribution's origin domain name.
04:39 So, there's a strong integration between Route 53
04:41 and a CloudFront here.
04:43 And in terms of origin,
04:44 we'll see this in the next lecture,
04:45 but this is where the content actually resides,
21. Component 2：Origin
时间范围：04:47–04:58
总结 / Summary
中文
源站（Origin）保存真实内容，可使用 S3 Bucket、应用负载均衡器（ALB）、HTTP Server、API Gateway 等资源。
English
The origin holds the actual content and can be an S3 bucket, ALB, HTTP server, API Gateway, or another supported endpoint.
Transcript
04:47 this could be an S3 Bucket,
04:48 and Application Load Balancer,
04:50 an HTTP Server, API Gateway, et cetera, et cetera.
04:52 And then you define a Cache Behavior,
04:55 which is, to define a cache configuration.
04:56 So, when do you want objects to expire?
22. Component 3：Cache Behavior
时间范围：04:58–05:08
总结 / Summary
中文
缓存行为（Cache Behavior）定义缓存配置，包括对象何时过期、存活时间（Time to Live, TTL）以及何时执行缓存失效（Cache Invalidation）。
English
A cache behavior defines caching rules such as object expiration, time to live, and cache invalidation.
Transcript
04:58 What's the time to live?
05:00 In which case, you won't have invalidations, and so on.
05:03 So, that's it for an overview of CloudFront.
05:05 In the next lecture, we'll have a detailed look at Origins.
整讲总结 / Overall Summary
中文
Amazon CloudFront 是内容分发网络（Content Delivery Network, CDN），通过全球接入点（Point of Presence）把内容缓存在靠近用户的位置，以降低延迟并减少源站（Origin）负载。请求先到边缘站点（Edge Location）；未命中时再查区域边缘缓存（Regional Edge Cache），最后才访问 S3 Bucket、HTTP Server、ALB 或 API Gateway 等源站。返回对象会在两级缓存中保存：Edge Location 适合热门内容，Regional Edge Cache 容量更大、对象驻留更久，能为多个 Edge Location 提供二级复用。CloudFront 与 AWS Shield、AWS WAF、Route 53 集成，支持端到端 HTTPS 与 WebSocket，也能缓解分布式拒绝服务攻击（DDoS Attack）。核心配置包括分配（Distribution）、源站（Origin）和缓存行为（Cache Behavior）；Distribution 具有域名，可由 Route 53 CNAME 或 Alias 指向，Cache Behavior 控制对象过期、存活时间（TTL）和失效（Invalidation）。
English
Amazon CloudFront is a content delivery network that caches content at points of presence close to users, reducing latency and origin load. A request first reaches an edge location; on a miss, it checks a regional edge cache and only then reaches an origin such as S3, an HTTP server, an ALB, or API Gateway. Returned objects are cached at both levels: edge locations keep popular content close to users, while larger regional edge caches retain less-popular objects longer and serve multiple edge locations. CloudFront integrates with AWS Shield, AWS WAF, and Route 53, supports end-to-end HTTPS and WebSocket, and helps absorb DDoS traffic. Its core components are the distribution, origin, and cache behavior. A distribution has a domain name that Route 53 CNAME or Alias records can target, while cache behaviors control expiration, TTL, and invalidation.
返回顶部 ↑