Missing Cost-Allocation Tags
Spend on this resource cannot be attributed to a team, product or environment, so it lands in an unallocated bucket nobody owns.
Free to start. No card. The playground just needs your work email.
AWSAzureGoogle CloudDatabricks
Found, explained, handed over.
Where the estate departs from your policies, frameworks and tagging rules.
Detect
ZopNight checks this automatically across AWS, Azure and Google Cloud, with read-only access to the account.
Explain
Every finding says exactly what to change: Add cost-allocation tags to the cluster.
Fix
The finding opens with the fix already written out, step by step, so it is one ticket, not an investigation.
- Applies to
- Databricks Cluster on AWS, Databricks Job on AWS, Databricks SQL Warehouse on AWS, Databricks Cluster on Azure, Databricks Job on Azure, Databricks SQL Warehouse on Azure, Databricks Cluster on Google Cloud, Databricks Job on Google Cloud, Databricks SQL Warehouse on Google Cloud
- The fix, by hand on AWS
- Add the missing custom tags to the cluster.
- Enforce required tags via a cluster policy.
These are the steps the finding carries in the product.
- Category
- Governance. Missing tags and labels that break cost attribution, such as no environment, team or cost-centre value.
- Where it appears
- The Compliance tab of Recommendations, with every affected resource listed.
- Rule IDs
RC-2220RC-2221RC-2222RC-2320RC-2321RC-2322RC-2420RC-2421RC-2422- Full reference
Cluster Missing Cost-Allocation Tags SQL Warehouse Missing Cost-Allocation Tags Job Missing Cost-Allocation Tags
Related checks
See the governance findings in your account.
Connect a read-only role and the first pass runs on your own estate. This check, and the rest of the catalogue, with it.
Prefer to talk it through first? Book 20 minutes with the team.
- $30M+annualised cloud spend under management
- 550K+resources tracked since launch
- 20-60%off the bill in the first month
- SOC 2Type II report, plus ISO 27001
Figures published on zop.dev.