Tag Compliance

Why Tags Matter

Cloud resources have technical names like "vol-0a1b2c3d" or "nic-westeurope-042" that mean nothing to a manager looking at a cost report. Tags are labels your team adds to resources so costs can be attributed to things the business cares about — projects, products, environments, and owners.

Without tags, you know how much you're spending, but not on what or for whom. That makes it hard to set budgets, identify waste, or hold teams accountable.

Recommended Tags

Project / Product

Examples: "Mobile App", "Customer Portal", "Data Pipeline". Maps every dollar to something on your roadmap. This is the single most impactful tag — start here.

Environment

Examples: "production", "staging", "development", "test". Know instantly how much you're spending on non-production. A common finding: dev/test environments costing as much as production.

Owner / Team

Examples: "platform-team", "jane.smith@company.com". When a resource looks wasteful, you know who to ask about it.

Cost Centre (optional)

For internal chargebacks or finance reporting. Maps cloud spend directly to your accounting structure.

What Scamallteoir Does

Once you set required tags in Settings, Scamallteoir does two things:

1. Tag compliance scanning — every sync checks your inventoried resources. Anything missing a required tag appears on the Cost Bleed page under "Tag Compliance", showing exactly which tags are missing.
2. Cost-by-tag grouping — the Dashboard gains a "By Tag" chart view. Select a required tag (e.g. "project") and see a stacked bar chart breaking down daily costs by tag value. Instantly answer "how much does Project X cost?"

Tag matching is case-insensitive — a resource tagged "project" satisfies a requirement for "Project".

Exporting & Sharing

Both waste findings and tag compliance findings can be exported as CSV files from the Cost Bleed page. Click the "Export CSV" button at the top of each table to download a spreadsheet you can share with your team or import into Excel / Google Sheets.

Each resource name also has a copy icon (📋) — click it to copy the name to your clipboard so you can quickly paste it into a ticket or Slack message when tasking an engineer.

How to Fix Findings

Each finding links directly to the resource in AWS or Azure. Click through, add the missing tags, and the finding resolves automatically on the next scan. No manual dismissal needed.

Tips for Rolling Out Tagging

• Start with just one required tag (Project) — don't overwhelm the team with five tags on day one.
• Add an Environment tag next — it's the fastest way to spot dev/test waste.
• AWS: Use Tag Policies in AWS Organizations to enforce tags at the source, preventing untagged resources from being created.
• Azure: Use Azure Policy to require tags on resource creation.