Attaching Owners to Cloud Resources for Improved Governance

The Problem of Orphaned Cloud Resources

Cloud instances often continue running and incurring costs even after the engineer who provisioned them leaves the company. This lack of clear ownership makes it difficult for teams to determine if a resource can be safely shut down, leading to unnecessary expenses and operational uncertainty. The absence of an ownership history often results in time-consuming investigations when cost reviews flag unknown resources.

Pillars of Good Resource Governance

Effective cloud resource governance relies on three core components: a continuously synchronized inventory of all resources, policies that prevent the deployment of resources without assigned owner tags, and a robust audit trail that persists through organizational changes. These pillars ensure accountability and visibility over the cloud infrastructure.

Identifying Resources Without Owners

The article suggests using existing tools like queries, policies, and logs to address the issue. Specifically, it demonstrates how to use SQL queries with tools like CloudQuery to identify resources across AWS, GCP, and Azure that lack an 'owner' tag. This allows teams to generate a list of unowned resources, providing a clear starting point for assigning accountability.

Preventing Future Orphaned Resources

By regularly running these queries, organizations can proactively manage their cloud assets. This approach helps avoid last-minute scrambles to identify resource owners when cost issues arise, ensuring that every deployed resource has a clear point of contact and accountability.