NAT gateway architektura

[peldax]

We have observed that your Amazon VPC resources are using a shared NAT Gateway across multiple Availability Zones (AZ). To ensure high availability and minimize inter-AZ data transfer costs, we recommend utilizing separate NAT Gateways in each AZ and routing traffic locally within the same AZ.

Each NAT Gateway operates within a designated AZ and is built with redundancy in that zone only. As a result, if the NAT Gateway or AZ experiences failure, resources utilizing that NAT Gateway in other AZ(s) also get impacted. Additionally, routing traffic from one AZ to a NAT Gateway in a different AZ incurs additional inter-AZ data transfer charges. We recommend choosing a maintenance window for architecture changes in your Amazon VPC.

A list of your VPCs and NAT Gateways that are shared across AZ(s), in the format: 'VPC | NAT Gateway', can be found in the 'Affected resources' tab.

Please refer to the AWS public documentation on how to create a NAT Gateway [1], and how to configure routes for different NAT Gateway use cases [2].

Should you have any questions or concerns, please reach out to the AWS Support team [3].

[1] https://docs.aws.amazon.com/vpc/latest/userguide/vpc-nat-gateway.html#nat-gateway-working-with
[2] https://docs.aws.amazon.com/vpc/latest/userguide/nat-gateway-scenarios.html
[3] https://aws.amazon.com/support