Try our Experimental-AI powered search above!

For YugabyteDB Anywhere (YBA) to be able to deploy and manage YugabyteDB clusters, you need to provide YBA with privileges on your cloud infrastructure to create, delete, and modify VMs, mount and unmount disk volumes, and so on.

The more permissions that you can provide, the more YBA can automate.

• On-premises
• AWS
• GCP
• Azure
• Kubernetes

GCP

The Compute Admin role permission is required on the GCP service account where you will deploy:

roles/compute.admin

To grant the required access, you must do the following:

• Create a service account in GCP.
• Grant the required roles to the account.

Then use one of the following methods:

• Obtain a file containing a JSON that describes the service account credentials. You will need to provide this file later to YBA.
• Attach the service account to the GCP VM that will run YBA.

Managing SSH keys for VMs

When creating VMs on the public cloud, YugabyteDB requires SSH keys to access the VM. You can manage the SSH keys for VMs in two ways:

• YBA managed keys. When YBA creates VMs, it will generate and manage the SSH key pair.
• Provide a custom key pair. Create your own custom SSH keys and upload the SSH keys when you create the provider.

If you will be using your own custom SSH keys, then ensure that you have them when installing YBA and creating your public cloud provider.