Parameter | Description |
|---|
Cluster Name | Provide a unique cluster name. |
License | Upload your Kyvos license file. |
Installation Path | Provide the installation path for Kyvos. |
Username | Enter your username. |
Authentication Type | Password: Provide your credentials. Ensure that the permissions listed here are available on all the EC2 instances for Linux user deploying the cluster. Private Key: Choose and Upload the Private Key file.
|
Configure Kyvos Services on Cloud | Select Instance By: IP Address: Select this option for IP Address-based deployment. Hostname: Select this option for hostname-based deployment. In this case, you can deploy the cluster using custom hostnames for nodes to be used for Kyvos services.
Click the Use custom hostname for selected nodes link to specify or map a custom hostname for the selected BI Server, Query Engine, and Kyvos Manager/repository node.
NOTE: Ensure that the instances have been configured for using Custom hostnames.
Stack: Select the stack that you created.
NOTE: If you want to deploy Kyvos Services (BI Server, Query Engine, and Web Portal) on the same Instance, in this case, select the None (node mapping Manually) option. Fetch resources: Click to view and modify any resources.
The resources configured in the stack, such as EC2 instance(s) for BI Server, EC2 instance(s) for Query Engine, EC2 instance(s) for Web Portal, and so on are displayed. Click the Modify link corresponding to the Identified Resources to edit them. You can also select the Repository here.
NOTE: If you want to use your own resources, select the None option, and provide the details in the displayed fields.
Here, if you have the requisite permissions, your AWS resources will be displayed in the lists. Otherwise, you will have to manually provide the details. Deploy BI Server, Query Engine, and Web Portal services on ip-<>.ec2 internal instance: This checkbox is displayed only when you select the None (node mapping Manually) option from the Stack list. Selecting this checkbox will deploy Kyvos services on the same instance.
NOTE: By default, the option to deploy EC2 instance(s) for BI Server, EC2 instance(s) for Query Engine, and EC2 instance(s) for Web Portal will be disabled.
|
Secrets Manager | Displays the name of the Secrets Manager that will be used for storing passwords. 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 or Shared Query Engines option. NOTE: When you select Kubernetes from the Compute Cluster list, the Kubernetes Details section is displayed. |
Kubernetes Details | Enter the following Kubernetes details: Kubernetes Cluster Name: Select the Kubernetes cluster name from the list.
If the list is not populated, you need to enter the Kubernetes cluster name manually, and then click Fetch Details. The Kubernetes cluster details will be fetched. Node Pool Name: Select the Node Pool name from the list. K8S Addon Auth Role Name: The K8S Addon Auth Role Name is displayed by default.
If the node pool name list is not populated, you need to enter the Node Pool Name manually, and then click Validate Kubernetes Cluster Details : Click this link to validate the K8s Kubernetes cluster details. |
Enable Compute Server Scaling | Select this checkbox to enable maximum or minimum compute server for scaling. When you select this checkbox, the following options will be displayed. Minimum Compute Server Count: Select the minimum compute Server count that will be started initially. Maximum Compute Server Count: Select the maximum compute Server count up to which you want to scale.
NOTE: If you do not select this checkbox, the Compute Server Count field is displayed. Enter the compute server count that you want to set for minimum or maximum compute server scaling. |
