Applies to: 
Kyvos Enterprise Kyvos Cloud (SaaS on AWS) Kyvos AWS Marketplace
Kyvos Azure Marketplace Kyvos GCP Marketplace 
Kyvos Single Node Installation (Kyvos SNI)
Important
From Kyvos 2024.11 release onwards, you can configure Application Gateway from different resource group.
To fetch the Application Gateway from different Resource Group, Kyvos Managed Identity has the Microsoft.Network/applicationGateways/read permission on Application gateway
To scale BI Server and Web Portal nodes in Azure Marketplace, the network interface attached to the existing BI Server and Web Portal nodes must be in the same resource group as the BI Server, Web Portal and other resources. If the network interface attached to the BI Server and Web Portal machines exist in a resource group other than the BI Server and Web Portal machine's resource group, assign the Microsoft.Network/virtualNetworks/subnets/join/action permission to MI (Managed Identity) over VN (Virtual Network) by creating a custom role.
For Azure Enterprise, create a custom role with the required permissions. While creating a custom role, add the Resource IDs for the following services in the assignable scope:
Application Gateway
Virtual Network
Network Security Group
To configure Application Gateway post deployment, create a separate backend pools for Kyvos Manager and Kyvos.
Once the custom role is created, it must be assigned to each of the above listed services.
Increasing Nodes
Note
From Kyvos 2024.10 onwards, you can manage (create/add or delete/terminate) Kyvos Reporting Node for Kyvos Enterprise.
Increased nodes that handle the creation and addition of nodes. An additional field for the zone will be displayed in the environment that supports the zone scaling.
The steps for increasing a node for Query Engine, BI Server, and Web Portal are the same. An additional input for Load Balancer will be displayed for Web Portal scaling.
Currently, the Marketplace and Kyvos Enterprise do not support zones. The zone list is displayed in the AWS Managed Service as it supports zones.
The Kyvos Web Portal node is cloned to create a Kyvos Reporting node.
To access Kyvos Reporting using a Load Balancer, you must configure it manually.
To increase a Kyvos Core Service node, perform the following steps.
On the navigation pane, click Kyvos and Ecosystem> Nodes and Services > Overview.
On the Overview page, you will see the number of nodes for Kyvos Core Services and the number of service instances (BI Server, Query Engine, and Web Portal) configured for the Kyvos cluster.
Click Create > Kyvos Core Service Node. The Create Kyvos Core Service Nodes (Azure Marketplace) dialog box is displayed.
Note
Ensure that the dialog box to create Kyvos Core Services for Managed Service deployment may vary.
When creating a Kyvos Reporting Service node, specify file or version details, upload the license, and enter your Kyvos Manager password. For Kyvos Enterprise, AWS Managed Services, AWS SaaS, the access or secret key is needed.
For Marketplace
For Kyvos Enterprise/AWS SaaS/AWS Managed Services
Enter the number of nodes for Query Engines, BI Server, and Web Portal service that you want to create. Enter your Kyvos Manager password to create the node.
Note
Enter the Instance Group Name (GCP) to add Web Portal Service on the cluster where Kyvos Services have already been installed. After adding the instance group name, click Validate. This will validate the instance group. If it is validated, the Validated Successfully message is displayed. In case of any error, you need to provide a valid instance group name.
The Load Balancer-related configuration is displayed in the Read-only mode. You can also modify the Load Balancer-related configuration using the Change Configuration button if required. When you modify the configurations, it is applicable only for the automation of entries addition for the newly added nodes.
Enter your Kyvos Manager password to create the node and click Create. The Nodes will be created, and you will be redirected to the Operations page where you can view the status.
Note
You can also manage node using the Actions menu (…) on the right side of the window. For adding or deleting node, see the Managing Services Mapping section.
Decreasing Nodes
Note
Deleting Kyvos Reporting Service node is only supported in AWS Managed Service.
The option to terminate Kyvos Reporting Service node will be displayed only when the node is created.
To delete a node, perform the following steps.
The following procedure to terminate the Kyvos Core Service Node has been demonstrated. Similarly, you can delete a node for Query Engine, BI Server, and Web Portal by clicking the three dots (…), and then click Terminate > Kyvos Core Service Node.
The Terminate Kyvos Core Service Nodes dialog is displayed. Enter the number of nodes you want to terminate, and then enter your Kyvos Manager password to terminate the node.
Click Terminate. The node will be terminated.
Important
After deleting the BI Server, Zookeeper must be removed before redeploying it. You will see the following message after the deletion.
Click Remove. This will take you to the Zookeeper Configuration page.
The Load Balancer-related configuration is displayed in the Read-only mode. You can also modify the Load Balancer-related configuration using the Change Configuration button if required. When you modify the configurations, it is applicable only for the automation of entries removal for nodes being removed.
Note
You can also manage node using the Actions menu (…) on the right side of the window. For adding or deleting node, see the Managing Services Mapping section.