"AWS has recently introduced regional availability for the managed NAT Gateway service. The new capability allows developers to create a single NAT Gateway that automatically spans multiple availability zones (AZs) in a VPC, providing high availability, eliminating the need to define separate gateways and public subnets in each zone. A NAT Gateway lets instances in a private subnet access the internet or other services outside a VPC using the NAT Gateway's IP address."
"If you are already operating AWS at scale, these early announcements are often more impactful than the keynote launches, adding major improvements to existing services. Case in point - regional NAT gateways. Whilst not addressing cost, they offer some significant quality of life benefits - in particular, no need to manage zonal routes in private subnets (they work as a regional resource similar to the Internet Gateway), they don't need public subnets (AWS manages that for you), and they scale across AZs as needed."
AWS introduced regional NAT Gateway allowing creation of a single NAT Gateway spanning multiple availability zones in a VPC. The regional gateway provides high availability and removes the need to define separate gateways and public subnets per AZ. Instances in private subnets can access external services using the NAT Gateway's IP address. The regional service automatically adjusts to workload distribution without requiring route table updates. Regional NAT Gateways offer automatic mode, where AWS manages IP addresses and AZ changes, and manual mode, where customers manage IP addresses per AZ. Expansion into a new AZ can take up to 60 minutes while traffic is processed across existing zones.
Read at InfoQ
Unable to calculate read time
Collection
[
|
...
]