|
| 1 | +--- |
| 2 | +title: AWS accounts tagging schema |
| 3 | +last_reviewed_on: 2025-09-09 |
| 4 | +review_in: 6 months |
| 5 | +--- |
| 6 | + |
| 7 | +# <%= current_page.data.title %> |
| 8 | + |
| 9 | +This policy defines the standards for applying metadata to AWS resources across the Cabinet Office. Consistent tagging is essential for cost tracking, security auditing, and automated resource management. |
| 10 | + |
| 11 | +## Core principles |
| 12 | + |
| 13 | +* **Standardisation**: use lowercase letters and hyphens for all tag keys (for example, `team-name`). |
| 14 | +* **Automation**: apply tags at the point of creation using Infrastructure as Code (Terraform or CloudFormation). |
| 15 | +* **Enforcement**: compliance is monitored via AWS Tag Policies and AWS Config rules. Untagged resources may be subject to automated isolation or shutdown. |
| 16 | + |
| 17 | +## Mandatory tags |
| 18 | + |
| 19 | +The [Request an AWS account](https://request-an-aws-account.platforms.cabinetoffice.gov.uk/) application automatically applies specific metadata tags to all resources in the AWS organisation level. These tags ensure every AWS account has the meta-data associated with the organisation's operational and financial needs. |
| 20 | + |
| 21 | +You cannot currently edit or manage these organisation tags. |
| 22 | + |
| 23 | +#### **Ownership and operational** |
| 24 | + |
| 25 | +* `account-name` |
| 26 | +* `description` |
| 27 | +* `organisation` |
| 28 | +* `team-name` |
| 29 | +* `team-email-address` |
| 30 | +* `team-lead-name` |
| 31 | +* `team-lead-email-address` |
| 32 | +* `team-lead-phone-number` |
| 33 | +* `team-lead-role` |
| 34 | +* `service-name` |
| 35 | + |
| 36 | +#### **Security and support** |
| 37 | + |
| 38 | +* `service-is-out-of-hours-support-provided` |
| 39 | +* `security-requested-alert-priority-level` |
| 40 | +* `security-critical-resources-description` |
| 41 | +* `security-does-account-hold-pii` |
| 42 | +* `security-does-account-hold-pci-data` |
| 43 | + |
| 44 | +#### **Billing** |
| 45 | + |
| 46 | +* `billing-cost-centre` |
| 47 | +* `billing-business-unit` |
| 48 | +* `billing-business-unit-subsection` |
| 49 | + |
| 50 | +## Conditional tags |
| 51 | + |
| 52 | +These tags are recommended to provide additional granularity for specific service support needs. |
| 53 | + |
| 54 | +* `out-of-hours-support-contact-name` |
| 55 | +* `out-of-hours-support-phone-number` |
| 56 | +* `out-of-hours-support-pagerduty-link` |
| 57 | +* `out-of-hours-support-email-address` |
| 58 | + |
| 59 | +#### References |
| 60 | + |
| 61 | +* [Tagging AWS resources \- The GDS Way](https://gds-way.digital.cabinet-office.gov.uk/manuals/aws-tagging.html#why-tag) |
| 62 | +* [Best Practices for Tagging AWS Resources \- Best Practices for Tagging AWS Resources](https://docs.aws.amazon.com/whitepapers/latest/tagging-best-practices/tagging-best-practices.html) |
| 63 | +* [Best practices and strategies \- Tagging AWS Resources and Tag Editor](https://docs.aws.amazon.com/tag-editor/latest/userguide/best-practices-and-strats.html) |
| 64 | +* [Tagging categories \- Tagging AWS Resources and Tag Editor](https://docs.aws.amazon.com/tag-editor/latest/userguide/tag-categories.html) |
0 commit comments