Activate repo cost allocation tag

[Alexanderamiri]

Summary

• Add repo to active cost allocation tags in Cost Explorer
• Already present on resources via default_tags, just needs activation

Test plan

• Verify terraform plan shows 1 new aws_ce_cost_allocation_tag resource

[github-actions]

Terraform Plan

🚧 Changes detected — Plan: 1 to add, 0 to change, 0 to destroy.

Plan output

Acquiring state lock. This may take a few moments...

Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # module.monitoring.aws_ce_cost_allocation_tag.tags["repo"] will be created
  + resource "aws_ce_cost_allocation_tag" "tags" {
      + id      = (known after apply)
      + status  = "Active"
      + tag_key = "repo"
      + type    = (known after apply)
    }

Plan: 1 to add, 0 to change, 0 to destroy.

─────────────────────────────────────────────────────────────────────────────

Saved the plan to: tfplan

To perform exactly these actions, run the following command to apply:
    terraform apply "tfplan"

---

LLM Review

Risk: 🟢 LOW

Adding a new cost allocation tag for repository tracking with no modifications to existing infrastructure.

• ✅ [routine] Creating a single new AWS Cost Allocation Tag for 'repo' key to enable cost tracking by repository. This is a non-destructive, low-impact change.
• 💰 [cost] Cost allocation tags are a free AWS feature for organizing billing data. No new billable resources are being created.
• ✅ [routine] No existing resources are being modified or destroyed. The plan only adds one new tagging resource.
• ✅ [routine] Existing infrastructure (Lambda functions, ECS, networking, monitoring, IAM roles) remains unchanged. All resources are in stable state.
• ✅ [routine] This change aligns with the existing tagging strategy already in place (team, service, managed-by, environment tags are already active).