> For the complete documentation index, see [llms.txt](https://docs.snyk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snyk.io/scan-fix-and-prevent/scan-with-snyk/snyk-iac.md).

# Snyk IaC

How Snyk IaC finds and fixes misconfigurations in infrastructure as code

With Snyk Infrastructure as Code (IaC), you can secure cloud infrastructure configurations before and after deployment.

With Snyk IaC, you can:

* Write secure configurations for [HashiCorp Terraform](/scan-fix-and-prevent/scan-with-snyk/snyk-iac/scan-your-iac-source-code/scan-terraform-files.md), [AWS CloudFormation](/scan-fix-and-prevent/scan-with-snyk/snyk-iac/scan-your-iac-source-code/scan-cloudformation-files.md), [Kubernetes](/scan-fix-and-prevent/scan-with-snyk/snyk-iac/scan-your-iac-source-code/scan-kubernetes-configuration-files.md), and [Azure Resource Manager (ARM)](/scan-fix-and-prevent/scan-with-snyk/snyk-iac/scan-your-iac-source-code/scan-arm-configuration-files.md) - for IDE, SCM, CLI, and Terraform Cloud/Enterprise workflows.
* View issues and receive [fix advice](/scan-fix-and-prevent/scan-with-snyk/snyk-iac/getting-started-with-current-iac.md) so you can make changes directly to code, before applications reach production.
* [Detect manually created resources](/scan-fix-and-prevent/scan-with-snyk/snyk-iac/detect-manually-created-resources.md) in your cloud.
* Onboard, scan, and test deployed cloud environments for misconfigurations for AWS, Azure, and Google Cloud environments.

For a list of supported IaC languages and cloud providers, see [Supported IaC and cloud providers](/scan-fix-and-prevent/scan-with-snyk/snyk-iac/supported-iac-languages-cloud-providers-and-cloud-resources.md).


---

# 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.snyk.io/scan-fix-and-prevent/scan-with-snyk/snyk-iac.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.