> For the complete documentation index, see [llms.txt](https://docs.aqua-cloud.io/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aqua-cloud.io/documentation/installation-for-on-premise/server-installation.md).

# Server Installation

Install aqua server on Windows using the IIS Installer.msi. Follow step-by-step setup for instance, email, license, and database options to complete your on-premise installation.

Please make sure, that you have all files available to install your aqua server.

* aqua for IIS Installer.msi
* license.lic

First, you must install the **aqua for IIS Installer.msi** on the Microsoft Windows server. In order to do so, double-click on the file.  

<figure><img src="http://aquawiki.andagon.com/pictures/drex_server_installation_custom.png" alt=""><figcaption></figcaption></figure>

Click Next. Choose the default path and click *Next.* &#x20;

<figure><img src="http://aquawiki.andagon.com/pictures/drex_server_installation_custom_2.png" alt=""><figcaption></figcaption></figure>

The next screen requires some configuration. &#x20;

<figure><img src="http://aquawiki.andagon.com/pictures/drex_server_installation_custom_3.png" alt=""><figcaption></figcaption></figure>

| **Instance name:**            | name of your aqua server                                                  |
| ----------------------------- | ------------------------------------------------------------------------- |
| **Notification mail address** | email address of the notification sender.                                 |
| **Notification mail host**    | host name of your mail server                                             |
| **Customer ID**               | this field may remain empty                                               |
| **License file**              | path to your local aqua license file                                      |
| **Database type**             | Choose your database type and deactivate the check box Configure database |

&#x20;Click on Next. Enter the required data according to your SQL-Instance. This data can also be changed afterwards. Click on *Next*, read the hints and click on *Next*. &#x20;

<figure><img src="http://aquawiki.andagon.com/pictures/drex_server_installation_custom_4.png" alt=""><figcaption></figcaption></figure>

The aqua server is being installed now. &#x20;

<figure><img src="http://aquawiki.andagon.com/pictures/drex_server_installation_custom_5.png" alt=""><figcaption></figcaption></figure>

Finally, you will receive the following message: &#x20;

<figure><img src="http://aquawiki.andagon.com/pictures/drex_server_installation_custom_6.png" alt=""><figcaption></figcaption></figure>

The aqua server has been successfully installed. The next step is to connect aqua to the corresponding database.\ <br>


---

# 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.aqua-cloud.io/documentation/installation-for-on-premise/server-installation.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.