skills.rest
masermediagroup-stack
masermediagroup-stackCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

resource-tagging

Implement and enforce cloud resource tagging policies across AWS, Azure, GCP, and Kubernetes.

1|Updated Feb 24, 2026
Search Tags:#aws#gcp#azure#governance#finops#cost allocation#cloud tagging
One-click install
npx skills add https://github.com/masermediagroup-stack/maser-media --skill resource-tagging-masermediagroup-stack
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: resource-tagging
Source: https://github.com/masermediagroup-stack/maser-media/tree/main/.cursor/skills/community/ai-design-components/skills/resource-tagging
Command: npx skills add https://github.com/masermediagroup-stack/maser-media --skill resource-tagging-masermediagroup-stack

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires boto3, azure-mgmt-resource, azure-identity, google-cloud-asset, tabulate, and includes scripts (resource) and references (resource) components.

What problem does it solve? Untagged cloud resources make costs untrackable, ownership unclear, and compliance audits painful—often leaving 35% of cloud spend unallocated. This Skill provides a complete tagging strategy with enforcement policies, audit scripts, and cost allocation setup across AWS, Azure, GCP, and Kubernetes. ## Core Features & Use Cases - Tagging Standards: Defines the "Big Six" required tags (Name, Environment, Owner, CostCenter, Project, ManagedBy) with naming conventions and provider-specific limits. - Policy Enforcement: Implements hard and soft enforcement via AWS Config rules, Azure Policy, GCP Organization Policies, and OPA Gatekeeper/Kyverno for Kubernetes. - Compliance Auditing: Ships a multi-cloud Python audit script plus SQL/KQL queries to find untagged resources and generate compliance reports. - Cost Allocation: Activates cost allocation tags, sets up budgets and anomaly detection per project or team, and enables showback/chargeback reporting. - Use Case: A FinOps team needs to reduce unallocated spend. Use this Skill to define required tags, deploy Terraform default_tags, enforce tagging with AWS Config rules, and run weekly audits to reach 95%+ compliance. ## Quick Start Ask the AI to define a tagging standard with the Big Six required tags and generate Terraform default_tags plus an AWS Config rule to enforce them.

Frequently Asked Questions about resource-tagging

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce required tags on AWS resources?▼

Use AWS Config rules with the REQUIRED_TAGS managed rule to detect non-compliant resources, or apply Service Control Policies to deny resource creation when required tags are missing. Terraform provider default_tags apply tags automatically at creation time.

What tags should every cloud resource have?▼

Start with the Big Six: Name, Environment, Owner, CostCenter, Project, and ManagedBy. These cover identification, lifecycle stage, ownership, cost allocation, and provisioning method. Add optional tags like Backup, Compliance, or SLA only when a clear use case exists.

How do I track cloud costs by project or team?▼

Activate cost allocation tags in AWS Cost Explorer, Azure Cost Management, or GCP Billing export, then group costs by Project, Owner, or CostCenter tags. For Kubernetes, use Kubecost or OpenCost to allocate costs by namespace labels.

Does tagging work the same across AWS, Azure, and GCP?▼

No. AWS tags are case-sensitive with 50 tags per resource, Azure tags are case-insensitive, and GCP requires lowercase labels limited to 63 characters. Choose one naming convention organization-wide and enforce it through IaC and tag policies.

How do I find untagged resources in my cloud accounts?▼

Run the included audit_tags.py script against AWS, Azure, or GCP, or use native queries: AWS Config advanced SQL queries, Azure Resource Graph KQL, or gcloud asset search-all-resources. Weekly audits are recommended to catch tag drift.

Should I use hard or soft tag enforcement?▼

Start with soft enforcement (alerts only) for 30-90 days to measure baseline compliance, then move cost allocation tags like Owner and CostCenter to hard enforcement that denies untagged resource creation. Test deny policies in a sandbox account first.

Related Skills

Explore More Software Engineering Skills→
oborchersoborchers
28

naming-and-labeling-as-code

Enforce standardized naming and mandatory tagging for cloud resources via Terraform.

Community
Advanced
mahg-esmahg-es
3

usage-metering

Collect and normalize cloud resource usage data for cost attribution.

Official
Intermediate
devkenidevkeni
1

iac-security

Scan Infrastructure as Code for security misconfigurations using Checkov, tfsec, and Trivy.

Community
Intermediate
ChrstprJohnChrstprJohn

hybrid-cloud-architect

Architect and govern multi-cloud infrastructure across AWS, Azure, GCP, OpenStack, VMware, and edge.

Community
Advanced