How do you perform role tagging in your DevOps practice?

When tagging roles, I use the following principles and approaches:

• Standardization: I define a set of standard tags for roles.
• Automation: I apply tags in Infrastructure as Code (IaC).
• Lifecycle: Tags reflect the state of the role (development, testing, production).
• Security: Tags are used for access control and policies.

Examples of standard tags:

Tag	Value	Description
Project	project-name	Project affiliation
Environment	dev / test / prod	Deployment environment
Service	service-name	Service/component name
Owner	team-name / user-id	Team or user responsible for the role
CostCenter	costcenter-id	Cost center for financial reporting

Example of usage in Terraform:

resource "aws_iam_role" "app_server_role" {
  name = "app-server-role-prod"

  assume_role_policy = jsonencode({
    Version = "2012-10-17"
    Statement = [
      {
        Action = "sts:AssumeRole"
        Effect = "Allow"
        Principal = {
          Service = "ec2.amazonaws.com"
        }
      },
    ]
  })

  tags = {
    Project     = "MyApp"
    Environment = "prod"
    Service     = "AppServer"
    Owner       = "BackendTeam"
  }
}

Tagging allows:

• Easily identify the resource and its purpose.
• Group resources for management and monitoring.
• Apply security policies and network rules.
• Conduct cost analysis by projects/services.
• Improve organization and resource search.