> For the complete documentation index, see [llms.txt](https://www.mlcompendium.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.mlcompendium.com/ai-engineering/full-stack-and-ops-1/infrastructure-as-code.md).

# Infrastructure As code

Cloud resources should be code, not clicks, so they can be reviewed, repeated, and rebuilt. The page starts with Terraform and how it compares with Ansible, then gives the beginner course that walks through it with labs.

The same notes are in [DevOps Courses](/ai-engineering/full-stack-and-ops-1/docker.md).

## Terraform

The first step is seeing Terraform build real infrastructure. [youtube course](https://www.youtube.com/watch?v=SLB_c_ayRMo) is freeCodeCamp.org's Terraform Course on automating your AWS cloud infrastructure. Terraform is often confused with configuration tools, and [Terraform vs Ansible](https://www.youtube.com/watch?v=n1zW_QHg8nY) is K21Academy's explanation of the difference between the two.

## Terraform course

After the overview, the hands-on path is a full course with exercises. [Terraform for beginners](https://www.youtube.com/watch?v=YcJ9IeukJL8) is KodeKloud's Terraform Tutorial for Beginners + Labs, a complete step-by-step guide.


---

# 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://www.mlcompendium.com/ai-engineering/full-stack-and-ops-1/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.