Applies to: 
Kyvos Enterprise 
Kyvos Cloud (SaaS on AWS) Kyvos AWS Marketplace
...
Regardless of the type of installation, the following prerequisites should be available.
EC2 key pair, consisting of a private key and a public key. You can create the key pair if needed.
...
You must have the Access Key and Secret Key to access the Kyvos bundle. Contact Kyvos Support for details.
Valid Kyvos license file.
Databricks cluster with the following parameters:
Databricks Runtime Version: Select 10.4 LTS (includes Apache Spark 3.2.1, Scala 2.12)
Autopilot Options: Select the following:
Enable autoscaling: Select this to enable autoscaling.
Terminate after ___ minutes of inactivity. Set the value as 30.
Worker type: Recommended value r5.4xlarge
Min Workers: Recommended value 1
Max Workers: Recommended value 10
Driver Type: Recommended value r 5.xlarge
Advanced options
To use Databricks with Spot Instances:
Select the Spot fall back to On-demand checkbox from the On-demand/spot composition area.
Specify the number of workers.
In the Spark Configurations define the following property in case of Glue-based deployment.
spark.databricks.hive.metastore.glueCatalog.enabled=true
If cross-account glue is to be used, then define the following property to access cross-account glue :
spark.hadoop.hive.metastore.glue.catalogid <GLUE_CATALOG_ID>
After these, set the below parquet-specific configuration properties:
spark.hadoop.spark.sql.parquet .int96AsTimestamp true
spark.sql.parquet.binaryAsString false
spark.sql.parquet .int96AsTimestamp true
spark.hadoop.spark.sql.parquet.binaryAsString false
spark.databricks.preemption.enabled false
spark.sql.caseSensitive false
spark.hadoop.spark.sql.caseSensitive false
You must change Spark configurations to use managed disk. Ensure that you must not change the configuration in the default root (/tmp) volume.
In the Spark Configurations, add the spark.local.dir /local_disk0 property where the local_disk0 is the managed disk.
Optionally, you can execute the df -h command from a notebook for verification.
Add the SPARK_WORKER_DIR=/local_disk0 value in the Environment variables.
Tags: Owner and JIRA tags are required to run the cluster.
Instance profile: Copy the Instance Profile ARN of the role created earlier (Point 2 of the Permission requirements).
In Databricks console, go to Admin Console > Instance Profile and click Add Instance Profile. Paste the Instance Profile ARN in the text box.
Select the Skip Validation checkbox and then click Add.
In Cluster settings, go to Advance Options, and in Instance Profile field, select the instance profile created above.
Databricks information:
Databricks Cluster Id: To obtain this ID, click the Cluster Name on the Clusters page in Databricks.
The page URL shows <https://<databricks-instance>/#/settings/clusters/<cluster-id>. The cluster ID is the number after the /cluster/ component in the URL of this page.Databricks Cluster Organization ID: To obtain this ID, click the Cluster Name on the Clusters page in Databricks.
The number after o= in the workspace URL is the organization ID. For example, if the workspace URL is https://westus.azuredatabricks.net/?o=7692xxxxxxxx, then the organization ID is 7692xxxxxxxx.Databricks Role ARN: Use the ARN of the Databricks-instanceprofile-role created earlier (Point 2 of the Permission requirements).
The ARN looks like this: arn:aws:iam ::45653****** *:role /AssumeRoleTest
This Databricks Role should have " iam:PassRole" permission in the role you have created for the Databricks workspace.
If using an existing Secrets Manager, ensure that the KYVOS-CONNECTION-DATABRICKS-TOKEN key is added to it.
Using Kyvos Public AMI
In addition to the prerequisites mentioned in the Common section, you must have the following:
...