// Definition
Cloud resource tagging is the practice of attaching key-value metadata to cloud resources at creation — for example, Team: payments, Environment: production, CostCenter: CC-421. Tags are the technical foundation for cost allocation, showback, chargeback, and governance. Without consistent tagging, costs can't be attributed to the teams or products that generated them.
// Why It Matters
The standard minimum tag set for FinOps: Team, Environment (prod/staging/dev), CostCenter, Product or Project, and Owner (person responsible). Tags must be enforced at resource creation via AWS Tag Policies, Azure Policy, or GCP Organization Policies — retrospective tagging of existing resources is slow, error-prone, and never reaches complete coverage.
Target: 90%+ of cloud spend tagged before implementing showback, 95%+ before implementing chargeback. Untagged spend must be handled explicitly — either absorbed centrally or distributed proportionally — and the methodology published to prevent disputes.
// In Practice
Example: A resource tagged Team: data-platform, Environment: prod, CostCenter: CC-112, Product: analytics-pipeline can be filtered in Cost Explorer, included in the data-platform team's monthly showback report, and charged to cost center CC-112 in a chargeback model — automatically, without manual intervention.