Lecture 209: Routing Policy - Traffic Flow & Geoproximity Hands On
- 课程：[NEW] AWS Certified Advanced Networking Specialty 2026
- 视频时长：07:32
- 来源：Udemy Lecture 28556435
- Slide 数量：9
- 画面切换：00:47、02:15、03:08、04:25、04:54、05:33、06:20、06:54
扫描说明
逐条读取了 Udemy 页面中的 187 条英文 Transcript cue，并按时间轴扫描全长约 07:32 的视频。依据 Traffic Flow 概念、Visual Editor、US East 节点、Singapore 与 Bias Map、Frankfurt 节点、Policy Record 与成本、Version/Map、VPN 验证、Hosted Zone Record 与删除划分为 9 个小节。截图均在 Transcript 侧栏关闭、播放器控件隐藏后复核，统一为 1364×770。
Transcript 来自 Udemy 页面自带的英文自动字幕，没有使用 ASR。下面保留页面原文，包括其中的语法或识别错误。
1. Traffic Flow 用 Visual Editor 管理复杂 DNS Decision Tree
时间范围：00:00–00:47
总结 / Summary
中文
Route 53 Traffic Flow 用可视化节点图替代逐条手工维护复杂 Record，适用于 Geoproximity 以及 Weighted、Failover、Geolocation、Latency、Multi-value 等组合策略。配置保存为可 Version 的 Traffic Policy，可重复应用到不同 Hosted Zone，并在修改后发布新版本，降低大型 Decision Tree 的维护难度。
English
Route 53 Traffic Flow replaces manual record-by-record management with a visual node graph for complex configurations. It supports geoproximity and combinations of weighted, failover, geolocation, latency, multivalue, and other rules. The configuration is saved as a versioned traffic policy that can be reused across hosted zones and redeployed as new versions.
Transcript
00:00 So, let's have a look into a way
00:01 we can build these complex geoproximity records
00:06 using a feature called Traffic Flow.
00:08 This is not just applying to geoproximity,
00:10 but applies to everything.
00:11 So, the idea is that we have a UI, a visual editor,
00:15 that allows us to manage complex routing decision trees.
00:19 So, this is the UI we'll have,
00:20 and in there we can specify different rules.
00:22 We'll have a play with it.
00:23 Though the idea is that instead of writing the records
00:25 one by one in your DNS management system in Route 53
00:28 we're going to just manage all of them visually.
00:31 And the cool thing about it is that it's going to be saved
00:34 as a Traffic Flow Policy,
00:35 and it can be versioned,
00:37 it can be applied to different hosted zones,
00:38 and we can easily change them
00:41 and apply them in our hosted zones.
00:44 So, let's have a look in the hands-on right now
00:45 to see how we can do it.
2. 从 A Start Point 连接 Rule 或 Endpoint，形成可视化树
时间范围：00:47–02:15
总结 / Summary
中文
创建 DemoGeoPolicy v1，Start Point 先选择 DNS Type A，再通过加号连接 Rule 或 Endpoint。可选节点包括 Weighted、Failover、Geolocation、Latency、Multivalue、Geoproximity 和 Direct Endpoint。最简单的 A→Endpoint 可直接填 IPv4；复杂场景则能继续嵌套 Rule，例如 Weighted 分支下再接 Failover 与最终 Endpoint。
English
Create DemoGeoPolicy v1, choose DNS type A at the start point, and connect rules or endpoints with the plus node. Available nodes include Weighted, Failover, Geolocation, Latency, Multivalue, Geoproximity, and direct Endpoint. A simple A-to-endpoint graph holds one IPv4 value, while complex graphs can nest rules such as failover beneath weighted branches.
Transcript
00:47 Okay, so let's go ahead.
00:48 We're gonna go on the left-hand side panel,
00:50 and you will find Traffic policies.
00:52 So, in here we get the UI,
00:54 we can create a Traffic Policy.
00:56 And I'll call this one DemoGeoPolicy, and click on Next.
01:01 So, here we have a starting point,
01:03 and the starting point is you have to specify
01:04 the type of record you want to create.
01:06 Is it an A, AAAA, CNAME, etcetera, etcetera,
01:10 and it gives you a detail about what each record is.
01:12 So, we'll have an A record,
01:14 and here we have to connect to a specific rule.
01:17 And as you can see, we can get Weighted rule,
01:19 Failover rule, Geolocation rule, Latency rule,
01:21 Multivalue, Geoproximity, or just an endpoint.
01:24 So, if you wanted to specify something very simple,
01:26 for example an A into an endpoint,
01:28 you could say the A record will point to this value
01:32 one, two, three, four, five, six, seven, right?
01:34 And this would be the record itself,
01:37 a very, very simple record.
01:38 But obviously we can create more complicated policies.
01:41 So, we can connect to a Weighted rule,
01:43 and here we can specify multiple weights.
01:45 So, we say a weight of 10 goes to, and then again,
01:48 we could have some advanced records, for example,
01:51 a Failover and so on.
01:53 So, we can get some really complicated stuff.
01:55 And when you're ready you can say endpoint,
01:57 and specify the value of the IPv4 that you want.
02:01 So, obviously we're not going to build
02:03 something as complicated.
02:04 As you can see, on the Weighted rule for example
02:06 we can add another weight, and so on, and so on.
02:08 And so, all of it is visual,
02:10 and it really allows us to make sense
02:12 of what is happening within Route 53.
3. Geoproximity Region 1 选 us-east-1，Bias 0 并连接 EC2 IP
时间范围：02:15–03:08
总结 / Summary
中文
删除示意规则后改建 Geoproximity Rule。Region 1 的 Endpoint Location 选择 US East (N. Virginia)，系统自动使用该 Region Coordinates，Bias 保持 0；分支连接 Endpoint Value 54.172.8.44。Traffic Flow 也支持 Custom Coordinates，使 Non-AWS Location 可加入同一 Geography Model。
English
Replace the illustrative rule with a geoproximity rule. For region 1, select US East (N. Virginia), let Route 53 use the region's coordinates, keep bias at zero, and connect endpoint value 54.172.8.44. Traffic Flow also supports custom coordinates so non-AWS locations can participate in the same geographic model.
Transcript
02:15 So, we are not going to create a Weighted rule though,
02:16 we are going to create a Geoproximity rule.
02:19 And we can show the map as well to have a visual feedback
02:23 of what we're trying to do.
02:25 So, here we have to enter the first region,
02:28 and then we can have the second region.
02:31 So, now for the first endpoint location
02:33 you can enter custom coordinates, or you can, for example,
02:37 have one of these regions of AWS available to you.
02:40 So, we're going to use the ones we have created from before.
02:42 So, we'll choose US-East-1,
02:45 and then we have to specify a bias.
02:47 And then I will move the map a little bit to the left,
02:50 I will just remove it for now.
02:52 And then this record right here is going to connect
02:56 to a new endpoint,
02:57 and the value of it
02:58 is going to be my US-East-1 EC2 instance.
03:02 So, I will paste the value, and we're good to go.
03:05 For now we'll leave the bias as zero.
4. 加入 Singapore 后打开 Map，用 Bias 34 实时扩大 North America 区域
时间范围：03:08–04:25
总结 / Summary
中文
Region 2 选择 Singapore/ap-southeast-1 并连接 54.251.92.166。Show Map 用不同颜色展示全球 User 会落到哪个 Endpoint；两节点零 Bias 时有自然分界。把 US East Bias 调到 34 后，North America 颜色区域扩大；设为负值则相反。地图即时反馈 Bias 对 Catchment Surface 的影响。
English
Add region 2 as Singapore/ap-southeast-1 and connect 54.251.92.166. Show Map colors the world by which endpoint each user would reach, with a natural boundary at zero bias. Raising the US East bias to 34 expands the North American color region; a negative value does the opposite. The map provides immediate feedback on catchment changes.
Transcript
03:08 Then for the second region we can enter some coordinates.
03:11 So, we can say for example Singapore,
03:14 which was AP Southeast 1.
03:17 And let's do it, Singapore, again, here we go.
03:20 And then this is going to connect to a new endpoint,
03:23 and that endpoint has to be my IP address of AP-Southeast-1.
03:29 Press Enter, and we're good to go.
03:30 So, now that we have created this policy
03:33 let's have a look at the map.
03:35 So, for this I will click on Show Map.
03:37 And so, this geoproximity map is going to show me,
03:40 based on the input I have right now,
03:42 which users are going to go to which instance.
03:44 So, if you're on that side of the world,
03:46 the blue side of the world,
03:47 as you can see there's a line dividing
03:48 the blue and the orange side of the world,
03:50 then you're going to go to my first instance.
03:52 If you're on the second side of the world
03:54 you're gonna go to my second instance.
03:56 And if we change the bias,
03:57 so if we increase the bias for example
04:00 of my instance in here, so we put a bias of 34,
04:03 this is going to increase the surface of the world
04:06 that is going to be redirected
04:08 to my instance in North America.
04:10 If I decrease the bias to something negative
04:12 it's going to do the opposite thing.
04:13 It's going to center more of the traffic
04:16 onto my instance number two.
04:19 So, we can really play it and really have a visual aspect,
04:22 and the cool thing is that we can consider
04:24 more than two instances.
5. 第三个 Frankfurt 节点形成三 Region Map，并创建 Policy v1
时间范围：04:25–04:54
总结 / Summary
中文
继续添加 Frankfurt/eu-central-1 Location，连接 Endpoint IP 3.70.14.253。Map 现在显示 North America、Europe 与 Asia 三个覆盖区域，且每个 Region 都可独立调整 Bias。确认 Node 与 Endpoint 后点击 Create traffic policy，把整棵 Visual Decision Tree 保存为 DemoGeoPolicy Version 1。
English
Add Frankfurt/eu-central-1 and connect endpoint 3.70.14.253. The map now displays North America, Europe, and Asia catchments, each with independently adjustable bias. After confirming the nodes and endpoints, create the traffic policy to save the entire visual decision tree as DemoGeoPolicy version 1.
Transcript
04:25 Of course, we can add another geoproximity location,
04:29 and for the details we're going to say
04:31 this is in Frankfurt.
04:34 And then we're going to have, as you can see now, a new map.
04:36 And again, you can play with the bias,
04:38 and see how the bias is going to impact
04:41 your geoproximity map.
04:43 And so, this Frankfurt, we're going to have it
04:45 to a new endpoint.
04:46 And we'll have the EU-Central-1 in here, paste it,
04:51 and then Create traffic policy.
6. 部署 proximity Policy Record，注意每月 50 美元且按时长计费
时间范围：04:54–05:33
总结 / Summary
中文
Traffic Policy 本身创建后还需部署 Policy Record：选择 Hosted Zone stephanetheteacher.com，DNS Name 设为 proximity，TTL 60，Type A。页面明确显示 Pricing per month 为 $50，按实际保留时长 Prorated。为了避免不必要费用，学习者可只观察 UI；演示创建后会立即删除。
English
After creating the traffic policy, deploy a policy record by selecting the stephanetheteacher.com hosted zone, DNS name proximity, TTL 60, and type A. The page explicitly shows $50 per month, prorated for the time retained. Learners can stop at the UI to avoid unnecessary cost; the demonstration deletes the record immediately afterward.
Transcript
04:54 So, we've done this one,
04:55 and now we need to deploy this
04:57 traffic policy with policy records.
04:58 So, for this I will just deploy this one
05:00 into the hosted zone, stephanetheteacher.com,
05:03 and we can set that, this policy record name
05:06 is going to be proximity.stephanetheteacher.com.
05:10 And we can specify a TTL.
05:12 And very importantly,
05:14 the pricing per month is $50 per month,
05:16 so to just create this policy record
05:18 you will pay $50 per month.
05:19 It's prorated obviously for how long you keep it,
05:21 but if you want to remain within the free tier and,
05:24 you shouldn't create it obviously.
05:26 So, I'll just create it just to show you what it means,
05:28 and I will delete it right after.
05:30 But this is not necessary for you to go
05:31 all the way, obviously.
7. Traffic Policy 可发布新 Version，Map 预览三地路由结果
时间范围：05:33–06:20
总结 / Summary
中文
Policy 页面保留 Version 1；后续编辑会保存并部署为 New Version，而不是破坏式覆盖。重新打开 Geoproximity Map 可预览：Europe（如 France）命中 Frankfurt，Brazil 命中 North America，India 命中 Singapore。Policy Record 应用指定 Version，从而让变更具备清晰的版本边界。
English
The policy page retains version 1. Later edits can be saved and deployed as a new version instead of destructively overwriting the graph. The geoproximity map previews France reaching Frankfurt, Brazil reaching North America, and India reaching Singapore. A policy record applies a specific version, giving changes a clear version boundary.
Transcript
05:33 So, let's create this policy record.
05:35 As you can see now, the policy versions are here.
05:38 So, we can edit this policy if we wanted to,
05:41 and edit this and deploy it as a new version.
05:43 And from there we can see the records that have been created
05:46 with this DemoGeoPolicy.
05:49 And so, if we have a look again at the map
05:51 we can demonstrate how this works.
05:53 So, let's click on this Geoproximity rule in here,
05:57 so let's edit this as a new version, Next,
05:59 and then click on this map.
06:01 So, as we can see, if I'm in Europe, like I'm in France,
06:04 I will be able to connect to this instance,
06:06 if I'm in Brazil I will connect to that instance,
06:08 and if I am in, for example, India, again,
06:11 I will connect to that region.
06:12 So, we'll verify this in a second by testing the record.
06:16 So, let's cancel and wait for this to be created.
8. Europe、Brazil、Thailand VPN 测试分别命中三地 Endpoint
时间范围：06:20–06:54
总结 / Summary
中文
Policy Record 生效后，从当前 Europe 网络访问 proximity 域名返回 eu-central-1；VPN 切到 Brazil 后返回 American/us-east-1 Endpoint；再切到 Thailand 后返回 ap-southeast-1b。三个实际 Query 与 Map Preview 一致，验证 Traffic Policy 已把 Geoproximity Decision Tree 发布为可解析 DNS。
English
After the policy record becomes active, the proximity hostname returns eu-central-1 from the current European network, the American/us-east-1 endpoint through a Brazil VPN, and ap-southeast-1b through Thailand. The three live queries match the map preview and confirm that the geoproximity decision tree is published as working DNS.
Transcript
06:20 So, the policy record has been applied.
06:22 As you can see, the version used is number one.
06:24 So, if I connect from where I am, I'm in Europe right now,
06:26 I will get the EU-Central-1,
06:29 and so, which is perfect.
06:30 If I go to Brazil, for example, zed, and refresh my page,
06:37 and then it should be connecting to my American instance.
06:39 So, let's verify this in a second.
06:41 Yes, and finally, if I connect to something in Asia,
06:45 so let's change this.
06:46 Let's go to Thailand, for example,
06:49 and then refresh, I'm gonna get my AP-Southeast-1b instance.
06:53 So, this is perfect.
9. Hosted Zone 显示 Traffic policy record，只能回到 Traffic Flow 编辑
时间范围：06:54–07:32
总结 / Summary
中文
Hosted Zone 过滤 proximity 后，只看到一条 A Record，Value/Route traffic to 为 Traffic policy record；它不是普通 Route 53 Record，点击 Edit 会跳回 Traffic Policy UI。讲师随即删除 Policy Record，避免继续产生每月 $50 的费用。使用 Traffic Flow 时，清理部署 Record 与 Cost Control 同样重要。
English
Filtering the hosted zone for proximity shows one A record whose value or route target is Traffic policy record. It is not edited like an ordinary Route 53 record; Edit returns to the traffic-policy UI. The instructor then deletes the policy record to stop the $50 monthly charge. Cleanup and cost control are essential when using Traffic Flow.
Transcript
06:54 And if we go back into Route 53 now and refresh this
07:02 you can see if I go to Filter and type proximity
07:06 the record itself, this proximity record,
07:08 is directly routing to a traffic policy record, okay?
07:12 And the only way I can edit this record
07:14 is if I click on Edit right here,
07:16 and this will take me directly
07:18 into the traffic policy UI, okay?
07:21 So, that's it for this lecture.
07:23 I'm just going to save some money, obviously,
07:25 and delete this policy record right now
07:27 so it doesn't cost me $50 a month.
07:29 And I hope you liked this lecture.
07:30 I will see you in the next lecture.
整讲总结 / Overall Summary
中文
Traffic Flow 用 Versioned Visual Policy 把多层 Routing Rule 与 Endpoint 组织成可复用 Decision Tree。Hands-on 建立 US East、Singapore、Frankfurt 的 Geoproximity Policy，用 Map/Bias 预览边界，部署每月 $50 的 proximity Policy Record，并通过 Europe、Brazil、Thailand 验证三地解析；最终删除 Record 控制成本。
English
Traffic Flow organizes layered routing rules and endpoints into a reusable, versioned visual policy. The hands-on builds a geoproximity policy for US East, Singapore, and Frankfurt, previews boundaries with the map and bias, deploys a $50-per-month proximity policy record, validates it from Europe, Brazil, and Thailand, and deletes the record to control cost.
返回顶部 ↑