<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>ECR on The David Page</title><link>https://thedavidpage.pages.dev/tags/ecr/</link><description>Recent content in ECR on The David Page</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Thu, 18 Jun 2026 09:00:00 +0700</lastBuildDate><atom:link href="https://thedavidpage.pages.dev/tags/ecr/index.xml" rel="self" type="application/rss+xml"/><item><title>The NAT Gateway 'Trick' That Was Actually Billing You for ECR, Not S3</title><link>https://thedavidpage.pages.dev/posts/cloud/aws/networking/nat-gateway-s3-gateway-endpoint/</link><pubDate>Thu, 18 Jun 2026 09:00:00 +0700</pubDate><guid>https://thedavidpage.pages.dev/posts/cloud/aws/networking/nat-gateway-s3-gateway-endpoint/</guid><description>&lt;p&gt;&lt;strong&gt;A client&amp;rsquo;s NAT Gateway bill hit a record ~$3,000/month. VPC Flow Logs pointed straight at S3 — except the client swore they barely used S3. Here&amp;rsquo;s what was actually going on.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Hi everyone 👋&lt;/p&gt;
&lt;p&gt;A client came to us about a month after going live with a new system built by a different vendor — one they no longer had a maintenance contract with. Their first full invoice after launch showed a &lt;strong&gt;NAT Gateway bill at a record high, roughly $3,000/month&lt;/strong&gt;. Standard architecture on their end: ECS services running in private subnets for security, NAT Gateway for outbound access. Textbook setup on paper — which made a bill that high, right out of the gate, more confusing, not less.&lt;/p&gt;</description></item></channel></rss>