How do you find the owner of an abandoned cloud server?
Cloud teams often cannot determine who owns unmanaged or underutilized instances, leaving them to rely on the "scream test"—shutting the server down to see who complains. This makes it difficult to clean up infrastructure safely and forces organizations to repeat the same inefficient identification process for years.
What people tried
Every workaround mentioned in the threads below. We haven’t tested any of them — and nobody here is claiming they worked.
Found another way around this?
Share your steps and trade-offs so fellow engineers don't have to reinvent the wheel. No account required.
- 1Using the scream test by powering off or scheduling deletion of instances to see who complainsDid this help you?
- 2Employing external monitoring techniques such as cost explorer, cloud trail, route 53, and network accessDid this help you?
- 3Calculating risk versus reward for each instance to justify investigation or shutdown costsDid this help you?
In their words
Unedited, grouped by where they were said, most upvoted first within each place, each linked to the thread it came from.
“Worse still, we're unable to determine who the owners of a lot of these instances are.”source ↗
Where this came up
People with this problem also raised
- 4What to do when a found cat's microchip is unregistered
- 2All-in-one platform for private consultancy and community hosting
- 4Tracking down unmanaged SaaS accounts when an employee leaves
- 3Why do CRM apps share my customer data with other companies?
- 3How to figure out what M365 or AD groups actually do
- 5How to stop juggling bookmarks for admin tools and reference sites