Automated Deployment for GCP using Terraform Script

Applies to: Kyvos Enterprise Kyvos Cloud (SaaS on AWS) Kyvos AWS Marketplace

Kyvos Azure Marketplace Kyvos GCP Marketplace Kyvos Single Node Installation (Kyvos SNI)

This section describes how to automate the deployment of Kyvos resources on Google Cloud Platform using Terraform scripts to create and configure the required infrastructure and services.

In the automated deployment method, you must use the scripts to create all the resources and services required for installing and deploying the Kyvos cluster in your GCP environment.

To create resources using Terraform script, see the Creating Kyvos Resources for GCP using Script using terraform script section for more details.

Note

Download the GCP Installation Files folder and keep the requisite files handy for installation and deployment.

After creating resources using scripts, the configuration of the Kyvos GCP cluster on Kyvos Manager is no longer needed.

Once the resources have been created successfully, deployment of the Kyvos cluster will automatically start. You can log in to Kyvos Manager and verify the cluster deploy Operations page.

You can verify the 'Cluster Deploy' on the Operations page of the Kyvos Manager.

Important

From Kyvos 2025.11 onwards, by default install PostgreSQL is used in new deployments.
Before proceeding with the installation and deployment, please ensure that you have all the prerequisites for deploying Kyvos in GCP using Terraform Script

Tip

To proceed with wizard-based deployment, change the value of the parameter kmCount to 0 in the kyvosparams.tfvars file (provided in the Installation Files folder).
To deploy the Kyvos cluster with password-based authentication and custom hostnames, you must use the wizard-based deployment, as these features are not supported in the automated deployment.
Post-deployment, for a non-SSH based cluster, if you use an existing Dataproc cluster and a new bucket, you must execute the dataproc.sh script (provided in the Installation Files folder) on the master node of Dataproc after modifying the values of DEPLOYMENT_BUCKET, WORK_DIR, COPY_LIB, and DATAPROC_VERSION to the name of the existing bucket. Then, sync the library and configuration files from the Kyvos Manager on the Dataproc page in the Common Configuration section.

HTTP Status 429 – Too Many Requests

Automated Deployment for GCP using Terraform Script

HTTP Status 429 – Too Many Requests