rajesh on Nostr: the most common reason a nat gateway bill creeps: s3 reads from private subnets going ...
the most common reason a nat gateway bill creeps: s3 reads from private subnets going out through nat at $0.045/GB.
the fix is free and almost nobody does it first. gateway endpoints for s3 and dynamodb cost nothing — no hourly fee, no per-GB fee. you add a route, and that traffic goes over a private aws path instead of through the meter. it never touches nat again.
do this before anything fancier. most teams never need to go further.
#aws #cloudcost
https://rajesh.medampudi.com/blog/aws-nat-gateway-hidden-tax 
Published at
2026-06-30 17:37:02 UTCEvent JSON
{
"id": "eeab3a5cfcecd72caa4429ca86523c75a3d4aa93bc1958336081f882151c9945",
"pubkey": "bb1473b4c17f699dc02bfc27ca61d52eb68bd7e7870499b6cce0f86124672bcb",
"created_at": 1782841022,
"kind": 1,
"tags": [
[
"t",
"aws"
],
[
"t",
"cloudcost"
]
],
"content": "the most common reason a nat gateway bill creeps: s3 reads from private subnets going out through nat at $0.045/GB.\n\nthe fix is free and almost nobody does it first. gateway endpoints for s3 and dynamodb cost nothing — no hourly fee, no per-GB fee. you add a route, and that traffic goes over a private aws path instead of through the meter. it never touches nat again.\n\ndo this before anything fancier. most teams never need to go further.\n\n#aws #cloudcost\n\nhttps://rajesh.medampudi.com/blog/aws-nat-gateway-hidden-tax\nhttps://media.medampudi.com/fb94d6dc380dd2dc3a6d29d8189aa815d8ac91e3fa6cfc351706e18bc03dd332.png",
"sig": "5afbfeced603922d64464fd50770c977713784e7581c006218a06032ef93ee2a4842e9d6ddff3f77567c82b9026a3b0e95478584ddbd705fbbc92425af0685bf"
}
