AWS Tagging Strategy

Consistent tags enable allocation, alerts, and automated actions. FCAI relies on a few required tags to route insights and approvals.

Required tags

• Owner: Primary person or team email/slug
• Environment: prod | staging | dev | sandbox
• Application: Service/app name
• CostCenter (optional): Finance code for chargeback/showback

Apply tags at provisioning time via IaC and enforce with SCP/Config.

Best practices

• Enforce tags via IaC modules and CI policy checks.
• Propagate tags automatically to child resources (e.g., EBS from EC2, ASG to instances).
• Use AWS Tag Policies to restrict values; audit with AWS Config.
• Block creation when required tags are missing in production accounts.

Reporting

• Use Cost Allocation Tags (activate in billing) to enable CUR and Budgets by tag.
• FCAI dashboards slice spend and recommendations by Owner, Environment, and Application.

FCAI helps

• Tag compliance reports and backfill helpers.
• Alert routing and approvals based on Owner and Environment.
• Guardrails to prevent untagged resources in critical accounts.