Node reachability validation for AWS clusters

Applies to: Kyvos Enterprise Kyvos Cloud (SaaS on AWS) Kyvos AWS Marketplace

Kyvos Azure Marketplace Kyvos GCP Marketplace Kyvos Single Node Installation (Kyvos SNI)

There can be four combinations of inputs for node reachability validation

If a password is used for node validation, enable password authentication on each BI Server, Query Engine, and Kyvos Manager nodes as explained in the Instances configuration to use password-based authentication for Kyvos deployment section.
Refer to the following combination of keys in init conf file:

Key name	Description
username	Required in init conf file
privateKey	Required in init conf file, this key is used to connect the Kyvos nodes when a secret is not used, and the password (encrypted/plain text) is not specified) in init conf file.
secretStoreId	Required in init conf file if an external secret is used. In case of secret exist in deployment, the password is read from the secret used in deployment.
kyvosnodespassword	Required in init conf file if plain text password or encrypted password is used to validate nodes. If nodepasswordEncAlgo key is present in init conf file, this value is treated as encrypted else, this is treated as plain text.
nodepasswordEncAlgo	Required in init conf file if validation needs to perform on encrypted password. The kyvosnodespassword key should be encrypted.
cryptography_algorithm	Required in init conf file if validation needs to perform on encrypted password. The kyvosnodespassword key should be encrypted. AES_128_GCM algorithm should be used as a value for cryptography_algorithm key.