Menu

The NAT Gateway bill is one line and the traffic belongs to twelve teams: who pays for the shared NAT in AWS, Azure, GCP and OCI
📰

The NAT Gateway bill is one line and the traffic belongs to twelve teams: who pays for the shared NAT in AWS, Azure, GCP and OCI

DEV Community: aws·Gonzalo Gjuka·about 3 hours ago
#jIooHQK7
#devtoaws#devto#dev#cost#resource
Reading 0:00
15s threshold

A network account runs one NAT Gateway per Availability Zone and, behind it, twelve teams go out to the internet: package downloads, calls to external APIs, backups to S3 that nobody routed through an endpoint. The VPC bill shows one line for the NAT hours and another for the GB it processed, both against the network account. When the time comes to split it, the question matches the one for any orphan resource: whose traffic is this? Until now the answer was a script over the flow logs or a fixed percentage per team. Since November 16 AWS has an answer of its own, and the other three clouds remain at the script stage. This note covers all four; everything comes from the official documentation and the sources sit at the end.

What a NAT Gateway charges and why the line is a single one

AWS charges a NAT Gateway for each hour it stays available and for each GB it processes.…

Continue reading — create a free account

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