> For the complete documentation index, see [llms.txt](https://docs.nuvens.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nuvens.cloud/architecture/resilence/infrastructure-as-code-iac.md).

# Infrastructure as Code (IaC)

If you require deploying WorkSpaces Manager using Infrastructure as Code (IaC), Nuvens would be delighted to assist. Some examples of IaC deployments include:

* Creation of required roles via individual CloudFormation templates
* Creation of required roles via Terraform
* Deployment of MS-SQL on RDS via Terraform
* Creation of a golden image or AMI for EC2 with the necessary WSM requirements using Packer
* Creation of a golden image or AMI for EC2 with WSM requirements using EC2 Image Builder (currently in progress)
* Deployment of a custom AMI with WSM on EC2 via Terraform
* Deployment of MS-SQL on RDS via CloudFormation (currently in progress)

We always recommend an end-to-end solution with a Git repository and pipelines to automate the process. We can also assist in customizing the architecture to meet your specific requirements. Additionally, we host a repository on our GitLab that includes examples of these setups.

{% embed url="<https://gitlab.com/nuvens-public>" %}


---

# 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.nuvens.cloud/architecture/resilence/infrastructure-as-code-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.
