Safer Internet Access

For servers in a VPC requiring Internet access, use SNAT supported by public NAT gateways to let the servers share an EIP while hiding their own IP addresses.

Advantages

-Flexible Deployment

NAT gateways can be shared across subnets.

-Flexible Choice of Gateway Types

Choose from a range of specifications designed for different needs.

-Cost-Effectiveness

Multiple instances share the same EIP to keep costs down.

Access from the Internet

Simply define port forwarding in DNAT rules so a public NAT gateway allows your instances to provide Internet-accessible services.

Advantages

-Flexible Deployment

NAT gateways can be shared across subnets.

-Cost-Effectiveness

Multiple instances share the same EIP, so fewer EIPs are needed.

High-Speed, Stable Internet Access

For on-premises servers connecting to a VPC through Direct Connect, configure SNAT and DNAT rules on public NAT gateways to allow the servers to share EIPs.

Advantages

-Speed and Stability

NAT gateways work in conjunction with Direct Connect to give your on-premises servers fast, stable access to the Internet.

Higher Performance with Multiple Gateways

If a single NAT gateway bottlenecks your services, use multiple ones. Simply create multiple route tables in your VPC to direct traffic from different VPC subnets to the NAT gateways you configure.

Unified Network Management

A private NAT gateway allows for communication between a VPC and an on-premises data center without needing to change your on-premises networks. This makes it safer and less expensive to migrate services to the cloud.

Advantages

– No Need for Network Changes

A private NAT gateway keeps communications clear of address conflicts thanks to a transit IP address, so your local VPC works seamlessly with your on-premises data center or a remote VPC.

– Overlapping IP Addresses Allowed

Two private NAT gateways can perform DNAT for the source and destination networks separately, allowing communication between overlapping networks.