Skip to content
Fixedmark

Cost · 11 min read

Updated

NAT Gateway Hidden Costs for One Static IP

In Mumbai (`ap-south-1`) one AWS NAT gateway costs $0.056 an hour, $0.056 per GB it processes in either direction, and $0.005 an hour for its Elastic IP. Two gateways for two Availability Zones cost about $89 a month before a single byte moves. Internet data transfer out, cross-AZ traffic, and AWS-service traffic through the gateway come on top.

On this page

The meters on one NAT gateway

A NAT gateway with an Elastic IP gives private-subnet compute a fixed outbound address, the one a bank, broker, or payout API puts on its allowlist. The bill for it has five parts.

  • Gateway hours. Each zonal gateway bills for every hour it exists. AWS's NAT gateway pricing guide says you pay for each hour the gateway is available, and the VPC pricing page says partial hours are billed as full hours.
  • Data processing. Every GB that passes through the gateway is billed, regardless of source or destination. Responses and downloads count, not only what you send.
  • Public IPv4. The gateway's Elastic IP costs $0.005 an hour like any other public address. Each secondary Elastic IP costs the same again.
  • Data transfer out. Bytes that leave AWS for the internet pay the normal internet egress rate. The NAT gateway does not replace this charge. It adds to it.
  • Cross-AZ transfer. Traffic from an instance in one Availability Zone to a gateway in another pays the regional data transfer rate on the way there and back.

Mumbai costs more than US East. The EC2 price list for ap-south-1 shows $0.056 per NAT gateway hour and $0.056 per GB processed, against $0.045 for both in US East (N. Virginia). The data transfer price list puts the first 10 TB of internet egress from Mumbai at $0.1093 per GB, against $0.09 in US East.

AWS published on-demand rates, ap-south-1 and us-east-1, checked November 2026
MeterMumbai (ap-south-1)N. Virginia (us-east-1)
NAT gateway, per hour$0.056$0.045
Data processed, per GB$0.056$0.045
Public IPv4, per address-hour$0.005$0.005
Internet data transfer out, per GB (first 10 TB after the free 100 GB)$0.1093$0.09
Cross-AZ transfer, per GB each side$0.01$0.01

Regional NAT gateways, which AWS announced on November 19, 2025, use the same numbers. The Mumbai price list bills them at $0.056 per hour for each Availability Zone they cover and $0.056 per GB, so one regional gateway across two zones costs the same as two zonal ones.

The fixed cost before any traffic

At 730 hours a month, one Mumbai gateway costs $0.056 x 730 = $40.88 in hours. Its Elastic IP adds $0.005 x 730 = $3.65. That is $44.53 a month for a gateway that has processed nothing.

Most production setups run more than one. AWS's NAT gateway basics say each gateway lives in one Availability Zone, and that if resources in several zones share one gateway and its zone goes down, the resources in the other zones lose internet access. The advice is one gateway per zone, with each zone's private subnets routed to their own gateway.

Fixed monthly NAT gateway cost in Mumbai, 730 hours, one Elastic IP per gateway
SetupGateway hoursPublic IPv4Per month
1 AZ, no redundancy$40.88$3.65$44.53
2 AZs$81.76$7.30$89.06
3 AZs$122.64$10.95$133.59

The same two-AZ setup in US East costs about $73 a month, which is the figure on the AWS NAT gateway comparison and the default in the NAT gateway cost calculator. The calculator uses US East rates, so add about a quarter to its gateway and processing lines for Mumbai.

Every environment pays it again

The fixed cost is per VPC, and teams usually have several. A dev, a staging, and a production VPC in Mumbai, each with a two-AZ NAT setup, cost 3 x $89.06 = $267.18 a month, or $3,206 a year, before traffic. Dev and staging often need no fixed IP at all. The gateways came with a copied network module.

If you are billed by AWS India, the invoice adds GST. AWS's India tax help page says AWS India charges IGST at 18% to customers outside Delhi, and CGST plus SGST at 9% each inside Delhi. The two-AZ setup above becomes about $105 a month on the invoice. A business that adds its GSTIN in Tax Settings can claim the input tax credit.

Downloads and AWS-service traffic are processed too

Inbound data from the internet is free on AWS, so downloads look free. Behind a NAT gateway they are not. The gateway processes the response on its way back to your instance, and every one of those GB is billed at $0.056 in Mumbai.

Common sources of download-heavy NAT traffic are container image pulls, package installs during builds, OS updates, and API responses larger than the requests that asked for them. A fleet that pulls a 1 GB image on every task start, 300 times a month, processes 300 GB. That is $16.80 of processing for traffic that would cost nothing to receive on a public subnet.

Traffic to S3 and other AWS services

Calls from a private subnet to S3, DynamoDB, ECR, CloudWatch Logs, or Secrets Manager also go through the NAT gateway unless you give them another path. Same-Region data transfer between EC2 and S3 is free, but the NAT processing charge still applies. A job that reads 1 TB a month from an S3 bucket in Mumbai through a NAT gateway pays about $56 in processing for it.

Gateway endpoints for S3 and DynamoDB remove that charge. The VPC pricing page says there are no data processing or hourly charges for gateway-type VPC endpoints. Add one to each route table your private subnets use, and that traffic stops touching the NAT gateway.

Terminal
aws ec2 create-vpc-endpoint \
  --region ap-south-1 \
  --vpc-id vpc-0123456789abcdef0 \
  --vpc-endpoint-type Gateway \
  --service-name com.amazonaws.ap-south-1.s3 \
  --route-table-ids rtb-0123456789abcdef0 rtb-0fedcba9876543210

Other services need interface endpoints, and those are not free. The VPC price list for Mumbai shows $0.013 per endpoint per AZ per hour and $0.01 per GB processed. One interface endpoint in one AZ costs $0.013 x 730 = $9.49 a month. It saves $0.056 - $0.01 = $0.046 per GB, so it pays for itself above about 206 GB a month per AZ. Below that, the NAT gateway is cheaper for that service. For ECR, the ECR endpoint guide says image layers are stored in S3, so the free S3 gateway endpoint carries most of the bytes of an image pull. The ecr.api and ecr.dkr interface endpoints carry the smaller API calls and manifests.

Cross-AZ traffic, the meter nobody draws

Running a single gateway for every private subnet saves $44.53 a month per zone you drop. It also moves cost somewhere harder to see. Traffic from the other zones now crosses an AZ boundary to reach the gateway, and the responses cross back.

The Mumbai rate for regional data transfer is $0.01 per GB. AWS's Cost and Usage Report guide says that for data transfer within a Region you are charged for both inbound and outbound traffic, and that each transfer shows up as two DataTransfer-Regional-Bytes line items. Plan on $0.02 for each GB that crosses a zone on its way to or from the gateway, on top of the $0.056 processing.

The break-even is easy to work out. A second Mumbai gateway costs $44.53 a month. Cross-AZ traffic costs $0.02 per GB. Above about 2,226 GB a month of traffic from the far zone, the second gateway is cheaper. Below it, one gateway is cheaper, and you accept that a zone outage cuts internet access for the whole VPC.

Regional NAT gateways and the 60-minute window

A regional NAT gateway follows your workloads across zones and bills per zone it is present in. AWS documents that it can take up to 60 minutes to expand into a new zone after a resource starts there. Until it does, that resource's traffic is processed by the gateway in an existing zone, which means cross-AZ charges for that window.

What it costs once a partner allowlists the IP

  • One address per zone. A zonal gateway per AZ gives you one Elastic IP per AZ, so a two-AZ setup means the partner allowlists two addresses. Many broker and bank forms have exactly two slots. See why brokers ask for a primary and secondary IP and static IP pairs and failover.
  • Regional mode can change the set. In automatic mode, AWS manages the gateway's IP addresses and zone expansion. For an allowlist you want manual mode, where you associate Elastic IPs you hold to each zone yourself, or automatic mode with an IPAM policy that draws from addresses you own.
  • Converting costs a window. AWS's regional NAT docs say switching from zonal to regional either gives you new IP addresses, which the partner must allowlist first, or requires deleting the zonal gateways to free their addresses, which interrupts traffic.
  • Deleted gateways leave billed addresses. AWS's guide to working with NAT gateways says deleting a gateway disassociates its Elastic IP but does not release it. Kept for the allowlist, it bills $3.65 a month as an idle address.
  • Secondary IPs multiply the charge. A zonal gateway can hold up to 8 addresses (2 Elastic IPs by default, more after a quota increase), and each one is a public IPv4 address at $0.005 an hour. You add them for more than 55,000 simultaneous connections to one destination, and every added address is one more for the partner to allowlist.

There is also the cost of scope. A NAT gateway translates everything the routed subnets send to the internet. If only one payout API needs the fixed address, you still pay processing on every image pull, telemetry upload, and third-party API call from those subnets. The AWS public IPv4 charge explainer covers the address side, and the NAT gateway alternatives post covers other ways to get a fixed egress address.

Worked monthly examples in Mumbai

These use the Mumbai rates above and 730 hours. Internet egress assumes the account's free 100 GB a month, which the EC2 pricing page says is shared across services and Regions, is either enough or already used elsewhere. Each scenario says which.

  1. 1
    A. A payout job on LambdaA Lambda function in two private subnets calls a payout API a few thousand times a month. About 5 GB passes through the gateways, 1 GB of it outbound, inside the free egress tier. Fixed $89.06, processing 5 x $0.056 = $0.28, egress $0. Total $89.34 a month. More than 99% of the bill is the cost of existing.
  2. 2
    B. A busy ECS serviceTasks in two AZs, each zone with its own gateway. 500 GB processed a month, 200 GB of it outbound, with the free tier used elsewhere. Fixed $89.06, processing 500 x $0.056 = $28.00, egress 200 x $0.1093 = $21.86. Total $138.92.
  3. 3
    C. Scenario B with one shared gatewaySame traffic through one gateway in the first AZ. Half of it, 250 GB, comes from tasks in the second AZ. Fixed $44.53, processing $28.00, egress $21.86, cross-AZ 250 x $0.02 = $5.00. Total $99.39. It saves $39.53 a month and loses the second zone's internet access whenever the first zone fails.
  4. 4
    D. Scenario B plus S3 reads through the gatewayAdd 1,000 GB a month of reads from an S3 bucket in Mumbai, with no gateway endpoint. Processing rises to 1,500 x $0.056 = $84.00. Same-Region S3 transfer is free, so egress stays $21.86. Total $194.92. Adding the free S3 gateway endpoint brings it back to $138.92.
Monthly totals for the scenarios above, Mumbai rates, before GST
ScenarioFixedProcessingEgressCross-AZTotal
A. Lambda payout job$89.06$0.28$0.00$0.00$89.34
B. ECS, two gateways$89.06$28.00$21.86$0.00$138.92
C. ECS, one gateway$44.53$28.00$21.86$5.00$99.39
D. B plus S3 via NAT$89.06$84.00$21.86$0.00$194.92

At low volume the fixed cost is the whole bill. At higher volume, processing counts both directions, and AWS-service traffic through the gateway can double it.

Find each meter on your bill

Each meter has its own usage type with a Region prefix. Mumbai's prefix is APS3. Zonal gateways bill as APS3-NatGateway-Hours and APS3-NatGateway-Bytes, regional gateways as APS3-RegionalNatGateway-Hours and APS3-RegionalNatGateway-Bytes. Cross-AZ traffic is APS3-DataTransfer-Regional-Bytes, internet egress is APS3-DataTransfer-Out-Bytes, and the address is APS3-PublicIPv4:InUseAddress.

Terminal
aws ce get-cost-and-usage \
  --time-period Start=2026-10-01,End=2026-11-01 \
  --granularity MONTHLY \
  --metrics UsageQuantity UnblendedCost \
  --filter '{"Dimensions":{"Key":"USAGE_TYPE","Values":[
    "APS3-NatGateway-Hours","APS3-NatGateway-Bytes",
    "APS3-RegionalNatGateway-Hours","APS3-RegionalNatGateway-Bytes",
    "APS3-DataTransfer-Regional-Bytes","APS3-DataTransfer-Out-Bytes",
    "APS3-PublicIPv4:InUseAddress","APS3-PublicIPv4:IdleAddress"]}}' \
  --group-by Type=DIMENSION,Key=USAGE_TYPE \
  --query "ResultsByTime[0].Groups[].[Keys[0], Metrics.UsageQuantity.Amount, Metrics.UnblendedCost.Amount]" \
  --output table

If NatGateway-Bytes is much larger than DataTransfer-Out-Bytes, most of what you process is downloads or traffic to AWS services. That is the signal to look for missing endpoints. DataTransfer-Regional-Bytes also includes cross-AZ traffic that has nothing to do with NAT, such as database replication, so treat it as an upper bound.

Per gateway, from CloudWatch

The bill does not split processing by direction. CloudWatch does. The NAT gateway metrics include BytesInFromSource, bytes the gateway received from your VPC, and BytesInFromDestination, bytes it received back from the internet. Their sum is a close estimate of what the gateway processed.

nat-bytes.sh
#!/usr/bin/env bash
set -euo pipefail

NAT_ID="nat-0123456789abcdef0"

for metric in BytesInFromSource BytesInFromDestination; do
  bytes=$(aws cloudwatch get-metric-statistics \
    --region ap-south-1 \
    --namespace AWS/NATGateway \
    --metric-name "$metric" \
    --dimensions Name=NatGatewayId,Value="$NAT_ID" \
    --start-time 2026-10-01T00:00:00Z \
    --end-time 2026-11-01T00:00:00Z \
    --period 86400 \
    --statistics Sum \
    --query 'sum(Datapoints[].Sum)' \
    --output text)
  awk -v m="$metric" -v b="$bytes" 'BEGIN { printf "%-24s %10.1f GiB\n", m, b / 1024^3 }'
done

A large BytesInFromDestination points at downloads. Regional NAT gateways publish these metrics with an AvailabilityZone dimension next to NatGatewayId, so for one of those, add Name=AvailabilityZone,Value=ap-south-1a and run it once per zone.

Doing this with Fixedmark

Fixedmark is a static IP proxy, in early access. It fits scenario A, where a NAT gateway exists only so one or two APIs see a fixed address. The Lambda function stays outside a VPC, with no gateways or Elastic IPs, and sends only the allowlisted calls through a proxy URL kept in FIXEDMARK_PROXY_URL. Bundle undici with the function. The partner allowlists the two addresses of your pair.

handler.mjs
import { fetch, ProxyAgent } from "undici";

// Built once per execution environment, reused by warm invocations.
const proxy = new ProxyAgent(process.env.FIXEDMARK_PROXY_URL);

export const handler = async (event) => {
  // Only this call goes through the fixed IP pair.
  const res = await fetch("https://api.partner.example/v1/payouts", {
    method: "POST",
    headers: { "content-type": "application/json" },
    body: JSON.stringify(event.payout),
    dispatcher: proxy,
  });
  return { status: res.status, body: await res.json() };
};

The planned launch price for a dedicated pair is $29 a month on Pro, with 100 GB of bandwidth, in Mumbai, Singapore, Newark, or Ashburn. Prices are planned and may change. AWS still bills internet egress for the bytes your function sends to the proxy, at the normal rate. In scenario A that is inside the free tier, so the comparison is about $29 against about $89.

It does not fit scenarios B to D. Tasks in private subnets that need general internet access still need a NAT gateway or public addresses, and the endpoint and zone advice above is what lowers that bill. The AWS Lambda guide has the full setup, and verify your egress IP before you send the addresses to a partner.

Sources

Checked November 2026. Confirm current details on the vendor's site before you decide. Prices and limits change.

Blog

Frequently asked questions

How much does an AWS NAT gateway cost per month in Mumbai?

One gateway costs $0.056 an hour, about $40.88 a month, plus $3.65 for its Elastic IP and $0.056 per GB processed. Two gateways across two Availability Zones cost about $89.06 a month before traffic, plus internet egress at $0.1093 per GB after the free 100 GB.

Does a NAT gateway charge for downloads?

Yes. Data processing applies to every GB through the gateway regardless of direction, so responses, image pulls, and package downloads are billed at the processing rate even though inbound internet data transfer is free.

Is one shared NAT gateway cheaper than one per AZ?

Below roughly 2.2 TB a month of traffic from the other zones, yes, in Mumbai. Each GB that crosses a zone costs about $0.02 extra. The tradeoff is that an outage in the gateway's zone cuts internet access for every zone.

Is a regional NAT gateway cheaper than zonal ones?

No. It is billed per Availability Zone per hour at the same rate, so covering two zones costs the same as two zonal gateways. It simplifies routing, and it can take up to 60 minutes to expand into a new zone.

How do I stop paying NAT charges for S3 traffic?

Add an S3 gateway endpoint to the route tables of your private subnets. Gateway endpoints for S3 and DynamoDB have no hourly or data processing charge, and that traffic then bypasses the NAT gateway.

Make it fixed.

Fixedmark is in early access. Join the list to get dedicated static IPs when your region opens.