Applies to: 
Kyvos Enterprise 
Kyvos Cloud (SaaS on AWS) Kyvos AWS Marketplace
Kyvos Azure Marketplace Kyvos GCP Marketplace Kyvos Single Node Installation (Kyvos SNI)
You can deploy Kyvos clusters on AWS using any of the following methods.
Automated deployment via CloudFormation with External Compute Cluster: In this method, you can either use a default CloudFormation template or create one from the Kyvos Manager and then execute it on AWS to automatically create all the resources required for cluster creation and deployment. After the creation of these resources from CloudFormation, the Kyvos cluster, and Kyvos Manager are created automatically. You can then access the Kyvos Manager or Kyvos and start working right away. You can either deploy it with Databricks or EMR.
Automated deployment via CloudFormation with Kyvos Native: In this method, you can either use a default CloudFormation template or create one from the Kyvos Manager and then execute it on AWS to automatically create all the resources required for cluster creation and deployment. After the creation of these resources from CloudFormation using Kyvos Native (Shared Query Engine or Kubernites), the Kyvos cluster, and Kyvos Manager are created automatically. You can then access the Kyvos Manager or Kyvos and start working right away.
Wizard-based deployment via Kyvos Manager: In this method, the Kyvos Manager allows you to use a wizard that will help to deploy a cluster using any of the following options.
Cluster deployment using resources that are part of the Stack that was created by downloading a template from Kyvos Manager.
Cluster deployment using resources created by your own Stack. (Not the one created by downloading the template from Kyvos Manager).
Cluster deployment using account resources (selecting node mapping option) that are created without any stack.
For external compute-based deployment, you can either deploy it with Databricks or EMR.
For Kyvos Native based deployment, you can also deploy it using with Shared Query Engine or Kubernetes.
Important
For external compute cluster, you must ensure that it must be used in the same region in which other resources of the Kyvos cluster are deployed. If external compute cluster is not in the same region, the Start and Stop functionality during scheduling will not work.
Regardless of which option you select, if you do not have permission to fetch resources from the cloud environment, then you will need to manually enter the information related to resources (like IP addresses of the instances and the name of the bucket). Resources are created by any of the means like AWS console, CLI, REST, or SDK.
After successful deployment, you can further configure the following:
Post-deployment, you can add a new data disk on Query Engines. See the Resources Configuration section for more details.
Knowledge requirements
To deploy Kyvos in the AWS environment, you must have knowledge of the following AWS services:
CloudWatch (Deployment Logs and Events)
Additionally, it is good to have knowledge of the following:
You will not need to request an increase in limits for your AWS Account for this deployment. Read more on proper policy and permissions.
Individuals possessing the AWS Associate Certifications should have a sufficient depth of knowledge to deploy the resources specified in this guide.
Supported AWS regions
Kyvos supports the following AWS regions:
US East (N. Virginia)us-east-1
US East (Ohio)us-east-2
US West (N. California)us-west-1
US West (Oregon)us-west-2
Asia Pacific (Mumbai)ap-south-1
Asia Pacific (Osaka)ap-northeast-3
Asia Pacific (Seoul)ap-northeast-2
Asia Pacific (Singapore)ap-southeast-1
Asia Pacific (Sydney)ap-southeast-2
Asia Pacific (Tokyo)ap-northeast-1
Canada (Central)ca-central-1
Europe (Frankfurt)eu-central-1
Europe (Ireland)eu-west-1
Europe (London)eu-west-2
Europe (Paris)eu-west-3
Europe (Stockholm)eu-north-1
South America (São Paulo)sa-east-1