> 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/remediations.md).

# Remediations

## Overview

Visibility alone doesn’t reduce cloud costs or improve efficiency—action does. Remediation in OneLens helps you translate insights into impact by enabling direct, controlled resolution of cost leaks, policy violations, and inefficiencies.

Every recommendation or violation detected in OneLens can be addressed through structured remediation, helping you:

* **Accelerate savings** by instantly resolving unused or underutilized resources
* **Enforce compliance** without relying on manual intervention
* **Reduce operational burden** through repeatable and automated execution
* **Maintain control** with auditable, permission-aware actions

## Ways of Remediations

You can remediate in two powerful ways:

* [**Through Runbooks** ](https://docs.onelens.cloud/automate/remediations/remediations-runbooks.md)– Purpose-built, policy-driven scripts that let you act immediately or schedule safe, guided changes.
* **Terraform** – Infrastructure-as-Code-driven remediation for scalable, governed infrastructure correction.

With remediation, you don’t just identify the problem—you fix it, securely and at scale.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.onelens.cloud/automate/remediations.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
