The NAT Gateway Bill Exploded. Add More Gateways?

NAT Gateway data processing is now your biggest line item. A teammate thinks it is just bandwidth. Defend where the cost really comes from.

intermediate12 min5 roundsAWS

Answer key reviewed by Branko Petric

Read first: AWS VPC and Networking Basics

Your decision

Cost Explorer shows NAT Gateway data processing charges have become your largest line item. Private-subnet instances pull large images and data from S3 and ECR. A teammate says it is just bandwidth, add another NAT gateway. What do you do?

The situation

The monthly AWS bill jumped and Cost Explorer points at NAT Gateway data processing as the single largest line item. The amount of data flowing through the gateway has been climbing as the platform grows.

Context

Workloads run in private subnets and reach the internet through a NAT gateway. They pull container images from ECR on every deploy and read large objects from S3 constantly. There are currently no VPC endpoints configured. A teammate looked at the throughput and concluded the gateway is saturated, proposing to add a second NAT gateway to spread the load.

More: AWS scenario interview questions