---
title: "Discussion on \"How a missing S3 gateway endpoint route quintupled our NAT bill\" | Hashnode"
description: "Discussion on \"How a missing S3 gateway endpoint route quintupled our NAT bill\". The finance lead asked why AWS charged us $2,100 for NAT gateway data processing last month. Our normal was around $400. Nothing in the release calendar explained it: no new services, no traffic bump"
url: "https://hashnode.com/posts/how-a-missing-s3-gateway-endpoint-route-quintupled-our-nat-bill/6a587149388b49190d4ee894"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [How a missing S3 gateway endpoint route quintupled our NAT bill](https://blog.infraforge.agency/how-a-missing-s3-gateway-endpoint-route-quintupled-our-nat-bill?utm_source=hashnode&utm_medium=feed)

The finance lead asked why AWS charged us $2,100 for NAT gateway data processing last month. Our normal was around $400. Nothing in the release calendar explained it: no new services, no traffic bump

Jul 16 · 11 min read · blog.infraforge.agency  
Updated Nov 2  
Read the article

-   [#cloudcost](https://hashnode.com/tag/cloudcost)
-   [#triage](https://hashnode.com/tag/triage)
-   [#costspikes](https://hashnode.com/tag/costspikes)

## Written by

[Muhammad Hassaan Javed](https://hashnode.com/@itxcrusher)

@itxcrusher · Lahore, Pakistan

  
[View profile](https://hashnode.com/@itxcrusher)

Reducing your cloud bill, therapy bill, & blood pressure all at once!

Founder @ infraforge.agency Cloud &amp; DevOps engineer focused on infrastructure recovery, Terraform/IaC debt, Kubernetes stabilization, CI/CD reliability, and cloud migration recovery for SaaS teams.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
