Menu

Post image 1
Post image 2
1 / 2
0

Debugging Hidden AWS Costs: From “Others” in Cost Explorer to a Real Root Cause

DEV Community·Mouheb GHABRI·25 days ago
#IVu0wF6M
#then#aws#cost#region#config#cloudtrail
Reading 0:00
15s threshold

I had an AWS account that was supposed to be almost empty. Most of the resources had already been deleted. Some cleanup had been done manually, and some of it had been done through tools like Terraform. So the expectation was simple: No active resources = no meaningful cost But Cost Explorer was still showing small charges. The amount was tiny, around a few fractions of a cent, but the problem was not the amount itself. The problem was that the charge was unclear. In the AWS Cost Explorer UI, part of the cost appeared under vague categories like: Others That was not enough to understand what was happening. The real question was: Why is an account that looks empty still generating cost? The actual problem At first, the charge looked confusing because the UI did not clearly explain the source. A small AWS bill can still hide important information: - Is there an orphaned resource? - Is AWS Config still recording resources? - Is Control Tower recreating or managing something? - Is CloudTrail charging money?…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.

Read More