I'm a beginner in AWS infrastructure, and after watching many videos and testing VPC configurations, I learned a valuable lesson that cost me 2.14 USD.
The project required a custom VPC with public and private subnets, a NAT Gateway so instances in the private subnet could access the Internet, and an Elastic IP associated with the NAT Gateway.
When I finished the project, I manually deleted the VPC and thought I had removed all associated resources.
Days later, I noticed charges on my free tier account. Reviewing Cost Explorer, I saw increasing charges for inactive Elastic IPs, the so-called Idle IPv4 charges, which quickly added up and explained part of the bill.
At the time, I didn't realize that the Elastic IPs associated with the NAT Gateways of the deleted VPC were still reserved in my account. Once I found out, I released the Elastic IPs immediately.
I contacted AWS support explaining that I'm a beginner and that the oversight was unintentional, that I had already released the addresses, and I asked for a review of the charge. After providing the information and confirming the action, I received an email from AWS stating that they had waived my July bill, that there were no remaining debts, and that the waiver was applied successfully. I especially appreciate the help of the support agent who handled my case.
I learned that although the amount was small, the lesson is huge: charges for forgotten resources can grow, and it's easy to avoid them by following good practices.
Key lessons and recommendations: always release Elastic IPs and delete NAT Gateways when you tear down a VPC; monitor the billing dashboard and use Cost Explorer regularly; enable budget alerts to detect unexpected charges; document a teardown checklist and don't hesitate to contact support if you make an unintentional mistake.
My new teardown checklist includes terminating instances, deleting NAT Gateways, releasing Elastic IPs, deleting route tables and subnets, and finally deleting the VPC. I also enabled billing alerts to detect any anomalies in time.
At Q2BSTUDIO, a custom software and application development company, we offer expertise in AWS and Azure cloud services, custom software, custom applications, artificial intelligence and AI for businesses, cybersecurity, business intelligence services, AI agents, and Power BI solutions. If you manage cloud infrastructure, remember that improper resource deletion can generate avoidable costs; at Q2BSTUDIO we help design secure and efficient architectures, automate environment teardown, implement cost management policies, and apply best practices in cybersecurity and artificial intelligence to optimize operations and costs.
Final reflection: the cost was small but the lesson is huge. Use the cloud responsibly, set up alerts, and review reserved resources like Elastic IPs to avoid surprises. If you need help with cost audits, migrations, custom application development, artificial intelligence solutions, or cloud security, contact Q2BSTUDIO and we'll support you every step of the way.
Have you ever had a similar oversight with cloud resources and been charged for it? Share your experience so others can learn and avoid the same trap.
