> For the complete documentation index, see [llms.txt](https://docs.onelens.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.onelens.cloud/automate/automated-tagging.md).

# Automated Tagging

### Overview

Automated Tagging enables organizations to apply and maintain consistent AWS resource tags at scale. It helps improve cost allocation, ownership tracking, governance, compliance, and FinOps reporting by automatically identifying resources that are missing required tags and applying approved tag values.

The feature uses AWS tagging APIs to discover resources across supported services and perform bulk tag updates without requiring manual intervention.

***

### Benefits

* Improve cloud cost allocation accuracy
* Increase tagging compliance across AWS accounts
* Reduce manual tagging effort
* Standardize tag values and naming conventions
* Enable department, product, application, and cost-center reporting
* Support FinOps, governance, and chargeback/showback initiatives

***

### Prerequisites

Before enabling Automated Tagging:

1. [Configure AWS access with the required tagging permissions.](/automate/automated-tagging/aws-iam-permissions.md)
2. Define the tag keys that should be enforced.
3. Identify approved tag values and ownership mappings.
4. Review resources that will be included in tagging automation.

Common examples of required tags include:

* Department
* Product
* Cost Center
* Environment
* Application
* Team
* Owner

***

### How Automated Tagging Works

#### Step 1: Resource Discovery

The system scans AWS accounts and discovers supported resources using AWS tagging APIs.

During discovery, the system identifies:

* Untagged resources
* Partially tagged resources
* Resources with invalid or inconsistent tag values
* Resources that do not meet tagging policies

***

#### Step 2: Tag Coverage Analysis

Discovered resources are analyzed against configured tagging requirements.

The analysis determines:

* Which resources are compliant
* Which tags are missing
* Existing tag values
* Resource coverage statistics

This provides visibility into current tagging compliance before any changes are made.

***

#### Step 3: Tag Mapping

Tag values can be mapped using one or more methods:

**Manual Mapping**

Users provide tag values directly for identified resources.

**Bulk Upload**

Tag mappings can be supplied through spreadsheets or bulk import templates.

**Rule-Based Mapping**

Tag values can be derived using predefined rules such as:

* AWS Account
* Resource Name
* Service Type
* Environment Pattern
* Existing Tags

Example:

| Condition                        | Apply Tag            |
| -------------------------------- | -------------------- |
| Account = Production             | Environment = Prod   |
| Resource Name contains "billing" | Department = Finance |

***

#### Step 4: Validation

Before tags are applied, the system validates:

* Required tag keys
* Allowed tag values
* Duplicate tags
* Invalid formats
* Tagging eligibility for each resource type

Validation helps prevent inconsistent tagging across the environment.

***

#### Step 5: Automated Tag Application

After validation, tags are applied automatically to supported AWS resources.

The automation process:

* Adds missing tags
* Updates configured tag values
* Preserves existing tags when applicable
* Processes resources in bulk
* Records tagging activity for audit purposes

***

#### Step 6: Compliance Monitoring

After tagging is completed, the system continuously monitors resources for compliance.

Monitoring includes:

* Tagging coverage percentage
* Newly discovered untagged resources
* Missing mandatory tags
* Invalid tag values
* Compliance trends over time

***

### Supported Operations

Automated Tagging supports:

#### Add Tags

Apply new tags to resources that do not currently have them.

#### Update Tags

Modify existing tag values to align with organizational standards.

#### Remove Tags

Remove obsolete or deprecated tags when required.

#### Bulk Tagging

Apply tags across multiple resources and AWS services in a single operation.

***

### Best Practices

* Define a standard tagging strategy before enabling automation.
* Limit allowed tag values where possible.
* Use consistent naming conventions.
* Prioritize high-cost resources for initial tagging efforts.
* Review compliance reports regularly.
* Automate tagging for newly discovered resources.
* Maintain ownership mappings for business-critical resources.

***

### Expected Outcomes

After implementing Automated Tagging, organizations typically achieve:

* Higher tagging compliance across AWS environments
* Improved visibility into cloud spending
* Better resource ownership tracking
* Simplified governance and reporting
* Reduced operational effort for tag management
* More accurate FinOps and unit-cost analysis


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.onelens.cloud/automate/automated-tagging.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.