# Windows Based Images

Create an EC2 instance from an Ortus BoxLang engine (Windows Server 2019) AMI (Amazon Machine Image). We have created several Windows-based images to deploy your BoxLang or CFML applications with Compat CFML BoxLang Module.

| Images                  | Status               |
| ----------------------- | -------------------- |
| BoxLang MiniServer      | :white\_check\_mark: |
| BoxLang with CommandBox | :white\_check\_mark: |

## Software and tools installed matrix

On every Windows based Cloud Server you will find software or tools to achieve best experience with our solutions. This software include:

| **Tool name**                     | **Version installed** | **BoxLang MiniServer**             | **BoxLang + CommandBox**              |
| --------------------------------- | --------------------- | ---------------------------------- | ------------------------------------- |
| CommandBox                        | latest                | :white\_check\_mark:               | :white\_check\_mark:                  |
| BoxLang runtime                   | latest                | :white\_check\_mark:(As OS binary) | :white\_check\_mark:(Into CommandBox) |
| BoxLang MiniServer (As OS binary) | latest                | :white\_check\_mark:               | :x:                                   |
| ColdBox Application               | latest                | :white\_check\_mark:               | :white\_check\_mark:                  |

Due these Cloud Servers are Windows Server 2019 based, you can follow this [link](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/microsoftwindowsserver.windowsserver?tab=Overview) to know more about base software running.

## Environment variables

| **Variable**             | **Default value** | **Description**                                      |
| ------------------------ | ----------------- | ---------------------------------------------------- |
| BOXLANG\_HOME            | `C:\boxlangHome`  | Directory where BoxLang place configs and modules    |
| COMMANDBOX\_HOME         | `C:\CommandBox`   | Directory where CommandBox place configs and modules |
| BOXLANG\_TARGET\_VERSION | `latest`          | BoxLang version installed and to be used for BoxLang |

## Default site

For every Windows based BoxLang Cloud Server a scheduled task is used to get up and running a Web Server on well know HTTP port 80/TCP. You can find this scheduled task as name **"Start ColdBox Sample Application"**, depending of the server flavor this can be started using BoxLang MiniServer or CommandBox. If you want to start your any custom site, you can update this task if need it, or just only place your custom site under `C:\inetpub\wwwroot` folder

| Server                  | Command execution                                                                                                  | Scheduled task name              |
| ----------------------- | ------------------------------------------------------------------------------------------------------------------ | -------------------------------- |
| BoxLang MiniServer      | `C:\boxlang\bin\boxlang-miniserver.bat --host 0.0.0.0 --port 80 --webroot C:\inetpub\wwwroot --rewrites index.cfm` | Start ColdBox Sample Application |
| BoxLang with CommandBox | `C:\box\box.exe -commandbox_home=C:/CommandBox server start serverConfigFile="C:\inetpub\wwwroot\server.json"`     | Start ColdBox Sample Application |

{% hint style="info" %}
If you only place your custom site under `C:\inetpub\wwwroot` remember to delete their content before in order to remove the sample ColdBox Application
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://cloud-servers.ortusbooks.com/aws/windows-based-images.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.