To use your own certificates in service configuration files, it is necessary to specify the path to the certificate and key files.

Evi-core service

Switch to editing the configuration file /opt/evi-core/evi-core.conf.

Specify the path to the certificate and key in the [ssl] section under the crt and key parameters:

[ssl]
cert_file=<path to certificate>
key_file=<path to key>

Evi-scud service

Switch to editing the configuration file /opt/evi-scud/evi-scud.conf.

Specify the path to the certificate and key in the [ssl] section under the crt and key parameters:

[ssl]
cert_file=<path to certificate>
key_file=<path to key>

Evi-live service

Switch to editing the configuration file /opt/evi-live/evi-live.conf.

Specify the path to the certificate and key in the [ssl] section under the crt and key parameters:

[ssl]
cert_file=<path to certificate>
key_file=<path to key>

Evi-archive sevice

Switch to editing the configuration file /opt/evi-archive/evi-archive.conf.

Specify the path to the certificate and key in the [ssl] section under the crt and key parameters:

[ssl]
cert_file=<path to certificate>
key_file=<path to key>

Evi-analyzer service

Switch to editing the configuration file /opt/evi-analyzer/evi-analyzer.conf.

Specify the path to the certificate and key in the [ssl] section under the crt and key parameters:

[ssl]
cert_file=<path to certificate>
key_file=<path to key>

Evi-core-web service

Switch to editing the configuration file /etc/angie/http.d/evi-core-web.conf .

Specify the path to the certificate and key under the ssl_certificate and ssl_certificate_key parameters:

ssl_certificate <path to certificate>
ssl_certificate_key <path to key>

Evi-analytics service

Switch to editing the evi-analytics_1.4.0_docker-compose.sh file. 

Specify in variables:

  #EVI-ANALYTICS CONFIG SECTION [ssl]
  : ${EVIANALYTICS_SSL_CERT_FILE="<path to certificate>"}
  : ${EVIANALYTICS_SSL_KEY_FILE="<path to key>"}