AWS NAT Gateway Explained: Private Subnet Internet Access and Costs

Quick Answer

An AWS NAT Gateway is a managed service that translates private IP addresses to a public elastic IP address, allowing instances in a private subnet to reach the public internet securely. Unlike a self-managed EC2 instance running NAT software, AWS automatically scales the managed gateway to handle up to 45 Gbps of bandwidth, making it ideal for enterprise workloads. It operates inside a public subnet, pairs with an Internet Gateway, and processes traffic directed to it via custom VPC route tables using a default 0.0.0.0/0 destination. While straightforward to set up, understanding its hourly fees and gigabyte processing charges is vital to prevent unexpected infrastructure bills.

What Is a NAT Gateway?

A NAT Gateway acts as a bridge between isolated private subnets and the broader internet. In AWS VPC architecture, resources launched inside a private subnet do not possess public IPv4 addresses. When these resources need to communicate externally, their traffic must be translated. A managed NAT Gateway performs source Network Address Translation, rewriting the private source IP address of outbound packets to the public Elastic IP address attached to the gateway. When the response packets return from the internet, the gateway reverses this translation, ensuring the packets reach the correct internal server.

Compared to legacy self-managed NAT instances running on EC2, the managed AWS NAT Gateway eliminates single points of failure tied to instance sizing, eliminates manual OS patching, and automatically scales bandwidth from 5 Gbps up to 45 Gbps without administrator intervention. This makes it a foundational component for production-grade cloud environments requiring reliable egress paths.

NAT placement

Correct NAT placement is critical for maintaining both security and operational resilience. A NAT Gateway must always be created within a public subnet that has an active route to an Internet Gateway via a 0.0.0.0/0 route rule. If you place a NAT Gateway inside a private subnet, it will fail to route traffic externally because it lacks a direct path to the internet.

For robust high availability, cloud architects typically deploy multiple NAT Gateways—one per Availability Zone—rather than relying on a single gateway in a single zone. If Availability Zone A experiences an outage, workloads in Availability Zone B can continue routing their outbound traffic through their local zonal NAT Gateway, avoiding complete internet isolation for your application tiers.

Private Subnet Egress

Private subnet egress is the mechanism by which internal workloads safely initiate outbound network sessions. In a standard multi-tier application architecture, web servers might sit in public subnets behind an Application Load Balancer, while application logic servers and databases reside securely inside private subnets. These internal servers frequently need to pull container images from external registries, download OS security patches from package repositories, or send telemetry data to third-party SaaS monitoring tools.

By routing this outbound traffic through an AWS NAT Gateway, administrators ensure that external entities cannot initiate unsolicited inbound TCP or UDP connections toward the private workloads. The internal instances remain invisible and unreachable from the outside world, drastically reducing the overall attack surface of the cloud infrastructure.

Route table

AWS VPC route tables dictate how network traffic is directed. To enable private subnet egress, you must configure a custom route table associated with your private subnets. This route table must include an entry pointing all outbound internet-bound traffic (0.0.0.0/0) toward the target ID of your deployed NAT Gateway (nat-xxxxxxxxxxxxxxxxx).

When an application server sends a packet destined for an external IP address, the local operating system checks its routing table, matches the packet against the default route pointing to the NAT Gateway, and encapsulates the packet for delivery within the VPC fabric.

Routing Flow

Understanding the exact routing flow helps administrators debug connectivity timeouts and packet loss effectively. When a resource in a private subnet initiates a connection to an external endpoint, the following sequence of network events occurs:

1. The private instance generates an outbound packet with its own private IP as the source and the external server's public IP as the destination.
2. The private instance's network interface consults the private subnet route table and forwards the packet to the NAT Gateway interface.
3. The NAT Gateway receives the packet, performs source NAT by replacing the private source IP with its associated Elastic IP address, and records the connection state in its internal translation table.
4. The NAT Gateway forwards the translated packet out to the Internet Gateway.
5. The Internet Gateway routes the packet across the public internet to the destination server.
6. When the external server responds, it sends the packet back to the NAT Gateway's Elastic IP.
7. The NAT Gateway inspects the packet's connection tracking table, reverses the translation back to the original private instance's IP, and delivers the packet into the private subnet.

Availability and Architecture

Achieving high availability requires designing for zonal failure domains. Because an AWS NAT Gateway is provisioned within a specific Availability Zone and tied to a specific Elastic IP address, a failure in that zone would disrupt egress for any subnets depending exclusively on that gateway if proper multi-zone redundancy is omitted.

To build a fault-tolerant architecture, best practice dictates provisioning a separate NAT Gateway in each Availability Zone where your application runs. You then create distinct private route tables for each Availability Zone, ensuring that private instances in Zone A route their internet-bound traffic to the NAT Gateway in Zone A, and instances in Zone B route to the NAT Gateway in Zone B. This design prevents cross-AZ data transfer charges and maintains uninterrupted egress during localized cloud infrastructure degradation.

Cost Considerations

Cloud financial management is a primary concern when deploying networking primitives at scale. An AWS NAT Gateway incurs two distinct types of charges: a flat hourly fee for each hour the gateway exists, regardless of whether it is actively processing traffic, and a per-gigabyte data processing fee for every gigabyte of data that flows through the gateway in either direction.

Because the hourly fee accumulates continuously 24 hours a day, 365 days a year, idle or underutilized NAT Gateways can quickly become a disproportionate percentage of a smaller AWS monthly bill. Furthermore, data processing fees can scale rapidly if applications frequently pull large payloads, stream media, or transfer massive datasets across the internet through the gateway.

Cost

To optimize networking expenditures without sacrificing security, engineering teams can adopt several cost-conscious architecture patterns:

• Consolidate Gateways: In non-production environments like staging or development, consider deploying a single NAT Gateway shared across multiple private subnets rather than a dedicated gateway per Availability Zone, accepting the risk of temporary downtime during a zonal failure.
• Use Gateway VPC Endpoints: For traffic destined for AWS services like Amazon S3 or Amazon DynamoDB, deploy Gateway VPC Endpoints instead of routing traffic out through a NAT Gateway. VPC endpoints are free of hourly and data processing charges for supported services and keep traffic entirely within the AWS backbone network.
• Monitor with Cost Explorer: Set up AWS Budgets and Cost Anomaly Detection alerts specifically targeting networking cost categories to catch unexpected traffic spikes early.

{
  "costComponents": {
    "hourlyFee": "Fixed cost per hour active",
    "dataProcessingFee": "Charged per GB processed"
  }
}

Troubleshooting

When private subnet resources lose internet connectivity, systematic troubleshooting can quickly isolate the root cause. Common failure modes include misconfigured route tables, missing security group rules, or Elastic IP disassociations.

Start by verifying the private subnet's route table association using the AWS CLI:

aws ec2 describe-route-tables --filters "Name=association.subnet-id,Values=subnet-0123456789abcdef0"

Confirm that the output contains a route where DestinationCidrBlock is 0.0.0.0/0 and NatGatewayId points to an active gateway in the available state. Next, check the Network ACLs and Security Groups attached to both the private instance and the NAT Gateway interface to ensure outbound TCP/UDP ports and ephemeral return ports are not blocked. Finally, verify that the Elastic IP associated with the NAT Gateway has not been accidentally released or modified.

Alternatives and Trade-Offs

Selecting the right egress mechanism depends heavily on workload requirements, budget constraints, and operational complexity tolerance. While a managed NAT Gateway is the gold standard for most production architectures, alternative patterns exist:

Compared to self-managed NAT instances running on EC2, managed NAT gateways save significant operational engineering time despite their higher base cost. Meanwhile, VPC Interface Endpoints provide private connectivity to specific AWS and third-party partner services without traversing an internet gateway at all, offering an even more secure and cost-efficient alternative for specific API integrations.