resource tag
A key and value label, such as Role=web or Environment=production, attached to a cloud resource to describe it.
In more detail
Tags let people and tools find, group and bill resources by purpose, owner or environment. They only help if everyone applies them consistently.
Examples
Ansible inventory plugins can filter instances by tag and turn tag values into groups with keyed_groups.In AWS: A key and value label, such as Owner=finance-platform, attached to an AWS resource so it can be grouped, reported on and controlled.Name=invoice-workerOwner=finance-platformEnvironment=productionCostCenter=FIN-042ManagedBy=terraformtags = { Owner = "platform", Team = "orders" }In Terraform: Tags drive cost reports, ownership and cleanup, so teams usually require some on every resource and check for them with policy. In Terraform tags are a map argument, often built with merge() so every resource gets the standard set.data_classification=restricted on a database, checked by a plan guardrailRelated terms
- keyed group — An inventory plugin setting that creates one group for each distinct value of a host attribute, named from a prefix and the value.
- aws_ec2 inventory plugin — The inventory plugin from the amazon.aws collection that lists EC2 instances in an AWS account as Ansible hosts.
- Amazon EC2 — Amazon Elastic Compute Cloud, the AWS service that rents out virtual servers called instances.
- tag policy — A rule listing which tags resources must have and which values are allowed, checked before or after deployment.
- cost allocation — Assigning each cloud charge to the team, product or cost centre responsible for it.
- AWS Budgets — An AWS billing feature that compares actual or forecast spend with an amount you set and alerts people when it crosses a threshold.
- attribute-based access control — An authorization model that decides each request from attributes of the subject, the resource and the environment, such as owner, department or time of day.
- data classification — Labelling data by how sensitive it is, such as public, confidential or restricted, so the right controls are applied.
- merge() — The function that combines several maps into one, with keys in later maps winning over earlier ones.
- policy as code — Writing organisational rules, such as required tags or allowed regions, as code that automatically checks every proposed change.
Taught in
- Dynamic Inventory — Ansible Configuration Management at Scale
- CodePipeline: Stages, Actions And The Key Nobody Shared — AWS Certified DevOps Engineer – Professional (DOP-C02) Exam Prep
- Artifacts: Where Packages And Images Live, And Die — AWS Certified DevOps Engineer – Professional (DOP-C02) Exam Prep
- Testing Resilience: The Experiment That Would Have Been The Outage — AWS Certified DevOps Engineer – Professional (DOP-C02) Exam Prep
- Collecting Logs And Metrics: The Disk Nobody Measured — AWS Certified DevOps Engineer – Professional (DOP-C02) Exam Prep
- Identity At Scale: The Boundary That Blocked The Admin — AWS Certified DevOps Engineer – Professional (DOP-C02) Exam Prep
- Security Hub, GuardDuty And Inspector: Signal, Noise And Response — AWS Certified DevOps Engineer – Professional (DOP-C02) Exam Prep
- Monday, Five Tickets — Microsoft Azure Administrator (AZ-104) Exam Prep
- A Storage Account In The Wrong Country: Azure Policy — Microsoft Azure Administrator (AZ-104) Exam Prep
- The Deleted IP Address: Locks, Tags, Groups And Subscriptions — Microsoft Azure Administrator (AZ-104) Exam Prep
- Three Weeks Before Anyone Noticed: Budgets, Alerts And Advisor — Microsoft Azure Administrator (AZ-104) Exam Prep
- Old X-Rays At Hot Prices: Tiers, Lifecycle Rules And Undelete — Microsoft Azure Administrator (AZ-104) Exam Prep
- The Server Nobody Could Rebuild: ARM Templates And Bicep — Microsoft Azure Administrator (AZ-104) Exam Prep
- What Drives An Azure Bill — Microsoft Azure Fundamentals (AZ-900) Exam Prep
- Governance: Policy, Locks And Purview — Microsoft Azure Fundamentals (AZ-900) Exam Prep
- Managing And Deploying Resources — Microsoft Azure Fundamentals (AZ-900) Exam Prep
- Governance Decision Drill — Microsoft Azure Fundamentals (AZ-900) Exam Prep
- Look-Alike Services Sprint — Microsoft Azure Fundamentals (AZ-900) Exam Prep
- Full Mock And Review — Microsoft Azure Fundamentals (AZ-900) Exam Prep
- Policy Simulation and Dry Runs — Cloud Infrastructure & Hyperscaler Architecture
- Elastic Compute Cloud (EC2) — Cloud Infrastructure & Hyperscaler Architecture
- Cost, Budgets, and Tagging — Cloud Infrastructure & Hyperscaler Architecture
- Infrastructure as Code (Handover to Terraform) — Cloud Infrastructure & Hyperscaler Architecture
- Cloud IAM Architecture & Permission Boundaries — Cloud Security & DevSecOps Engineering
- Supply Chain Security: SBOMs & Cosign Signing — Cloud Security & DevSecOps Engineering
- Enforcing OPA Guardrails on Terraform Plan Payloads — Cloud Security & DevSecOps Engineering
- Cloud Security Posture Management & Remediation — Cloud Security & DevSecOps Engineering
- What Is Infrastructure As Code? — Infrastructure as Code with Terraform
- Parameterising With Input Variables — Infrastructure as Code with Terraform
- Return Values: Outputs And Locals — Infrastructure as Code with Terraform
- Functions And Expressions In HCL — Infrastructure as Code with Terraform
- Writing A Custom Network Module — Infrastructure as Code with Terraform
- Policy As Code With OPA — Infrastructure as Code with Terraform
- Runs In HCP Terraform: The cloud Block And Remote Execution — HashiCorp Terraform Associate (004) Exam Prep
References
- AWS: tagging your AWS resources
- Organizing and tracking costs using cost allocation tags
- AWS: tagging best practices