Use Graviton Instances

Select the checkbox to deploy the Kyvos Services (like Analytical Server, Query Engine, Kyvos Manager, EMR Master, and Core nodes) on Graviton instances.

NOTE: For Kyvos instances, Graviton CPU is supported with RDS repository service only.

EC2 instance(s) for Analytical Server

Specify the following:

• Number of Node(s)

• Instance Type

• Installation Disk

EC2 instance(s) for Query Engine

Specify the following:

• Number of Node(s)

• Instance Type

• Installation Disk

• EBS Volume

NOTE: Installation disk size must be 100 GB and the cuboid replication disk size must be in the multiplier of 50 or 100.  

Web Portal High Availability  

Select to enable web portal high availability, and specify the following:

• Number of Node(s) 

• Instance Type 

• Installation Disk 

• Subnet for Load Balancer (Possible value list should be Public or Private) 

EC2 instance for Kyvos Manager

The checkbox is selected by default for the automated deployment and an EC2 instance is launched for the Kyvos Manager.

• Provide the Instance Type and Installation Disk details.
  When using a multi-tenant environment, you can use the Deploy as Tenant checkbox to define a tenant.

Select one of the following repository types from the Repository list.

• Bundled Postgres: To select bundled Postgres as a repository for Kyvos Manager. 

• Create New RDS: To create a new external repository for Kyvos Manager.

• Existing RDS: To use the existing RDS of Kyvos Manager.

• Select the size of the instance type from the Repository Instance Type. 

External Repository for Kyvos 

• Select this option to create a PostgreSQL-based repository using the Amazon RDS. Otherwise, the pre-bundled PostgreSQL-based Kyvos repository will be used.

• Select the Repository Instance Type

Output S3 Storage 

Select this option to create an S3 storage bucket for Kyvos output.

Bucket Name Prefix

Compute Cluster Type

Select one of the following options to select a compute cluster type engine to process semantic model.

• EMR

• Databricks

EMR Cluster

Select this option to define configurations for the EMR cluster.

• Master Node Instance Type

• Core Node Instance Type

• Enable Glue

NOTE: In case you do not configure the EMR here, you can use a Shared EMR. In this case, you need to add a common Security Group for master and core in the inbound rule of the Security Group of the Analytical Server.

Use Graviton Instances for EMR cluster 

The checkbox is selected by default, indicating that the EMR cluster is deployed with Graviton instances.  To deploy the EMR cluster with non-Graviton instances, you must clear the checkbox. 

After selecting this checkbox, the Master Node Instance Type and the Core Node Instance Type are selected by default.  

Enable Replication

Select this checkbox to configure replication will be available when at least one of the Bucket, Secret, or RDS Repository is created as part of deployment. Replica are created and configured only for the deployment time created resources. For any of these 3 resources used in deployment that are created externally, user must manage (create & configure) their replica.

Replication region

Select the required replication region.

Use Custom Image

(please see the note below)

Select this option to use a custom image of your environment for deploying the Kyvos cluster. Custom images can be used to bootstrap deployment tasks like preloading applications, application configurations, and other configurations.   

You will have to provide the following information when deploying the cluster through CloudFormation.

• AmiDefaultUserName: Enter the AMI default logged-in Linux user

• AmiId: Enter the AMI ID to be used for launching Kyvos Instances .  

NOTE: 

• To use your custom image, templates named oe _custom.json, qe_custom.json,   km_custom.json, and base_custom.json must be available at the $KYVOS_MANAGER_HOME/cloud/ aws /templates/ location.

• If you select the Use Graviton Instances checkbox, the Use Custom Image checkbox is disabled.

Deploy with enhanced security

Enhanced security ensures passwords are stored in the AWS Secrets Manager and not in the Kyvos configuration files.

Credit Based Deployment 

Select this checkbox to create or support the credit-based license in Kyvos. 

In the Credit Management Resouces list, select one of the following: 

• Create New: Select this option to create a shared Credits Database for the primary cluster deployment.

• Use Existing: Select this option to use the existing shared Credits Database for the secondary or tertiary cluster deployment.  

EMR and RDS Versions  

Select Kyvos Certified Versions Only to list EMR and RDS versions supported by Kyvos .

Else, select the All versions option to view all the versions.

These versions are displayed on the AWS CFT Console at the time of cluster deployment.