Lecture 211: Routing Policy - Multi Value
- 课程:[NEW] AWS Certified Advanced Networking Specialty 2026
- 视频时长:03:42
- 来源:Udemy Lecture 28556439
- Slide 数量:6
- 画面切换:00:31、01:22、01:46、02:26、02:59
扫描说明
逐条读取了 Udemy 页面中的 98 条英文 Transcript cue,并按时间轴扫描全长约 03:42 的视频。依据 Multi-value 核心机制、与 Simple/ELB 对比、US Record、Asia/EU Record、三条 Healthy Answer、制造 Unhealthy 后只返回两条划分为 6 个小节。截图均在 Transcript 侧栏关闭、播放器控件隐藏后复核,统一为 1364×770。
Transcript 来自 Udemy 页面自带的英文自动字幕,没有使用 ASR。下面保留页面原文,包括其中的语法或识别错误。
1. Multi-value 最多返回 8 条 Healthy Record,由 Client 侧选择
时间范围:00:00–00:31
总结 / Summary
中文
Multi-value Routing 用于同一 Name 指向多个 Resource,Route 53 每次 Query 最多返回 8 条 Healthy Record。每条 Record 可关联 Health Check,因此 Unhealthy Resource 会被过滤。Client 再从返回集合中选择 Endpoint,这是一种 Client-side Distribution;它看似 Load Balancing,但不能替代 ELB 的连接级能力。
English
Multivalue routing points one name to multiple resources and returns up to eight healthy records per query. Each record can use a health check, so unhealthy resources are filtered out. The client then selects an endpoint from the returned set. This is client-side distribution and, despite resembling load balancing, is not a substitute for an ELB.
Transcript
00:00 Let's talk about the last routing policy,
00:01 which is Multi-Value,
00:02 which is going to be used when you want to route traffic
00:04 to multiple resources.
00:06 And Route 53 will therefore
00:07 return multiple values or resources.
00:10 Now, you can associate them with Health Checks,
00:12 and so therefore the only resources returned
00:15 via the Multi-Value policy are going to be the ones
00:18 that are associated with a healthy Health Check.
00:20 So up to eight healthy records are going to be returned
00:22 for each Multi-Value query.
00:25 And although it looks like an ELB,
00:26 it's not a substitute for having an ELB.
00:28 The idea is that it's the client-side load balancing.
2. 与 Simple 多 Value 相比,Multi-value 具有逐 Record 健康过滤
时间范围:00:31–01:22
总结 / Summary
中文
Multi-value 为同一 Hostname 建立多条独立 A Record,每条有自己的 Value、Set/Record ID 与 Health Check。Query 只收到通过检查的最多 8 条 Record。Simple Routing 虽可在一条 Record 中包含多个 Value,却不能关联 Health Check,可能把 Unhealthy Endpoint 一并返回;这正是 Multi-value 更可靠之处。
English
Multivalue routing creates separate A records for one hostname, each with its own value, set or record ID, and health check. A query receives up to eight records that pass their checks. Simple routing can hold multiple values in one record but cannot attach health checks, so it may return unhealthy endpoints. This is the reliability advantage of multivalue.
Transcript
00:31 So let's look at an example.
00:33 We are going to set up multiple A Records
00:34 for our example.com,
00:36 and we associate them with Health Checks.
00:38 So when a Multi-Value query is done by our clients,
00:41 it's going to receive up to eight records back,
00:43 and then the clients will choose one of them.
00:45 But at least by combining this with Health Checks,
00:48 we know that one of the eight records being returned,
00:52 or up to eight, are going to be healthy.
00:54 And therefore the client
00:55 can have very safe queries into them.
00:59 This is going to be different, for example,
01:01 when you have a simple routing with multiple values in it,
01:05 because as you know, the simple routing policy
01:07 does not allow for Health Checks,
01:09 and therefore it's possible
01:10 that one of the resources returned in the query
01:12 of a simple routing policy will be unhealthy.
01:15 This is why Multi-Value are a little bit more powerful
01:18 as types of records.
01:20 So let's have a look in the UI at how we can test them.
3. 第一条 US Record:Multivalue + us-east-1 Health Check
时间范围:01:22–01:46
总结 / Summary
中文
创建 multi.stephanetheteacher.com 的第一条 A Record,Value 使用 us-east-1 IP 54.172.8.44,Routing Policy 选 Multivalue Answer,Health Check 选 us-east-1,Record ID 为 US,TTL 设为 60 秒。每个 Regional Endpoint 都以独立 Record 参与 Answer Set。
English
Create the first A record for multi.stephanetheteacher.com using us-east-1 address 54.172.8.44. Select Multivalue answer, associate the us-east-1 health check, use record ID US, and set TTL to 60 seconds. Each regional endpoint participates as an independent record in the answer set.
Transcript
01:22 So let's practice the Multi-Value record.
01:26 So let's go and create a multi-record,
01:29 so a multi dot blah blah blah.
01:31 And then the value of it
01:32 is going to be linked to us-east-1.
01:34 So I will add this value here,
01:36 and then the Routing policy is going to be Multivalue.
01:39 The Health check is going to be us-east-1.
01:41 And the Record is going to be US.
01:44 And TTL is going to be 60 seconds.
4. 再加入 Asia 与 EU,各自关联同 Region Check
时间范围:01:46–02:26
总结 / Summary
中文
第二条 Record 使用 ap-southeast-1 IP,Health Check 为 ap-southeast-1,Record ID 为 Asia;第三条使用 eu-central-1 IP 3.70.14.253,Health Check 为 eu-central-1,Record ID 为 EU,TTL 均为 60 秒。三条同名同 Type Record 的健康状态可以独立变化。
English
The second record uses the ap-southeast-1 address, its matching health check, and record ID Asia. The third uses eu-central-1 address 3.70.14.253, the eu-central-1 check, and record ID EU, all with 60-second TTLs. The three same-name, same-type records can change health independently.
Transcript
01:46 Let's add another Record.
01:47 So, multi, and again,
01:50 we're going to route to a different region,
01:51 so this one is ap-southeast-1.
01:53 So the answer is Multivalue answer.
01:56 The Health check is ap-southeast-1.
01:58 And the Record ID is going to be Asia.
02:02 And then the record TTL is one minute.
02:05 And then finally, the last one,
02:07 so again, one more Record name.
02:09 The Value is going to be linked to eu-central-1 right here.
02:14 The TTL is one minute.
02:16 And the Routing policy is Multivalue answer.
02:19 And for the Health checks,
02:20 we're going to use the one from eu-central-1.
02:25 And the Record ID is EU.
5. 三条 Check Healthy 时,dig 同时返回三种 Region IP
时间范围:02:26–02:59
总结 / Summary
中文
记录创建后执行 dig multi.stephanetheteacher.com,Answer Count 为 3,同时返回 us-east-1、ap-southeast-1、eu-central-1 三个 IP,TTL 60。原因是三条 Health Check 均为 Healthy;Route 53 不在此阶段替 Client 建立连接,而是把健康候选集合交给 Client。
English
After creating the records, dig multi.stephanetheteacher.com returns an answer count of three: the us-east-1, ap-southeast-1, and eu-central-1 addresses with TTL 60. All three health checks are healthy. Route 53 does not establish the application connection; it gives the client a healthy candidate set.
Transcript
02:26 Okay, so let's create these records.
02:29 And the records are successfully created.
02:31 Now let's test it out.
02:33 So for this, we're going to use our CloudShell in here.
02:35 So let's reconnect to CloudShell.
02:37 And what I want to do is to test this record.
02:40 So I will copy the record in here,
02:43 and then I will clear my screen.
02:46 And so if I test a dig on this,
02:49 then I get three answers.
02:50 So the three IPs are returned,
02:52 and the reason is, well,
02:53 the three health checks are fully working.
02:57 So as you can see, they're all healthy.
6. Invert EU Check 制造 Unhealthy 后,dig 只剩两条 Answer
时间范围:02:59–03:42
总结 / Summary
中文
为快速制造故障,编辑 eu-central-1 Health Check 并启用 Invert Health Check Status,使原 Healthy 状态变为 Unhealthy。重新 dig 后 Answer Count 降为 2,只剩 us-east-1 与 ap-southeast-1,EU IP 被 Route 53 排除。验证后取消 Invert,即可恢复正常健康判断。
English
To simulate failure quickly, enable Invert health check status on eu-central-1 so its healthy result becomes unhealthy. A new dig returns only two answers, us-east-1 and ap-southeast-1, with the EU address filtered out. Disabling inversion afterward restores normal health evaluation.
Transcript
02:59 But if I take one of them, for example,
03:00 I remove the eu-central-1,
03:02 so I'm gonna make this one unhealthy,
03:04 and I'm just going to trick it
03:05 by editing and do an Invert health status.
03:08 So this is going to make the healthy unhealthy,
03:10 and vice versa.
03:11 It's just a quick way for me
03:12 to create an unhealthy health check.
03:15 So let me pause right now.
03:16 Okay, so now my eu-central-1 health check is Unhealthy.
03:20 And so if I reissue a dig command right here,
03:24 I should expect to see only two values, yes, as a result.
03:27 So the Multivalue answer has worked,
03:29 and it worked really well.
03:30 So just to revert this, edit this health check,
03:32 and let's untick this Invert health check status,
03:36 and we're good to go.
03:37 Okay, so that's it for this lecture.
03:39 I hope you liked it.
03:40 And I will see you in the next lecture.
整讲总结 / Overall Summary
中文
Multi-value Routing 用多条独立同名 Record 返回最多 8 个 Healthy Endpoint,并由 Client 选择。与 Simple 多 Value 不同,它能为每条 Record 关联 Health Check。Hands-on 中三条健康记录全部返回;反转 EU Check 后 EU 自动从 Answer Set 消失,证明健康过滤有效。
English
Multivalue routing returns up to eight healthy endpoints through separate same-name records and lets the client choose. Unlike a simple record with multiple values, each multivalue record can have its own health check. All three demo records are returned while healthy; inverting the EU check removes it from the answer set and validates health filtering.
返回顶部 ↑