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.
- 1Using the scream test by powering off or scheduling deletion of instances to see who complains
- 2Employing external monitoring techniques such as cost explorer, cloud trail, route 53, and network access
- 3Calculating risk versus reward for each instance to justify investigation or shutdown costs
In their words
Unedited, most upvoted first, 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 ↗
shalomb · Server Fault · 5 upvotes
Where this came up
People with this problem also raised
- 3Why do CRM apps share my customer data with other companies?
- 5How to stop juggling bookmarks for admin tools and reference sites
- 2Automated notification emails only show IDs instead of client names
- 2Seller belongings still in the house during final walk-through
- 3Thrown into managing cloud architecture with no experience
- 3Why do former employees still have active logins?