Installing Cluster using Resources Created on AWS
This documentation is for Kyvos 2026.8.x. To view documentation for other Kyvos versions, click here. |
|---|
Overview
This section explains how to deploy a Kyvos Enterprise cluster on AWS using pre-provisioned AWS infrastructure. You can provision the required resources, such as EC2 instances, networking, and storage, manually or using a CloudFormation stack. The Kyvos Installer then configures and deploys Kyvos on the existing infrastructure.
On this page:
Installing cluster using resources created on AWS
To install cluster using resources created on AWS, perform the following steps.
Access the installation URL, such as: http://clusterIP:port/kyvosmanager/#/kyvos-installer/aws
If you do not have the URL and/or credentials, click here to contact support.On the Kyvos Installer, select the I have all the resources option.
Click Install Kyvos. The Setup Kyvos Environment dialog is displayed.
Enter details as:
Parameter | Description |
|---|---|
Cluster Name | Provide a unique cluster name. |
License | Upload your Kyvos license file. |
Installation Path | Provide the installation path for Kyvos. |
User Name | Enter your username. |
Authentication Type |
|
Configure Kyvos Services on Cloud |
|
Kyvos Repository | Select the required external Kyvos Repository. In case you are using an externally managed repository, the following options are displayed.
|
Repository Password |
|
Output S3 Storage > Bucket Name | Select the output S3 bucket name. |
Secrets Manager | Enter the name of the Secrets Manager that will be used for storing passwords. This is a mandatory field. Note: This field is displayed if you selected the Deploy with Enhanced Security option at the time of creating resources. |
Compute Cluster | Select the Kubernetes, Shared Query Engines, or Dedicated Compute Cluster option from the Compute Cluster Type list. NOTE:
|
Kubernetes Details | Enter the following Kubernetes details:
|
Lambda Function | Select the required function from the list:
|
Click the Advanced Settings link. The Advanced Settings dialog box is displayed with values populated according to the ones that you defined while creating the stack.
To update any fields, enter information as:
Configuration Type | Parameter/Field | Comments/Description |
|---|---|---|
Common | Kyvos Setup Package | Select the Kyvos bundle to be installed. Kyvos Manager contains compatible Kyvos bundles. To use any other Kyvos version, click the Upload button |
Semantic Model Local Path | Enter the semantic model local path where cuboids will be copied. For multiple paths, enter a semicolon-separated list. Note: The deployment user must have full permission on the parent of the local semantic model path. | |
Automatically restart Kyvos services when down | Select this option to enable high availability mode for the Kyvos service. This will ensure Kyvos services are always up and running. The Kyvos Manager will automatically restart the , query engine, repository, and web portal services, in case any of these services go down | |
| Listener Port | Enter the listener port for analytical server. |
JMX Port | Enter the JMX port for analytical server health monitoring. | |
Work Directory | Enter the directory location on HDFS, where analytical server has access permissions. | |
Memory Configuration Mode | By default, the Auto mode is selected. In Auto Mode, calculations are performed automatically by the system internally. Note: The Maximum Heap Memory and Analytical Store Max Memory options are enabled only when you set the memory configuration in the Manual mode. | |
Maximum Heap Memory | Enter the maximum memory available for analytical server. | |
Analytical Store Max Memory | Specify analytical store max memory for querying in GB. | |
Additional Java Options | Use this to define custom Java properties for your analytical server. | |
Query Engine | Thrift Listener Port | Enter the thrift listener port for Query Engine. |
JMX Port | Enter the port for Query Engine health monitoring. | |
Memory Configuration Mode | By default, the Auto mode is selected. In Auto Mode, calculations are performed automatically by the system internally. In the Manual Mode, you can manually provide memory values as needed. Note:
| |
Maximum Heap Memory | Enter the maximum memory for Query Engine. | |
| Analytical Store Max Memory for Querying | Specify analytical store max memory for querying in GB. |
Analytical Store Max Memory for Processing | Specify analytical store max memory for processing in GB. | |
Configure Concurrent Processing Task Count | By default, the Auto mode is selected. If you select the Manual mode, specify the number of nodes to be used for concurrent processing task count. | |
| Additional Java Options | Use this to define custom Java properties for your Query Engine. |
Compute Server | Listener Port | Enter the listener port for compute server configuration. |
| Maximum Heap Memory | Enter the maximum memory available for compute server configuration. |
| Additional Java options | Use this to define custom Java properties for your compute server configuration. |
| Analytical Store Maximum Memory | Enter the maximum Analytical Store memory available for compute server configuration. |
Web Portal | UI Port | Enter the port on which Kyvos Web client will run. |
JMX Port | Enter the port for Web portal health monitoring. | |
Shut-down Port | Enter the port to be used for shutting the Tomcat server. | |
AJP Port | Enter the port on which the AJP connector creates a socket and awaits an incoming connection. | |
Maximum Heap Memory | Enter the maximum memory for the Web portal. | |
Additional Java Options | Use this to define custom Java properties for the Web portal. | |
Network Protocol Configuration | Enable TLS | Select the checkbox to enable TLS for the cluster. Note: Before enabling TLS, if you are using your own script for resource creation instead of the Kyvos shared scripts, you must rename the OpenSSL configuration file on the Kyvos Manager and the node where the Postgres Service is running. The OpenSSL configuration file is available in the /etc/pki/tls/openssl.cnf folder. To accomplish this, you will need to have sudo access. |
HTTP Protocol Version | Select the HTTP Protocol Version for use with TLS. | |
Kyvos Web Portal on HTTPS | Select the checkbox to use HTTPS for connecting to Kyvos Web Portal. | |
Kyvos Web Portal Configuration | NOTE: This is displayed only if Kyvos Web Portal on HTTPS checkbox is selected
| |
Enable GPU | Upload Drutdb Jar | For a GPU enabled cluster, upload the drutdb.jar file to enable GPU querying. |
Click Apply.
Click NEXT. The system validates your settings, and all the configurations that are done so far are displayed in the Review and Confirm dialog box.
Review the settings, and click BACK to make any changes.
Select the checkboxes to accept the terms and start Kyvos services on installation.
Click INSTALL to complete the installation.
Important
After completing a wizard-based deployment with Kyvos Native using Shared Query Engines, run the
vi /proc/sys/vm/max_map_countcommand on each Kyvos node, including the Analytical Server, Query Engine, and Kyvos Manager.Set the value of
vm.max_map_countto 524288 in the/proc/sys/vm/max_map_countfile on each Kyvos node.
If you deployed Kyvos using a custom stack or your own AWS account resources in the wizard, create and configure the Lambda functions to enable scheduling on the Analytical Server.