Skip to content

Important

For the production environment, a separate X-Road Security Server must be deployed on separate infrastructure (physical or virtual), with its own IP address and DNS name, different from those of the test environment.

Please do not use the test environment's Security Server, or its IP address or DNS name, for production. The Security Servers of the test and production environments, and their corresponding network identifiers, must be kept separate.

Alongside the transition to the production environment, the test infrastructure must be maintained and continue to operate for testing purposes.

X-Road Security Server Deployment Guide

Introduction

There are two deployment options available:

  1. On virtual machines using the Ansible Playbook
  2. In a Kubernetes cluster using X-Road Helm Chart

Supported operating systems for VM deployments are Ubuntu 24.04 and Red Hat 9. The recommended database for the current version of the Security Server is PostgreSQL 16.

According to X-Road's official documentation, the minimum resource requirements for a single security server are:

  • 2 CPU
  • 4 GB RAM
  • 100 Mbps network interface

The X-Road Security Server uses several ports for data exchange between members and for server administration. These ports are:

  • 5500 (HTTPS) - Public (must be accessible from the internet), used for data exchange between security servers.
  • 5577 (OCSP) - Public (must be accessible from the internet), used for data exchange between security servers.
  • 8080 (HTTP) - Internal only, used by services to access the X-Road network.
  • 8443 (HTTPS) - Internal only, used by services to access the X-Road network.
  • 4000 (HTTPS) - Internal only, used for the Administration UI.

Before deployment, please contact ADEL at adel@isaa.am to get the configuration anchor and your member code. This information is required for the post-deployment Security Server configuration.