Menu

Cut NAT gateway costs: cheaper Lambda in a VPC
📰

Cut NAT gateway costs: cheaper Lambda in a VPC

DEV Community: aws·Sascha Mirow-Stanitzok·7 days ago
#8UCSMGmf
#devtoaws#devto#dev#gateway#ipv6
Reading 0:00
15s threshold

NAT gateway costs are the line on the AWS bill that surprises me most often in serverless projects. The Lambda functions cost a few euros a month, and right next to them sits an amount for a network component that does little more than pass packets along. Ever since I deliberately added a NAT gateway in my article on the Claude IP allowlist , I wanted to run the numbers the other way round: when do you really need one, and how do you get rid of it when you don't?

So this is not a generic list of savings tips. You will learn how to measure where your traffic goes first and then change things on purpose: with gateway endpoints, with an honest break-even calculation for interface endpoints and with IPv6 as a way to reach the internet without any NAT at all. I walk through the change step by step with the Serverless Framework.

In short

A NAT gateway charges per hour and for every gigabyte that flows through it, even when the destination is S3 or DynamoDB in the same region.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.