<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Daniel Nkeng</title>
    <description>The latest articles on DEV Community by Daniel Nkeng (@daniel_nkeng_eb88d402164a).</description>
    <link>https://dev.to/daniel_nkeng_eb88d402164a</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4249669%2Fd5b7fdb4-9954-42e8-ab8d-fca1d6751f07.png</url>
      <title>DEV Community: Daniel Nkeng</title>
      <link>https://dev.to/daniel_nkeng_eb88d402164a</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/daniel_nkeng_eb88d402164a"/>
    <language>en</language>
    <item>
      <title>The 5 AWS resources that keep billing after your lab is ‘done’</title>
      <dc:creator>Daniel Nkeng</dc:creator>
      <pubDate>Tue, 17 Nov 2026 13:44:13 +0000</pubDate>
      <link>https://dev.to/daniel_nkeng_eb88d402164a/the-5-aws-resources-that-keep-billing-after-your-lab-is-done-1692</link>
      <guid>https://dev.to/daniel_nkeng_eb88d402164a/the-5-aws-resources-that-keep-billing-after-your-lab-is-done-1692</guid>
      <description>&lt;p&gt;You finish an AWS lab late at night, close the laptop, and think you're done. Weeks later there's an email from AWS with a number you didn't expect.&lt;/p&gt;

&lt;p&gt;Almost none of these bills come from advanced services. They come from a few resources that &lt;strong&gt;bill by the hour just for existing&lt;/strong&gt;, whether or not anything is using them. Here are the five I would check first, with the maths, so you can verify it yourself on the AWS pricing page. (Prices are US East examples. Check your region.)&lt;/p&gt;

&lt;h3&gt;
  
  
  1. NAT gateway: about $32 a month
&lt;/h3&gt;

&lt;p&gt;A NAT gateway costs about &lt;strong&gt;$0.045 per hour&lt;/strong&gt;, plus a small charge per GB processed. It bills even if no traffic passes through it.&lt;/p&gt;

&lt;p&gt;&lt;code&gt;$0.045 × 24 hours × 30 days ≈ $32&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;Many VPC wizards and tutorials offer to create one for you, so it's easy to click through without noticing.&lt;/p&gt;

&lt;h3&gt;
  
  
  2. Load balancer: about $16 a month
&lt;/h3&gt;

&lt;p&gt;An Application Load Balancer is about &lt;strong&gt;$0.0225 per hour&lt;/strong&gt; plus usage: &lt;code&gt;$0.0225 × 24 × 30 ≈ $16&lt;/code&gt;. "Easy deployment" tutorials often create one behind the scenes.&lt;/p&gt;

&lt;h3&gt;
  
  
  3. A database you only "stopped"
&lt;/h3&gt;

&lt;p&gt;A small RDS instance is around &lt;strong&gt;$12 a month&lt;/strong&gt; or more with storage. Stopping it isn't enough: &lt;strong&gt;AWS restarts a stopped RDS instance automatically after 7 days&lt;/strong&gt;, and its storage bills the whole time. Delete it when the lab is finished.&lt;/p&gt;

&lt;h3&gt;
  
  
  4. Public IPv4 addresses: about $3.65 each
&lt;/h3&gt;

&lt;p&gt;Since 2024 AWS charges &lt;strong&gt;$0.005 per hour&lt;/strong&gt; for every public IPv4 address, whether it's attached to a running instance or sitting unused: &lt;code&gt;$0.005 × 24 × 30 = $3.60&lt;/code&gt; each. A typical web-app lab can have five of them, which is about $18 a month.&lt;/p&gt;

&lt;h3&gt;
  
  
  5. Elastic IPs left behind by a NAT gateway
&lt;/h3&gt;

&lt;p&gt;When you delete a NAT gateway, its Elastic IP is freed but &lt;strong&gt;not released&lt;/strong&gt;. It keeps billing until you choose &lt;strong&gt;Release Elastic IP addresses&lt;/strong&gt;. This is the most commonly missed step in teardown.&lt;/p&gt;

&lt;h3&gt;
  
  
  Put it together
&lt;/h3&gt;

&lt;p&gt;A classic "three-tier" lab (a load balancer, two EC2 instances, an RDS database, a NAT gateway and five public IPs) comes to roughly &lt;strong&gt;$95 a month if you forget it&lt;/strong&gt;, from a lab that took two hours.&lt;/p&gt;

&lt;h3&gt;
  
  
  How to find what's billing you (10 minutes)
&lt;/h3&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Cost Explorer:&lt;/strong&gt; Billing and Cost Management → Cost Explorer. (The first time, enable it. Data can take up to 24 hours to show.) Set the range to the last 7 days, granularity &lt;strong&gt;Daily&lt;/strong&gt;, group by &lt;strong&gt;Usage type&lt;/strong&gt;.

&lt;ul&gt;
&lt;li&gt;
&lt;code&gt;NatGateway-Hours&lt;/code&gt; means a NAT gateway exists.&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;LoadBalancerUsage&lt;/code&gt; means a load balancer exists.&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;PublicIPv4:InUseAddress&lt;/code&gt; or &lt;code&gt;PublicIPv4:IdleAddress&lt;/code&gt; means public IPs.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Group by Region&lt;/strong&gt; too. A flat daily bill in a region you don't use means something is running there.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Check from the command line&lt;/strong&gt;, per region:
&lt;/li&gt;
&lt;/ol&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;aws ec2 describe-nat-gateways \
  --filter &lt;span class="nv"&gt;Name&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;state,Values=available,pending \
  --query &lt;span class="s2"&gt;"NatGateways[].[NatGatewayId,VpcId]"&lt;/span&gt; --output table

aws ec2 describe-addresses \
  --query &lt;span class="s2"&gt;"Addresses[].[PublicIp,AllocationId,AssociationId]"&lt;/span&gt; --output table
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Any row returned is a resource that costs money.&lt;/p&gt;

&lt;h3&gt;
  
  
  How to delete in the right order
&lt;/h3&gt;

&lt;p&gt;AWS blocks deletion when something depends on the resource, so order matters:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Auto Scaling groups (otherwise they relaunch instances you terminate)&lt;/li&gt;
&lt;li&gt;Load balancers&lt;/li&gt;
&lt;li&gt;EC2 instances (&lt;strong&gt;terminate&lt;/strong&gt;, not stop)&lt;/li&gt;
&lt;li&gt;RDS databases&lt;/li&gt;
&lt;li&gt;NAT gateways (wait until the state reads &lt;strong&gt;Deleted&lt;/strong&gt;)&lt;/li&gt;
&lt;li&gt;Elastic IPs (&lt;strong&gt;release&lt;/strong&gt; them)&lt;/li&gt;
&lt;li&gt;VPC endpoints and storage (volumes, then AMIs, then snapshots)&lt;/li&gt;
&lt;li&gt;The VPC last&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Then check Cost Explorer again &lt;strong&gt;the next day&lt;/strong&gt;. Billing data lags by hours, so a clean sweep today and a $0.00 line tomorrow together mean you're safe.&lt;/p&gt;

&lt;h3&gt;
  
  
  Set a $1 alert before your next lab
&lt;/h3&gt;

&lt;p&gt;Create a monthly &lt;strong&gt;$10&lt;/strong&gt; budget with alerts at &lt;strong&gt;$1, $5 and $10&lt;/strong&gt;, set as absolute values, not percentages. A $1 alert means something is running that shouldn't be. Alerts are a smoke detector, not a seatbelt, because billing lags, so the cleanup habit matters more than the alert.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;I wrote a short playbook that puts all of this in one place: the account lockdown, the 10 services that bill by the hour, the delete order, a Notion lab log, and a 7-day plan, plus scripts and printable checklists. It's paid, so I'm telling you plainly: &lt;a href="https://selar.com/487198w19v" rel="noopener noreferrer"&gt;https://selar.com/487198w19v&lt;/a&gt;.&lt;br&gt;
Everything in this article is free to use without it.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;— Daniel Nkeng&lt;/em&gt;&lt;/p&gt;

</description>
      <category>aws</category>
      <category>cloud</category>
      <category>beginners</category>
      <category>devops</category>
    </item>
  </channel>
</rss>
