Prerequisites

Before beginning the installation, ensure that the following are prepared:

• If any operation is being carried out using the interactive tool, these steps should be followed.
  • If a script patch is released for the version, make sure to download the patch.
  • Move the patch to the <installer_path>/patch directory.(e.g.: /home/appviewx/appviewx_kubernetes/patch)
  • Trigger the install.sh script and respond with 'yes' to any prompts that appear, as shown in the image below.

  These steps are essential to ensure that the tool operates with the latest fixes.

• Sudo access to the configured for the appviewx installation user
• If the user opts for a key-based installation, passwordless sudo must be configured. As the root user, add the following lines to the /etc/sudoers file:

  appviewx ALL=(ALL) NOPASSWD:ALL

• Load balancer (LB) for the AppViewX GUI (optional - refer note below)
• Kubernetes master L4 load balancer (optional - refer note below)
• A .p12 certificate for the AppViewX Web GUI - An external signed certificate is typically issued by a trusted Certificate Authority (CA) and is used to authenticate and encrypt communication between the web server and clients, ensuring data integrity and security. (optional - refer note below).
• NTP server details
• Nameserver details
• Proxy or internet access is required on all the nodes if any of the following OS prerequisite packages mentioned below are to be installed during the prerequisite check. Ignore, if the packages are already installed on the nodes.
  • Ubuntu - curl, net-tools, nmap, zip, unzip, sysstat, rsync, tcpdump, chrony, bind9-utils, dnsutils, ebtables, netcat, netcat-openbsd
  • RHEL - curl, net-tools, nmap, zip, unzip, sysstat, rsync, tcpdump, chrony, bind-utils, nmap-ncat, (ebtables, iptables-ebtables, iptables-nft) any one based on OS version
• If you wish to enable Mongo/Vault backups to the SFTP server, you must specify the server where the Database and Vault backups will be securely stored. Ensure that the IP address or hostname is accurate, accessible from your network, and has enough storage space to avoid any connectivity or capacity issues during the backup process.
• The HSM client must be configured on the HSM node. For a single node, the configuration is done on the node itself. For a multi-node setup, the HSM nodes are selected and configured accordingly.