---
title: "Dinamo key stores - Amplia"
description: "Configure Dinamo HSM key stores in Amplia: address and credentials, with an Operator user required for PIN-protected keys used with PSC."
canonical: "https://docs.lacunasoftware.com/en-us/articles/amplia/on-premises/key-stores/dinamo"
locale: "en"
product: "Amplia"
last_updated: "2026-10-12"
---

# Dinamo key stores - Amplia

> **Note**
>
> Dinamo key stores are compatible with all supported platforms

To store keys on a [Dinamo HSM](https://www.dinamonetworks.com/en/hardware-security-module-hsm/), use the following settings:

* **Type**: `Dinamo`
* **Address**: IP address or hostname of the HSM
* **User** and **Password**: credentials for an Operator or regular user (see below)

If you intend to use the HSM for storing CA keys, the credentials can be either for an Operator or a regular user.

If you intend to use the HSM for storing PIN-protected keys, typically combined with [Lacuna's PSC module](https://docs.lacunasoftware.com/en-us/articles/psc), the credentials must be for an
**Operator** user.

Sample configuration (*.ini* or *.conf* file):

```ini
[KeyStores:MyDinamoHsm]
Type=Dinamo
Address=10.1.2.3
User=SOME_USER
Password=SOME_PASSWORD
```

Sample configuration (environment variables):

```bash
KeyStores__MyDinamoHsm__Type=Dinamo
KeyStores__MyDinamoHsm__Address=10.1.2.3
KeyStores__MyDinamoHsm__User=SOME_USER
KeyStores__MyDinamoHsm__Password=SOME_PASSWORD
```

Sample configuration (*.json* file):

```json
"KeyStores": {
	"MyDinamoHsm": {
		"Type": "Dinamo",
		"Address": "10.1.2.3",
		"User": "SOME_USER",
		"Password": "SOME_PASSWORD"
	}
}
```

If you intend to use the HSM combined with Lacuna's PSC module, you must also set the environment variable `HSM_DISABLE_SESSION_CACHE` to `1`. This cannot be done on the
Amplia configuration file, it *must* be an environment variable. On Linux, this means adding the following to the `/etc/systemd/system/amplia.service` file:

```ini
[Service]
...
Environment=HSM_DISABLE_SESSION_CACHE=1
```

If the HSM is in operation modes **RM1** or **RM2**, you must also set the environment variable `HSM_DISABLE_LEGACY_OPERATIONS` to `1`. This cannot be done on the
Amplia configuration file, it *must* be an environment variable. On Linux, this means adding the following to the `/etc/systemd/system/amplia.service` file:

```ini
[Service]
...
Environment=HSM_DISABLE_LEGACY_OPERATIONS=1
```

## See also

* [Amplia - Key Stores](https://docs.lacunasoftware.com/en-us/articles/amplia/on-premises/key-stores)
* [Amplia on premises](https://docs.lacunasoftware.com/en-us/articles/amplia/on-premises)