Mandate Resource Tagging for Governance
Specification & Description
Combine AWS Organizations Tag Policies, Service Control Policies (SCPs), and AWS Config required-tags rules to enforce mandatory tag keys and standardized tag values across landing zone workloads.
Technical Specifications
SCPs do not have a report-only mode; once attached, a Deny SCP immediately blocks non-compliant API calls. Pre-enforcement auditing and rollout use three complementary layers. First, AWS Organizations Tag Policies (TAG_POLICY) standardize tag key casing and allowed values, supporting non-blocking compliance reporting before you enable enforced_for on specific resource types. Second, AWS Config REQUIRED_TAGS detects existing or out-of-band untagged resources. Third, an SCP using Null on aws:RequestTag/KeyName blocks resource creation when mandatory tags are absent. When gating ec2:RunInstances in an SCP, scope the Resource array to instance and volume ARNs rather than a wildcard because referenced VPC, subnet, image, and security group ARNs do not carry request tags.
Security Rationale
Consistent tagging drives cost allocation, owner accountability, automated incident routing, and attribute-based access control (ABAC). Enforcing tag standards at creation time avoids expensive retroactive tagging across thousands of resources.
Business & Security Impact
Missing or inconsistent tags break FinOps chargeback, hide resource ownership during security incidents, and weaken ABAC boundaries. Scoping an ec2:RunInstances tagging SCP to Resource '*' blocks valid tagged launches whenever referenced VPC or AMI sub-resources lack request tags.
Operational & Implementation Notes
Some creation APIs (such as s3:CreateBucket) do not evaluate aws:RequestTag condition keys in SCPs. Use Tag Policies with s3:bucket in enforced_for and AWS Config REQUIRED_TAGS to cover S3 buckets and pre-existing resources.
Related Controls & Guardrails (3)
Compliance Framework Mappings (4)
Regulatory baselines and industry standards mapped to this control specification.
| Framework / Standard | Mapped Requirements & Controls | Controls |
|---|---|---|
NIST 800-53 Rev 5NIST 800-53 | CM-8CM-2AC-3 | 3 |
ISO 27001:2022ISO 27001 | A.5.9A.5.12A.8.9 | 3 |
PCI DSS v4.0PCI DSS | 2.2.1 | 1 |
SOC 2SOC 2 | CC6.1CC8.1 | 2 |
* Compliance framework mappings are provided for informational architectural reference. Always verify control alignment against your organization's formal audit requirements.
Automated Detection & Rule Logic
Detection Engine: aws-api • Automated: Yes
Inspect both SERVICE_CONTROL_POLICY and TAG_POLICY policies and their targets in AWS Organizations, query Resource Groups Tagging API get-compliance-summary from the Management account in us-east-1 alongside list-required-tags, and verify AWS Config required-tags rules are active. Required IAM permissions: organizations:ListPolicies, organizations:DescribePolicy, organizations:ListTargetsForPolicy, tag:GetComplianceSummary, tag:ListRequiredTags, and config:DescribeConfigRules.
Remediation Guide & Automation
Define a canonical tag schema, deploy AWS Organizations Tag Policies and AWS Config required-tags rules first to audit non-compliant workloads without blocking, and then attach an aws:RequestTag Deny SCP to target workload OUs with properly scoped EC2 instance and volume ARNs. Required IAM permissions: organizations:ListRoots, organizations:EnablePolicyType, organizations:CreatePolicy, organizations:ListOrganizationalUnitsForParent, organizations:AttachPolicy, and config:PutConfigRule.
Step-by-Step Instructions
- Define mandatory tag keys (such as CostCenter, Owner, and Environment) and allowed values.
- Enable TAG_POLICY on the Organization Root and attach a Tag Policy without enforced_for first to collect baseline compliance metrics.
- Deploy the AWS Config REQUIRED_TAGS managed rule across member accounts to flag existing untagged resources.
- Enable enforced_for in the Tag Policy for supported resource types once teams remediate legacy drift.
- Attach the tag-presence Deny SCP (scoping ec2:RunInstances to instance/* and volume/* ARNs) to a sandbox OU, validate IaC templates, and promote to workload OUs.