Prioritize missing allocation tags by untagged spend

What

Prioritize missing cost-allocation tags by the spend attached to untagged resources.

Why

CLDBRN-AWS-TAGGING-1 finds resources without user-created tags, but a count treats a tiny test resource like an expensive production workload. Dollar-weighted evidence makes the finding useful for FinOps prioritization.

Details

• Add configuration for required allocation-tag keys and a minimum unallocated-spend threshold.
• Use Cost Explorer data to calculate current-month and recent full-month spend where each required tag is absent or empty.
• Group findings by account, service, and missing tag key, with affected spend and currency as evidence.
• Return diagnostics when a requested cost-allocation tag is not active or Cost Explorer cannot provide the dimension.
• Discovery only. Keep resource-level tagging hygiene and spend-level allocation coverage as separate rules.

Start by locating the implementation of CLDBRN-AWS-TAGGING-1 and the Cost Explorer integration. Trace how rule configuration and findings are represented, then define completion as spend-weighted grouping by account, service, and missing tag key, with thresholds, currency evidence, and diagnostics for inactive tags or unavailable dimensions.