> 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/install/alternate-deployment-options/deployment-from-shared-ami/shared-ami-amazon-machine-image.md).

# Shared AMI (Amazon Machine Image)

At this stage, you'll launch the custom AMI shared by Nuvens to deploy WorkSpaces Manager. The AMI is based on **Windows Server 2019** and includes two volumes:

* **C:\\** with 75GB of storage
* **D:\\** with 20GB of storage

When deploying WorkSpaces Manager from a shared AMI, ensure that you use the newly created **Security Group** and the appropriate **EC2 instance profile** with the correct policies attached. This setup will grant the instance the necessary permissions to interact with AWS services, while the Security Group ensures proper network access and security.

For a real-world example of how to deploy an AMI via **Terraform**, please check this repository below for guidance and best practices:

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


---

# 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/install/alternate-deployment-options/deployment-from-shared-ami/shared-ami-amazon-machine-image.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.
