Resource Ownership

Architecture

Establish clear resource ownership with standardized tags:

• Owner tag for team or individual responsibility
• Contact tag for escalation during incidents
• Application tag for service mapping
• Integration with PagerDuty, Slack, or ITSM tools

When to Use

This pattern is ideal when you need:

• Incident response ownership
• Resource lifecycle management
• Security incident attribution
• Orphan resource identification
• Compliance auditing

Implementation

module "ownership_tags" {
  source  = "registry.patterneddesigns.ca/standardnat/tagging-policy/aws"
  version = "1.1.0"

  required_tags = [
    "Owner",
    "Team",
    "Application",
    "Contact"
  ]

  default_tags = {
    ManagedBy = "terraform"
  }

  enforce_lowercase = true
}

Considerations

• Define ownership at team level for long-term stability
• Include escalation path in Contact tag
• Integrate with service catalog for automatic tagging
• Regular audits to identify unowned resources