> For the complete documentation index, see [llms.txt](https://help.dragen.illumina.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.dragen.illumina.com/dragen-v4.6/reference/licensing/cloud_licensing.md).

# Legacy DRAGEN Cloud Licensing

{% hint style="warning" %}
This page describes the **legacy** licensing system for Bring-Your-Own-License (BYOL) cloud runs, which authenticates with an Illumina-issued alphanumeric username and password. Usage is metered in gigabases against a prepaid quota that is separate from your BioInsight Credit balance, on every DRAGEN version including 4.6.

New BYOL deployments should use an Illumina BioInsight Platform API key instead. See [BioInsight Platform Licensing](/dragen-v4.6/reference/licensing/api_key_licensing.md).
{% endhint %}

Credential based authentication is required for users that run DRAGEN on the cloud with the legacy Bring-Your-Own-License (BYOL) model. DRAGEN must have access to the DRAGEN License server at runtime, license.dragen.illumina.com.

DRAGEN also authenticates cloud runs with the instance identity document from the cloud provider's instance metadata service. See Instance Identity for [AWS](/dragen-v4.6/reference/dragen-multi-cloud/dragen-on-aws.md#instance-identity) or [Azure](/dragen-v4.6/reference/dragen-multi-cloud/dragen-on-azure.md#instance-identity).

To verify connectivity to the license server, you can query the healthcheck endpoint which will return a 200 status code and a small JSON body if successful.

```
curl https://license.dragen.illumina.com/healthcheck/version --header 'Content-Type: application/json'
{"version":"<server version>"}
```

## Running DRAGEN Cloud BYOL with Credential Licensing

BYOL users must provide credentials to DRAGEN at runtime, using one of two options.

### Providing Credentials via License Credentials File

The suggested method for specifying your credentials is through a file passed in to DRAGEN at runtime. The file can be pointed to using the option `--lic-credentials <path to file>` or an environment variable containing the path to this file, `DRAGEN_LICENSE_CREDENTIALS_FILE`. This method provides a more secure way to pass credentials, which avoids accidental credentials leaks from command line console logs.

The License Credentials File should be formatted as follows;

```
credentials-1=<username>
credentials-2=<password>
```

{% hint style="warning" %}
**Version requirements**:

* `--lic-credentials` requires **DRAGEN 4.2 or higher**.
* The `DRAGEN_LICENSE_CREDENTIALS_FILE` environment variable requires **DRAGEN 4.5 or higher**.
* **DRAGEN 4.5+ only**: An S3 path can be provided to retrieve the file so it does not need to reside on the local instance. See the Networked Streaming portion of the user guide for more information.
  {% endhint %}

{% hint style="warning" %}
**Default license server domain by version**: When using the License Credentials file, DRAGEN selects a default domain based on its version:

* **DRAGEN 4.4 and above**: `https://license.dragen.illumina.com`
* **DRAGEN 4.3 and earlier**: `https://license.edicogenome.com`

To override this behavior, add the `credentials-3` option to the credentials file. Do not specify the protocol (i.e. `https`).

```
credentials-3=license.dragen.illumina.com
```

{% endhint %}

### Providing Credentials via Command Line

Alternatively, you can simply provide your credentials over the command line using the option `--lic-server <license server URL with credentials>`.

The license server URL should be formatted as follows;

```
https://<username>:<password>@license.dragen.illumina.com
```

{% hint style="warning" %}
DRAGEN 4.6 prints a warning stating that the `--lic-server` option will be deprecated in future versions. Use a License Credentials File with `--lic-credentials` instead, which also keeps your password out of console logs.
{% endhint %}

## Retrieving License Information and usage using dragen\_lic

There are two options for retrieving information and usage for your licenses using the packaged dragen\_lic tool. Examples for each one are below.

{% hint style="warning" %}
**Version requirement**: Retrieving license information using the `dragen_lic` tool is only supported on **DRAGEN 4.4 and above**.
{% endhint %}

* Basic Output (i.e. no additional arguments). This is the recommended method to view license information by a human user as the output is more readable.
* JSON Output (i.e. using the -j flag). This is the recommended method to view license information by a machine user as the output is already in a machine readable JSON format.

**Note**: Just like running DRAGEN as noted above, you must specify your credentials using the `--lic-credentials` or `--lic-server` command line options.

```
$ dragen_lic --lic-credentials my_credentials.cfg
```

```
User: <username>
DRAGEN Version: <DRAGEN version>
Time: <time>

DRAGEN Core:
    Status: Active
    Used: 68.0 Gbases since 2023-Dec-05
    Quota: 100250 Gbases
    Expiry: 2024-Feb-13
    Includes; Genome, JointGenotype, CNV, Somatic, Transcriptome License(s)

Compression:
    Status: Active - !!! EXPIRING IN LESS THAN 30 DAYS !!!
    Used: 0 Gbases since 2024-Jan-12
    Quota: Unlimited
    Expiry: 2024-Feb-13
```

```
$ dragen_lic --lic-credentials my_credentials.cfg -j
```

```
{"dragen_boards":[{"user":"<username>","installed_licenses":{"Compression":[{"expiry":"2025-Mar-19","quota_limit":100250,"start":"2023-Dec-01","status":"Active","units":"Gbases","used":5223}],"TSO500Combined":[{"expiry":"2050-Jan-01","quota_limit":-1,"start":"2022-Jul-13","status":"Active","units":"Gbases","used":23518284}],"TSO500_HRD":[{"expiry":"2024-Feb-13","quota_limit":-1,"start":"2021-Oct-13","status":"Active","units":"Gbases","used":0}],"Dragen_Core":[{"expiry":"2024-Feb-13","includes":{"CNV":{"expiration":"2025-Mar-19","status":"Active"},"Genome":{"expiration":"2024-Feb-13","status":"Active"},"JointGenotype":{"expiration":"2025-Mar-19","status":"Active"},"Somatic":{"expiration":"2025-Mar-19","status":"Active"},"Transcriptome":{"expiration":"2025-Mar-19","status":"Active"}},"quota_limit":-1,"start":"2023-Oct-14","status":"Active","units":"Gbases","used":79708}]}}],"generated":"<ISO time>"}
```

## Retrieving License Information and usage using API endpoint

Alternatively, you can retrieve license information and usage using our License Server endpoint specified below without the use of DRAGEN. License information is returned in a JSON format.

GET request to <https://license.dragen.illumina.com/api/v2/query\\_quota>. Your user credentials must be provided as a Basic Authorization header. An example of this using the curl tool is shown below.

```
curl https://license.dragen.illumina.com/api/v2/query_quota --user <username>:<password>
```

```
{"user": "<username>", "credential_expiration": "<date>", "generated": "<date>", "licenses": [{"pipeline": "Compression", "start": "2024-12-02T00:00:00Z", "expiration": "2025-03-02T00:00:00Z", "quota_limit": 2.5, "usage": 0, "units": "Tbases"}, {"pipeline": "Genome", "start": "2024-12-02T00:00:00Z", "expiration": "2025-03-02T00:00:00Z", "quota_limit": 2.5, "usage": 0.727295399, "units": "Tbases"}], "per-pipeline-licenses": true, "message": "Active Licenses Found"}
```

## Run information collected

Run information is a key component of the DRAGEN Licensing infrastructure. For each individual run, the following information is collected by Illumina;

* date
* duration
* run status
* software version
* data quality
* licensing quota consumed (number of bases)
* instance identity


---

# 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 dynamically by asking a question.

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

```
GET https://help.dragen.illumina.com/dragen-v4.6/reference/licensing/cloud_licensing.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
