> 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/licenses.md).

# Licenses

Easily install or update your aqua licenses by copying files to the Licenses folder. Learn version requirements and troubleshooting steps for on-premise aqua environments.

If you receive new aqua licenses, it is very easy to install them into your aqua environment.&#x20;

You only have to copy them into the following folder on aqua server\
\
`C:\Program Files\andagon GmbH\aqua For IIS\aqua\Licenses`&#x20;

{% hint style="warning" %}
**Please do not delete any existing ones!**
{% endhint %}

The aqua server will read these licenses automatically. If this is not working (or if it takes too long), you can simply restart the **`aquaWebservicePool`** in the **`IIS-Manager`**.&#x20;

Licenses always refer to a major aqua version, e.g. 21.x or 22.x. This means that if you update from aqua 21.2.2 to 22.6.3 you will receive new licenses which you must install with the update. When updating to a minor version, e.g. aqua 22.6.3 to 22.20.0, the existing licences are still valid and don't have to be updated.


---

# 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/licenses.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.
