Tagging Compliance
Track tag coverage across all monitored AWS accounts. Required tags: team, env, service, owner.
Fleet-wide tagged %
0%
Untagged spend MTD
$766.9K
Accounts below 80%
10
By account
MTD tag compliance derived from cost rows with null tag columns.
| Account | Owner | Resources | Tagged % | Untagged $/mo |
|---|---|---|---|---|
| — | 1 | 0% | $405.5K | |
| — | 1 | 0% | $182.5K | |
| — | 1 | 0% | $65.5K | |
| — | 1 | 0% | $35.6K | |
| — | 1 | 0% | $22.9K | |
| — | 1 | 0% | $15.2K | |
| — | 1 | 0% | $13.2K | |
| — | 1 | 0% | $10.5K | |
| — | 1 | 0% | $9.1K | |
| — | 1 | 0% | $6.9K |
Untagged resource drill-down
Click any account row to inspect untagged resources by ARN, type, age, and cost. One-click 'Create Jira' available via the Tagging Compliance agent.