AWS · Advanced Networking Specialty

网络课程笔记

Lecture 022 · 4 张幻灯片

幻灯片、双语总结及 Transcript · 图片已内嵌,可离线阅读。

原文默认收起
lecture-022.md

Lecture 22: New ! Regional NAT Gateway (Re:invent 2025)

  • 课程:[NEW] AWS Certified Advanced Networking Specialty 2026
  • 视频时长:03:48
  • 来源:Udemy Lecture 54100957
  • Slide 数量:4
  • 画面切换:约 00:13、01:24、03:00

扫描说明

按页面英文 transcript 的 52 个时间点逐一定位并检查视频画面。标题页、传统 NAT 网关、区域级 NAT 网关特性和最终架构图分别作为独立小节;同一页中的项目和网络组件逐步出现视为动画构建。

Transcript 来自 Udemy 页面自带的英文自动字幕,没有使用 ASR。下面保留页面原文,包括其中的语法或识别错误。

1. AWS Regional NAT Gateway Announcement

时间范围:00:00–00:13

AWS Regional NAT Gateway title slide

总结 / Summary

中文

本讲介绍 AWS re:Invent 2025 发布的区域级 NAT 网关(Regional NAT Gateway, RNAT)。讲师先回顾传统 NAT 网关(Traditional NAT Gateway)的限制,再说明新资源如何简化多可用区出站互联网连接。

English

This lecture introduces the Regional NAT Gateway (RNAT) announced at AWS re:Invent 2025. The instructor first reviews the limitations of the traditional NAT Gateway, then explains how the new regional resource simplifies multi-AZ outbound Internet connectivity.

Transcript

00:00 Hi.

00:00 So if you are following the Reinvent 2025 announcement, you might heard about AWS regional Nat gateway.

00:08 So in this lecture let's try to understand what is regional Nat gateway.

2. Traditional NAT Gateway

时间范围:00:13–01:24

Traditional NAT Gateway architecture and limitations

总结 / Summary

中文

传统 NAT 网关(Traditional NAT Gateway)是可用区级资源(Availability Zone-scoped Resource)。为了高可用,需要在每个可用区(Availability Zone, AZ)部署 NAT 网关;每个网关还必须位于公有子网(Public Subnet),其子网路由表通过互联网网关(Internet Gateway, IGW)访问公网。单 AZ 只有一个 NAT 时,该 AZ 或网关故障会使相关私有工作负载失去互联网出口。

English

A traditional NAT Gateway is scoped to one Availability Zone (AZ). High availability therefore requires one gateway per AZ, and each gateway must live in a public subnet whose route table reaches the Internet through an Internet Gateway (IGW). With only one NAT in one AZ, a gateway or AZ failure removes Internet egress for the affected private workloads.

Transcript

00:12 But before we talk about that let's first talk about the traditional Nat gateway.

00:18 So the scope of traditional Nat gateway is easy level which means for high availability of Nat gateways,

00:25 you need to launch these Nat gateways in multiple AZS, which definitely adds some manual overhead.

00:33 Further, in order to launch this Nat gateway, you need to have your own public subnet and you have

00:38 to also configure the route for that subnet so that traffic can go from Nat gateway to the internet

00:44 gateway.

00:45 So your VPC setup will look something like this where the private subnet has the outbound internet connection

00:52 for IPv4 addresses through the Nat gateway and Nat gateway subnet route table will have this route table

00:58 entry to take the traffic out to the internet through the internet gateway.

01:03 So that's a traditional Nat gateway.

01:06 Now this Nat gateway is only in one AZ.

01:09 And which means if this Nat gateway goes down, your application servers will not be able to access

01:15 the internet.

01:16 and that's where it is recommended to launch another Nat gateway in another AZ, which is obviously

01:22 extra work for you.

3. Regional NAT Gateway Characteristics

时间范围:01:24–03:00

Regional NAT Gateway characteristics and multi-AZ design

总结 / Summary

中文

区域级 NAT 网关(Regional NAT Gateway, RNAT)在 VPC 级别工作并跨多个可用区。它既可根据工作负载自动扩展到新增 AZ,也可用手动模式指定覆盖的 AZ。RNAT 保持可用区亲和性(Zonal Affinity),尽量让某 AZ 的工作负载使用同 AZ 的 NAT 路径,从而避免跨 AZ 数据传输费用。AWS 负责公有侧基础设施和专用路由表,用户不必为 RNAT 创建公有子网,只需修改私有子网路由表。

English

A Regional NAT Gateway operates at the VPC level and spans multiple Availability Zones. It can automatically expand into AZs as workloads are deployed, or use manual mode to select specific AZs. RNAT maintains zonal affinity so workloads normally use a NAT path in the same AZ, avoiding cross-AZ data transfer charges. AWS manages the public-side infrastructure and a dedicated route table, so customers do not create public subnets for RNAT; they only update the private subnet route tables.

Transcript

01:24 And that's where AWS has now launched regional Nat gateway.

01:29 And as the name suggests, it works at the VPC level and it can span across multiple availability zone.

01:37 And when you create this Nat gateway, you have the option to either automatically expand it to additional

01:44 AZS.

01:45 So depending on in which AZ you have your workload, this Nat gateway will automatically expand into

01:51 that Z.

01:52 However, if you need more control and if you want to configure in which all AZS this Nat gateway should

01:59 be present, then you can also configure the manual mode for this Nat gateway where you can specify

02:07 I want this Nat gateway in this specific AZS.

02:07 Now few additional things that you should know about the Nat gateway is that because it is in multiple

02:17 AZS, it tries to maintain the zonal affinity, which means traffic from a particular application server

02:24 in AZ one will be routed through the Nat gateway in that AC only, so that there is no inter AZ data

02:31 transfer charge further because now it is fully managed service, you do not need to create the public

02:37 subnet for this regional Nat gateway.

02:40 AWS will manage it for you.

02:40 Further, there will also be a route table which will be automatically created for this regional Nat

02:47 gateway.

02:49 So this means for the end user, we just need to configure the private subnet route tables and route

02:56 the internet bound traffic through the regional Nat gateway.

4. Regional NAT Gateway Architecture

时间范围:03:00–03:48

Regional NAT Gateway VPC-level architecture

总结 / Summary

中文

架构中,应用实例仍位于多个私有子网(Private Subnet),区域级 NAT 网关(Regional NAT Gateway)直接创建在 VPC 范围内。每个私有子网路由表把 0.0.0.0/0 指向 RNAT,即可获得 IPv4 出站互联网访问。视频中特别说明:此内容主要用于了解新功能,讲师预计至少到 2026 年底之前不会出现在该认证考试中。

English

In the architecture, application instances remain in private subnets across multiple AZs, while the Regional NAT Gateway is created at VPC scope. Pointing each private subnet's 0.0.0.0/0 route to RNAT provides IPv4 outbound Internet access. The video explicitly presents this as informational and says the instructor does not expect it on the certification exam through at least the end of 2026.

Transcript

03:00 And typically this is how the architecture for the Nat gateway will be.

03:04 So you will have your instances in the private subnet.

03:07 And for the regional Nat gateway you do not need to create any subnets.

03:12 You will just create the Nat gateway in the VPC.

03:15 And that's it.

03:17 You then just need to modify the route table for this subnet to route the outbound internet traffic

03:22 through the regional Nat gateway.

03:25 Something like this.

03:27 All right.

03:28 So that's it about the Nat gateway that you should know as of now and in your AWS certification exam,

03:34 this is not going to be there for at least by the end of 2026.

03:39 So don't worry about that.

03:41 This lecture was just for your information.

03:44 All right with that.

03:45 Now let's go to the next lecture.

整讲总结 / Overall Summary

中文

区域级 NAT 网关(Regional NAT Gateway, RNAT)把传统按 AZ 部署的 NAT 模式提升为 VPC 级托管能力:可自动或手动覆盖多个可用区(Availability Zone),保持可用区亲和性(Zonal Affinity),并免除用户创建公有 NAT 子网和维护其路由表的工作。用户仍需在各私有子网路由表(Private Route Table)中把默认互联网路由指向 RNAT。与传统 NAT 相比,它重点降低了多 AZ 高可用设计的部署和运维复杂度。

English

Regional NAT Gateway (RNAT) elevates the traditional per-AZ NAT pattern into a VPC-level managed capability. It can cover multiple Availability Zones automatically or manually, preserves zonal affinity, and removes the need for customers to create public NAT subnets and maintain their route tables. Customers still point the default Internet route in each private subnet route table to RNAT. Compared with traditional NAT, its main benefit is reduced deployment and operational complexity for multi-AZ high availability.

返回顶部 ↑