All Topics
All Topics
Technology
Technology
Design
Design
Programming
Programming
Science
Science
News
News
Gaming
Gaming
Entertainment
Entertainment
Business
Business
Finance
Finance
Sports
Sports
Health
Health
Food
Food
Travel
Travel
Art
Art
Music
Music
Books
Books
Education
Education
Politics
Politics
Personal
Personal
No algorithm. No AI slop. No ads. Just RSS. Pro-human. Indie writers. Real journalism. Open web. Chronological. Hand toasted.

AWS Cost Lesson: How a Missing VPC Endpoint Led to $1,000 in Unexpected Charges

By

thecodemonkey

6mo ago· 6 min readenInsight

Summary

A developer shares a cautionary tale about accidentally incurring $1,000 in AWS charges due to a missing VPC Endpoint configuration. The article explains how data transfers from EC2 instances to S3 were routed through expensive NAT Gateways instead of using the free VPC Endpoint service, resulting in unexpected costs. The author provides technical details about AWS networking, VPC configurations, and lessons learned about monitoring and cost optimization. An update reveals AWS ultimately refunded the charges after understanding the oversight.

Key quotes

· 3 pulled
Update (January 7, 2026): Good news! AWS ended up refunding the entire amount after we explained what happened. Their support team was surprisingly understanding about our VPC Endpoint oversight.
A cautionary tale about AWS VPC networking, NAT Gateways, and how a missing VPC Endpoint turned our S3 data transfers into an expensive lesson.
I've been using AWS since around 2007. Back then, EC2 storage was entirely ephemeral and stopping an instance meant losing all your data. The platform has come a long way.
Snippet from the RSS feed
A cautionary tale about AWS VPC networking, NAT Gateways, and how a missing VPC Endpoint turned our S3 data transfers into an expensive lesson.

You might also wanna read