> For the complete documentation index, see [llms.txt](https://wiki.datadike.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.datadike.com/pam/deploy-operate/install-single-node.md).

# Install a single node

The documented path for bringing up one instance from the appliance image — console setup, DNS, first login, licence — and the parts of the procedure that only DataDike holds.

{% hint style="warning" %}
**Validate this procedure against the version you are deploying.** Installation procedure changes between releases, and the sources this page is built from do not state which version they were written for. Before you start, confirm the current procedure and the correct appliance image with DataDike.

The image itself, the licence file and the low-level installation steps are maintained by DataDike and are not reproduced here. Nothing on this page is a substitute for the release-specific installation notes.
{% endhint %}

## What this is and when to use it

The single-node path: one machine, running everything. It is the right shape for a lab, a proof of concept, or a production environment that does not need to survive the loss of the node. If access must survive a node failure, deploy a cluster instead — see [Install a high-availability cluster](https://wiki.datadike.com/pam/deploy-operate/install-cluster.md).

The deployment is containerised and fronted by nginx. It is delivered as an appliance image that you import into your hypervisor or cloud, then configure from a console menu on first boot.

## Before you start

* A machine that meets the [system requirements](https://wiki.datadike.com/pam/deploy-operate/requirements.md), with the disk sized for your recording retention rather than the minimum figure.
* The firewall rules from [Network and connectivity requirements](https://wiki.datadike.com/pam/deploy-operate/network-requirements.md), agreed before the machine is deployed rather than after.
* The appliance image and the licence file, from DataDike.
* A DNS name for the instance, and the ability to create the record in your private DNS. A wildcard or subdomain certificate if you are terminating HTTPS on the instance.
* The implementation support contact. Two of the steps below — installing the certificate and any change to the appliance configuration file — are performed on the appliance's command line by that team.

## Steps

1. **Import the appliance image** into the hypervisor or cloud and start it.
2. **Configure the machine from the first-boot console.** Sign in to the console with the documented appliance user (see [Documented defaults](#documented-defaults) below). The menu covers network configuration, the hostname, system information, and reboot and shutdown.
3. **Set the date, time and timezone correctly** before going any further. A drifted clock breaks one-time passwords and is easily mistaken for an authentication fault.
4. **Reach the console by name, temporarily.** Until the DNS record exists, add an entry mapping the instance's address to its hostname in the hosts file of your own workstation — on Windows, `C:\Windows\System32\drivers\etc\hosts`. This is a setup aid for your machine only, not a deployment step.
5. **Sign in to the console** at `https://<your-hostname>` with the documented default administrator account, and change its password immediately.
6. **Import the licence.** Every function of the platform stays disabled until the licence is imported, so do this before you try anything else and conclude the build is broken.
7. **Install the HTTPS certificate.** This is performed by the implementation support team on the appliance's command line, with your wildcard or subdomain certificate.
8. **Create the definitive DNS records** — in your private DNS, and also in public DNS if you are publishing the console through NAT or DNAT. Then remove the temporary hosts entry from your workstation.
9. **Validate the firewall rules** against [Network and connectivity requirements](https://wiki.datadike.com/pam/deploy-operate/network-requirements.md), from a client that sits where real users will sit.
10. **Connect your authentication sources** and set the inactivity and auto-disable thresholds for accounts.
11. **Register the assets** to be protected — manually, by spreadsheet import, or by discovery and synchronisation.
12. **Register the accounts** to be managed on those assets.
13. **Configure the mail server.** It carries backup delivery, alerts and approval workflows, so several later features silently do nothing without it.
14. **Set up the vault backup policy and automation**, and set the retention periods for logs and session records.
15. **Turn off component registration.** Once every component has registered, clear **Registration** in **System settings › Components › Basic**. While it is enabled, any component that knows the address of the instance can register itself. Re-enable it only for as long as it takes to add a new component.

## What you should see

The console answers over HTTPS on its DNS name with a valid certificate. After the licence import, the menu areas that were inert become usable. **System settings › Components** lists the platform's own microservices — the core API, the task service, and the terminal, graphical, database and virtual application connectors — each with a **Load status** of **Normal** and a **Remote address** pointing at the node.

## How to verify it worked

Four checks, in this order. Each one proves something the previous one does not.

1. **The platform's own dependencies.** Request `/api/health/` — no authentication needed. The JSON it returns carries `status`, `db_status`, `db_time`, `redis_status`, `redis_time` and `time`. A healthy response proves the database and Redis are reachable, which a plain "the login page loads" does not.
2. **The components.** On **System settings › Components**, every component shows **Normal**. Anything reading **Offline** is a service that did not come up, and the connectors are the ones users will notice first.
3. **The clock and the second factor.** Enrol one account with a one-time password and sign in with it. If the code is rejected, the clock is wrong, not the account.
4. **A real session, end to end.** Connect to one registered asset with one managed account, then find that session in the audit trail with its recording attached and playable. This is the only check that exercises the whole path — authentication, authorisation, credential injection, the connector, and the recording store.

## Common errors

| Symptom                                                                      | Cause                                                                                                   | Fix                                                                                                                               |
| ---------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------- |
| The console loads but most features are unavailable                          | The licence has not been imported                                                                       | Import the licence. All functions stay disabled until it is present                                                               |
| The hostname does not resolve during setup                                   | The DNS record has not been created yet                                                                 | Add the temporary hosts entry on your own workstation, then create the definitive record in your private DNS                      |
| *OTP code invalid, or server time error* on every login                      | The node's clock has drifted; TOTP is validated to the second                                           | Synchronise the clock over NTP and set the correct timezone                                                                       |
| A component shows **Offline** in the Components list                         | The service did not start on the node where it is installed                                             | Check that service on that node. An offline core API takes the whole platform down; an offline connector removes one session type |
| The node's disk fills within weeks                                           | Recordings are still going to the local **default** backend, which has no redundancy and does not scale | Configure external object storage and make it the default backend                                                                 |
| Sessions from a client network fail while they work from the console network | A firewall rule was validated from the wrong place                                                      | Re-test from a client that sits where real users sit                                                                              |

## Documented defaults

These are the defaults the sources document. Treat all of them as things to change or confirm, not as configuration to keep.

| Item                                | Documented default                        | Note                                                                      |
| ----------------------------------- | ----------------------------------------- | ------------------------------------------------------------------------- |
| Appliance console user              | `client` / `client@client`                | Change it as part of the build                                            |
| Console administrator               | `admin` / `datadike`                      | Change it at first login, before the instance is reachable by anyone else |
| Command-line access to the solution | SSH on port 2222                          | Not port 22 — that port belongs to the assets                             |
| Recording backend                   | **default**, type **Server** (local disk) | Not suitable for production                                               |
| Component registration              | Enabled                                   | Disable it once the build is complete                                     |
| Licence grace period                | 7 days after expiry                       | Time to load the new licence, not a licence-free period                   |

{% hint style="danger" %}
The two default credentials above are published in DataDike's documentation, which means an attacker has them too. Change both before the instance is reachable from anywhere but your own workstation.
{% endhint %}

## Related pages

* [System requirements](https://wiki.datadike.com/pam/deploy-operate/requirements.md)
* [Network and connectivity requirements](https://wiki.datadike.com/pam/deploy-operate/network-requirements.md)
* [Install a high-availability cluster](https://wiki.datadike.com/pam/deploy-operate/install-cluster.md)
* [LDAP and Active Directory](https://wiki.datadike.com/pam/administration/identities/ldap-and-ad.md)
* [Core concepts](https://wiki.datadike.com/pam/get-started/core-concepts.md)
