Your cloud cost data is lying to you (here's the fix)
Resource IDs churn every time an image refreshes. Tags don't — but only if you design the taxonomy right, not retrofit it.
Stop Tracking Cloud Costs by Resource ID
Most cost-tracking systems start the same way: key everything off resource IDs — EC2 instance IDs, RDS ARNs, whatever the cloud provider hands you. It works, right up until it doesn't. The moment a routine AMI refresh cycles an instance, the ID changes, and every historical cost record tied to that ID becomes an orphan.
The Fix Is Identity, Not Tracking
The more durable approach is to stop keying cost data on infrastructure identity and start keying it on business identity — expressed through a small, mandatory tag taxonomy: Application, Environment, Owner, and Cost Center.
Once tagging is enforced at provisioning time, not applied retroactively, cost tracking survives instance churn automatically. The resource can be replaced, resized, or migrated entirely — the business identity attached to it doesn't move.
Where This Gets Hard
The hard part isn't the taxonomy. It's enforcement — getting tagging treated as a provisioning requirement rather than a best practice. That's a governance problem before it's an engineering one.