Cloud concept · Updated

Resource Tagging - Resource tagging is the practice of attaching key–value metadata to cloud resources so they can be organized, governed, automated, and associated with costs.

In short

Tags describe business and operational attributes such as ownership, department, cost center, application, and environment without changing a resource’s function. A consistent tagging strategy supports cost allocation and resource management, while policy controls help prevent missing, misleading, or unauthorized tags.

Cloud Concepts Hub →

6 key aspects of Resource Tagging

Effective tagging combines consistent metadata, explicit billing activation, logical grouping, and governance controls that account for security and coverage limits.

01
Consistent key–value metadata

Define stable keys such as Department, CostCenter, Environment, and Owner, with controlled values and capitalization. Consistency makes resource queries, billing reports, and automation predictable.

02
Explicit cost allocation activation

In AWS, activate relevant user-defined or AWS-generated tag keys for cost allocation before relying on them in billing analysis. Applying a resource tag alone does not make it an active billing dimension.

03
Logical resource grouping

Use shared tags to select resources across supported services for inventory and management. These groups describe business or operational relationships rather than creating isolation boundaries.

04
Policy-driven governance

Apply tags during provisioning and check for missing or invalid values afterward. Standardization policies, creation-time controls, and compliance detection serve different purposes and often need to be combined.

05
Controlled security attributes

Tags can participate in attribute-based access control where supported, but authorization still requires explicit policies. Restrict who can set or change tags that affect access or sensitive automation.

06
Coverage and propagation limits

Check tagging support and propagation behavior for each resource type rather than assuming inheritance. Track untagged spending and shared costs separately so reports do not imply complete allocation.

Cloud services for Resource Tagging

AWS Organizations establishes consistent tag conventions across accounts, while deployment workflows apply those tags to resources. AWS Config can detect missing or noncompliant tags, and IAM controls who may change them or use them in authorization decisions. AWS Resource Groups uses tags to assemble supported resources into management views. Separately, AWS Billing and Cost Management activates selected tag keys for financial use, making eligible tagged charges available for analysis in Cost Explorer and billing reports such as the AWS Cost and Usage Report. Together, these capabilities connect operational ownership with spending visibility without making tags an isolation boundary.

AWS Billing and Cost Management

Provides the controls for activating user-defined and AWS-generated cost allocation tag keys. Activated tags can support cost allocation in billing datasets, including the AWS Cost and Usage Report, subject to resource support and processing.

AWS Cost ExplorerAWS Cost Explorer

Uses activated cost allocation tags to filter and group eligible spending. Engineers can compare application or departmental costs and investigate charges that lack the expected allocation tags.

AWS OrganizationsAWS Organizations

Provides tag policies that standardize tag keys and values across accounts, with enforcement for supported resource types. Tag policies alone do not ensure that every resource has all required tags.

AWS ConfigAWS Config

Can evaluate recorded, supported resources for required tags using compliance rules. Detection identifies resources needing remediation but does not inherently prevent their creation or automatically correct their tags.

Resource Tagging exam questions

Real practice exam questions on Resource Tagging, with the correct answer and its explanation. Answer them with every option in the exam simulator.

CLF-C02

A company uses AWS Organizations. One application team tags its resources with CostCenter=Sales, and another team uses costcenter=Sales. Both tag keys are activated for cost allocation, but finance sees two separate tag dimensions in billing reports. The company wants future charges for these resources to appear under one consistent cost center tag dimension. Which solution meets this requirement?

Show answerCORRECT ANSWER

Standardize the resources on the activated CostCenter key, replacing costcenter where necessary, and allow billing data to update.

Tag keys are case-sensitive. Applying the same activated key consistently lets finance allocate future supported resource charges using one cost center dimension after processing.

MLA-C02 (beta)

An ML platform runs GPU-based training workers on Amazon EC2. Each project has its own Auto Scaling group and launch template in a shared AWS account. The Auto Scaling groups apply a Project tag to instances at launch. The Project cost allocation tag is already activated in AWS Billing and Cost Management.

In AWS Cost Explorer, instance charges appear under the correct projects, but charges for the workers' attached Amazon EBS volumes appear without a Project value. The report includes all services and usage types. Finance needs future instance and EBS volume charges attributed to the same projects without moving workloads or maintaining custom billing-data joins.

Which change should the ML engineer make?

Show answerCORRECT ANSWER

Keep the instance tagging configuration and add a volume tag specification with the appropriate Project value to each project's launch template. Update each Auto Scaling group to use the new template version.

EBS volumes do not automatically inherit instance tags. A launch template can specify tags for volumes created during instance launch. Applying the same activated Project key and project value to these volumes allows supported future volume charges to be allocated alongside instance charges after billing processing.

SAP-C03

A company uses AWS Organizations with all features enabled. Its member accounts host projects for different customers. Accounts in the same organizational unit (OU) can have different approved project codes, and accounts occasionally move between OUs.

Finance needs to group eligible resource charges by a user-defined ProjectCode tag in AWS Cost Explorer. The company has the following requirements:

• Every account, including a newly joined account before account-specific configuration runs, must inherit the exact tag key ProjectCode from a central standard.
• Policies attached below the organization root must not be able to change the tag key or its capitalization.
• Each account must have its own approved project-code values. Administrators must be able to replace that account's approved values without modifying the central policy or affecting other accounts.
• No project-code value must be approved organization-wide.

An existing account-provisioning workflow can attach an account-specific tag policy. Resource deployment workflows apply the required tags; preventing missing tags is outside the scope of this design.

Which solution meets these requirements?

Show answerCORRECT ANSWER

Attach a tag policy to the organization root that assigns the tag key ProjectCode and sets @@operators_allowed_for_child_policies to ["@@none"] for tag_key. Omit tag_value from the root policy. Attach a policy to each account that assigns its approved tag values. Activate ProjectCode as a user-defined cost allocation tag in the management account.

All accounts inherit a tag policy attached to the organization root, including accounts that do not yet have account-specific policies. Locking tag_key prevents child policies from changing ProjectCode, including its capitalization. Leaving tag_value undefined at the root allows each account policy to assign and subsequently replace its own approved values. Activating the key in the management account makes it available for organization-wide cost allocation reporting after processing.

Practice Resource Tagging in a full exam

Questions on Resource Tagging in each practice exam, with every answer option and an explanation for each:

Start a free practice exam

What is Resource Tagging

3 min read

Resource tagging adds structured metadata to cloud resources. A tag usually consists of a key and a value, such as Department=Finance, CostCenter=CC104, or Environment=Production. These attributes provide a business-oriented view of infrastructure that complements technical identifiers, accounts, subscriptions, and regions. One resource can have several tags, allowing it to participate in different management views without being moved or duplicated.

A practical tagging standard defines approved keys, allowed values, ownership, and the processes that maintain them. For example, an application team might apply Application=Payments, Owner=PaymentsPlatform, and Environment=Production to its compute instances, databases, and storage. Operations teams can then find related resources, investigate ownership, or target approved automation. Tags are generally case-sensitive, so Environment and environment can become separate keys and fragment reporting.

For financial management, tags connect eligible resource charges to departments, projects, or cost centers. In AWS, resource tags and cost allocation tags are related but are not interchangeable: applying a tag to a resource does not by itself make that tag available as a billing dimension. The relevant tag key must also be activated for cost allocation in AWS Billing and Cost Management. In an AWS Organizations consolidated-billing setup, the management account manages cost allocation tag activation.

AWS distinguishes user-defined cost allocation tags from AWS-generated cost allocation tags. User-defined tags are created by customers, such as CostCenter=CC104. AWS-generated tags use the reserved aws: prefix; aws:createdBy is one example where supported. Customers cannot create or modify tags using that reserved prefix. AWS-generated tags are not guaranteed to exist on every resource, and activation requirements still matter for billing use.

Once activated and processed, supported cost allocation tags can appear in billing analysis tools and tag-related fields in the AWS Cost and Usage Report. Engineers can aggregate eligible charges by CostCenter to produce departmental reports or configure tag-filtered budgets. Allow for processing delays, and do not assume that activation automatically populates all historical charges. Untagged resources, unsupported charges, and shared infrastructure require separate review or an explicit allocation method; tagging does not automatically divide a shared database bill among its consumers.

Tags also support operational grouping. For example, a tag-based resource group can identify supported resources with Department=Finance and Environment=Development. Automation can use that selection to schedule maintenance or stop development instances outside working hours. A group is a logical selection, not a network boundary or an authorization boundary, and support varies by resource type and management tool.

For security, attribute-based access control can compare resource, request, and principal tags when the service and action support the required conditions. However, a tag does not grant or deny access on its own. Permissions must explicitly use it, and changes to authorization-relevant tags must be restricted. Otherwise, someone who can change Department or Environment might alter which resources they can access or which automation affects them.

Apply tags through deployment templates and provisioning workflows, then check coverage continuously. Do not assume tags automatically propagate from accounts, networks, stacks, or parent resources to every child resource. AWS Organizations tag policies can standardize tag spelling and values and enforce compliance for supported resource types, but they do not, by themselves, require every resource to carry every desired tag. Use complementary creation controls and compliance checks where appropriate. Avoid secrets and sensitive personal data in tags because tag values can appear in inventory, billing, and operational systems.

Learn Resource Tagging in lessons

12 short lessons on Resource Tagging in 8 certification courses.

and 6 more lessons

Open the lessons