> For the complete documentation index, see [llms.txt](https://help.aikido.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.aikido.dev/autofix-and-remediation/scope/autofix-for-infrastructure-as-code.md).

# AutoFix for Infrastructure as Code

AutoFix for Infrastructure as Code supports the following IaC tools:

* Terraform
* CloudFormation
* Serverless framework
* Docker
* Kubernetes
* Helm

AutoFix creates the patch for the IaC files, it **does not automatically apply** the changes to your cloud. The execution of the changes needs to be executed by the user.

On the [AutoFix > IaC](https://app.aikido.dev/issues/fix/iac) page in the Aikido UI, you will find the detected IaC issues. AutoFix can generate a preview of the change or create a Pull Request.

<figure><img src="https://3149773201-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyKbzcQGrx7UtrG0nPZZ7%2Fuploads%2FnW9vffCuNM6JvG7PE9cr%2Fimage.png?alt=media&amp;token=fc873e94-c0a4-42d3-b3f5-fead0e778604" alt=""><figcaption></figcaption></figure>

Clicking AutoFix will generate a preview of the change required to remediate the issue.

<figure><img src="https://3149773201-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyKbzcQGrx7UtrG0nPZZ7%2Fuploads%2F6yV96d6Qj81zfTkaXYj5%2Fimage.png?alt=media&amp;token=e3a98822-7979-48aa-89e1-b4425865cb02" alt=""><figcaption></figcaption></figure>

From here you can

* Create a Pull Request
* Apply the patch directly in your IDE
* Refine the solution with Aikido AI


---

# 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://help.aikido.dev/autofix-and-remediation/scope/autofix-for-infrastructure-as-code.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.