Lecture 198: Route 53 - EC2 Setup
- 课程：[NEW] AWS Certified Advanced Networking Specialty 2026
- 视频时长：05:40
- 来源：Udemy Lecture 28556385
- Slide 数量：7
- 画面切换：01:10、01:46、02:16、02:39、03:58、05:08
扫描说明
逐条读取了 Udemy 页面中的 120 条英文 Transcript cue，并按时间轴扫描全长约 05:40 的 Hands-on。依据 Frankfurt EC2/User Data、N. Virginia EC2、Singapore EC2、多 Region 汇总、Frankfurt ALB/Target Group、三个 Public IP 验证、ALB DNS 验证划分为 7 个小节。截图均在 Transcript 侧栏关闭、播放器控件隐藏后复核，统一为 1364×770。
Transcript 来自 Udemy 页面自带的英文自动字幕，没有使用 ASR。下面保留页面原文，包括其中的语法或识别错误。
1. 在 Frankfurt 启动带 AZ 标识的 Web Server
时间范围：00:00–01:10
总结 / Summary
中文
先在 Frankfurt（eu-central-1）启动 Amazon Linux 2 t2.micro，不使用 Key Pair，Security Group 允许 SSH 与 HTTP from Anywhere。User Data 安装并启动 httpd，通过 Instance Metadata 读取 placement/availability-zone，再把 Hostname 与 AZ 写入 index.html，便于后续从 DNS 响应判断访问落在哪个 Region/AZ。
English
First launch an Amazon Linux 2 t2.micro in Frankfurt (eu-central-1) without a key pair and allow SSH and HTTP from anywhere. User data installs and starts httpd, reads placement/availability-zone from instance metadata, and writes the hostname and AZ to index.html so later DNS responses reveal the serving region and AZ.
Transcript
00:00 So let's get started.
00:01 And before we use Route 53,
00:03 I want to go ahead and create three EC2 instances
00:05 in different regions, as well as one ALB.
00:08 So in one of these regions I'm going to go
00:10 into instances and then launch an instance.
00:13 And very simply, I will choose Amazon Linux2
00:16 on this architecture, a T2 micro type of instance.
00:20 I don't need a key pair, because I will use,
00:22 if I need to, I will use EC2 instance connect.
00:25 And then for network settings,
00:26 I'm going to create a security group.
00:28 I will allow SSH as well as HTTP from anywhere.
00:32 Then I will just, in advanced details,
00:36 specify a bootstrap user data script.
00:39 So, to do so, just go into your Route 53
00:43 user script and you copy this entire script.
00:47 And you paste it here.
00:48 So what's going to do is it's going to say
00:50 hello world from the instance, just as before.
00:52 But now we're going to add the AZ
00:54 the instance was launched in,
00:55 using this environment verbal called EC2,
00:58 availability, zone that I created from before.
01:01 So it's going to give us a little bit
01:03 more info about EC2 instance.
01:05 So I'm going to go ahead and launch this instance.
2. 在 Northern Virginia 复制相同 EC2 配置
时间范围：01:10–01:46
总结 / Summary
中文
切换到 Northern Virginia（us-east-1），使用同样的 AMI、Instance Type、无 Key Pair、HTTP Security Rule 与 User Data 启动第二台 Instance。保持 Bootstrap 一致，使各 Region 返回页面格式相同，差异只体现在 Hostname 与 Availability Zone。
English
Switch to Northern Virginia (us-east-1) and launch a second instance with the same AMI, instance type, no key pair, HTTP security rule, and user data. Keeping the bootstrap identical gives every region the same page format, with only hostname and availability zone differing.
Transcript
01:10 So this has been launched and it is right here.
01:13 Okay, that's good.
01:14 Next I'm going to go into another region.
01:16 For example, Northern Virginia, so US East one.
01:21 And then I will launch an instance.
01:24 And same settings.
01:26 So again, no key pair required.
01:28 So proceed without a key pair.
01:30 I will allow HTTP as well.
01:33 And for advanced details, I will provide
01:35 the exact same EC2 user data script.
01:39 Then we click on launch instance and we're good to go.
3. 在 Singapore 启动第三台 EC2
时间范围：01:46–02:16
总结 / Summary
中文
再切换到 Singapore（ap-southeast-1），重复 t2.micro、No Key Pair、HTTP from Anywhere 与相同 User Data，启动第三台 Web Server。三个 Region 的独立 Public IP 将作为后续 Simple、Weighted、Latency、Geolocation 等 Route 53 Routing Policy 的 Target。
English
Switch to Singapore (ap-southeast-1) and repeat the t2.micro, no-key-pair, HTTP-from-anywhere, and identical user-data setup for a third web server. The three regional public IPs become targets for later Route 53 simple, weighted, latency, geolocation, and other routing policies.
Transcript
01:46 And finally I'm going to go into
01:47 one last region, for example Singapore.
01:51 And in Singapore I'm going to launch an instance.
02:00 And then we'll leave it as t2 micro,
02:02 we will choose no key pair.
02:04 We'll allow HTTP from anywhere.
02:07 And then, under advanced details,
02:11 I'm going to paste in the data and launch this instance.
4. 确认三个 Region 的 Instance 均已启动
时间范围：02:16–02:39
总结 / Summary
中文
此时部署包含 Frankfurt、Northern Virginia 与 Singapore 各一台 EC2。应等待 Instance State 为 Running、Status Check 通过，并确保各 Region Security Group 允许 TCP/80；跨 Region 资源独立，不能假设一个 Region 的 Security Group 会自动应用到另一个 Region。
English
The deployment now contains one EC2 instance each in Frankfurt, Northern Virginia, and Singapore. Wait for Running state and passing status checks, and ensure each regional security group allows TCP/80. Resources are regional, so a security group in one region does not automatically apply in another.
Transcript
02:16 Okay, so we have three instances
02:18 now being started in three different regions.
02:20 So we have one in Frankfurt,
02:22 one in Northern Virginia, and one in Singapore.
02:25 So this is good.
02:26 Lastly, what I'm going to do is that
02:27 I'm going to launch a load balancer
02:30 in Frankfurt, for example.
02:32 So here I'm going to create a load balancer
02:35 and choose an application load balancer.
02:38 Create.
5. 在 Frankfurt 创建 Internet-facing ALB 与 Target Group
时间范围：02:39–03:58
总结 / Summary
中文
在 Frankfurt 创建 DemoRoute53ALB，Scheme 为 Internet-facing、IPv4，并映射三个 Subnet。选择允许 HTTP 的 Security Group，Listener 使用 HTTP/80；新建 Instance 类型 Target Group demo-tg-route53，Health Check 使用 HTTP 根路径 /，注册 Frankfurt 的 EC2，再把该 Target Group 绑定到 ALB。
English
In Frankfurt, create DemoRoute53ALB as an internet-facing IPv4 ALB across three subnets. Select a security group allowing HTTP, use an HTTP/80 listener, create an instance-type target group named demo-tg-route53 with an HTTP health check on /, register the Frankfurt EC2 instance, and attach the target group to the ALB.
Transcript
02:39 And then the unique name will be DemoRoute53ALB.
02:44 This is fine, it's going to be internet facing, on IPv4.
02:49 I will choose for mapping, one, two, and three subnets.
02:55 And for security group I can choose up to five.
02:58 So I'm going to choose the one that I've created
03:01 just from before, which was the launch user two,
03:03 which had AWS and HTTP enabled.
03:06 This way we're sure that HTTP is enabled.
03:09 And the protocol is on 80, you're going
03:11 to forward to a new target group,
03:14 that we're going to have to create, based on instances.
03:17 And I'll call it this one demo tg route 53.
03:22 And, what I want to do is next
03:27 and register my one instance right now
03:30 that I just created from before.
03:32 So you do include as pending below.
03:35 Then on the review targets, you have one target.
03:37 And then create the target group.
03:41 So the target group is not created.
03:42 So back into model balancers.
03:44 I can refresh this and select the demo tg group route 53.
03:51 And everything looks good.
03:53 Let's create our load balancer,
03:56 and then click on view the balancer.
03:57 And here we go.
6. 逐一记录并验证三个 Region 的 Public IP
时间范围：03:58–05:08
总结 / Summary
中文
依次用 http://Public-IP 打开三台 Instance，页面应分别显示 eu-central-1b、us-east-1a 与 ap-southeast-1b 等 AZ 信息。把 Public IPv4 与 Region 记录在文本中，作为后续 DNS Record Value。若页面失败，先排查 Instance User Data、httpd、Security Group 与 Public Routing。
English
Open each instance through http://Public-IP. The pages should show AZs such as eu-central-1b, us-east-1a, and ap-southeast-1b. Record every public IPv4 address with its region for use as later DNS record values. If a page fails, check user data, httpd, the security group, and public routing first.
Transcript
03:58 So now to summarize, let's see
04:00 if everything has been working properly.
04:02 So, we have one EC2 instance right here.
04:05 And let's take the public IP, so I'll just copy
04:08 the IP itself, make sure using the IP via http.
04:12 And it says hello world from blah, blah, blah.
04:14 So this is good, so what I'm going to do
04:15 is that I'm going to, under a text file,
04:18 just to have a mark of a trace of everything,
04:20 I'm going to put the IP address
04:23 as well as the region I'm in.
04:24 So EU central one.
04:26 As you can see, it says hello from AZ EU central one B.
04:30 Okay, so this instance is working.
04:31 I'm just testing whereas everything's working.
04:33 So I'm going to also take this public IP right here,
04:38 paste it in, and it says yes hello from US East one A.
04:42 So this is perfect, so this is US East one.
04:46 And the last instance right now it's here.
04:52 And then I'm going to copy this IPv4 address,
04:57 paste it in, and it says hello from AP Southeast one b.
05:01 So this one's working as well.
05:02 So let's go here, AP southeast one.
7. 等待 ALB Active，并用 DNS Name 验证 Frankfurt Target
时间范围：05:08–05:40
总结 / Summary
中文
等待 ALB Provisioning 完成并进入 Active，复制其 DNS Name 访问。由于 Target Group 当前只注册 Frankfurt Instance，返回页面显示该 Instance 的内部 Hostname 与 eu-central-1b。应把 ALB DNS Name 与三个 EC2 Public IP 一并保存，供 Route 53 Alias 与各类 Routing Policy 实验使用。
English
Wait for the ALB to finish provisioning and become active, then open its DNS name. Because the target group currently contains only the Frankfurt instance, the page shows that instance's internal hostname and eu-central-1b. Save the ALB DNS name alongside the three EC2 public IPs for Route 53 alias and routing-policy labs.
Transcript
05:08 And finally, if I go under my ALB
05:13 and take the DNS name right here,
05:15 let's see if it has been provisioned.
05:17 So let's refresh this.
05:18 So it is provisioned as we can tell.
05:20 So this can take a bit of time.
05:21 So for you, it may not work, for me it worked.
05:24 And so because it is pointing to one EC2 instance,
05:26 it's a hello world from AZ EU Central one B.
05:30 So now we have properly set up
05:33 all our instances, as well our GNS.
05:35 So we're good to go.
05:36 And keep this information handy,
05:38 and I will see you in the next lecture.
整讲总结 / Overall Summary
中文
本讲为 Route 53 实验准备了 Frankfurt、N. Virginia、Singapore 三台带 Hostname/AZ 页面标识的 EC2，以及 Frankfurt 的 Internet-facing ALB。逐一验证三台 Public IP 和 ALB DNS，并保存各地址；它们将作为后续多种 Route 53 Routing Policy 的 Target。
English
The lecture prepares three EC2 web servers in Frankfurt, Northern Virginia, and Singapore, each displaying hostname and AZ, plus an internet-facing ALB in Frankfurt. It verifies every public IP and the ALB DNS name and saves them as targets for later Route 53 routing-policy exercises.
返回顶部 ↑