Skip to main content

Hardware Requirements

The following minimum hardware specifications are required for each node running an instance of the Xillio Link Redirector.

These specifications are only for running the Xillio Link Redirector itself. When running it on the same machine as for example your database service, please refer to the documentation of these services themselves.

In case of running a PostgresQL database on the same machine, this could mean that additional 2GB of ram, an upgraded CPU, and additional disk storage to store all the configuration.

Storage Requirements​

The Xillio Link Redirector uses third-party applications like databases (PostgresQL, MongoDB) and time-series databases (InfluxDB) to read/write data from/to. Because of this, the Xillio Link Redirector itself does not require much storage.

Additionally, Logs are written to the console and should be collected using tools like FluentD, if they need to be kept for longer time-frames.

Because of these design decisions, the application has a very small footprint on your environment. So depending on the configuration of your system, you will need some storage for you database applications etc.

Cloud instances​

For running the Xillio Link Redirector in cloud solutions, we suggest the following VM's:

  • Azure: Azure VM with the Standard B2s size.
  • AWS: EC2 Instance with the T2.medium type.
  • Google Cloud: VM with the n2-standard-2 machine family.

Network Requirements​

Depending on the configuration of the Xillio Link Redirector, the network requirements can vary. But in most cases the following ports need to be open to users:

  • 80 (HTTP)
  • 443 (HTTPS)

This does not mean they have to be open to the internet, but at least to the users that need to access the Xillio Link Redirector.

Additionally we require that the Link Redirector can make outgoing connections to our licensing server. This is done over port 443 (HTTPS) and the domain api.cryptolens.io. Without this connection, the software will not start. The license will be checked regularly, but the software will not stop working immediately if the license check fails. For more information, see Licensing.