Cost Allocation Tagging on AWS: How to Know What Everything Costs and Who Owns It

Most engineering organisations that complain about cloud cost visibility don't have a cost problem — they have a tagging problem. Without consistent tags, Cost Explorer shows total spend by AWS service but can't tell you which team, which project, or which environment is responsible. Cost allocation tagging solves this.

The Minimum Viable Tag Set

Four tags cover most cost attribution requirements:

• team: Which engineering team owns this resource (payments, identity, data, platform)
• environment: dev, staging, production
• project: The specific project or product this resource serves
• cost-centre: The billing unit or business unit (important for larger organisations)

These four tags enable: cost breakdown by team, by environment across all teams, by project, and by business unit. Add a managed-by tag (quickinfra, terraform, manual) to identify how resources were created.

AWS Cost Allocation Tags

AWS has a two-step tagging process: you apply tags to resources (which anyone can do), and you activate tags for cost allocation in the Billing console (which only an account admin can do). Tags that aren't activated don't appear in Cost Explorer groupings.

QuickInfra includes a setup guide that walks through activating the standard tag set for cost allocation in your AWS accounts.

Enforcing Tags With QuickInfra

QuickInfra enforces mandatory tags on all resources it provisions. You configure the required tag keys in Organisation Settings → Tagging Policy. Any Infrastructure Project or Pipeline that creates a resource must have values for all required tags — the project creation form validates this before generating Terraform.

The compliance scan flags untagged resources as findings, giving you visibility into resources created outside QuickInfra that don't have the required tags.

Cost Explorer With Tags

With consistent tagging, Cost Explorer becomes significantly more useful. Filter by team tag to see one team's total spend across all services and environments. Filter by environment + team to see what development environments are costing relative to production. Filter by project to see the total cost of a specific initiative including all the infrastructure it's using.

Chargeback and Showback

For organisations that internally charge cloud costs to business units, cost allocation tags enable chargeback: the finance team can use Cost Explorer tag groupings to produce monthly reports of cloud spend per business unit for internal billing.