v2025.1 STS Stable release with standard-term support v2.25 Preview Preview release - not for production v2024.2 LTS Stable release with long-term support v2024.1 STS Stable release with standard-term support v2.20 LTS Stable release with long-term support Unsupported versions

Legacy provisioning

Prepare a VM for deploying universes on-premises

Legacy provisioning deprecated

Legacy provisioning of on-premises nodes is deprecated. Before you can upgrade YugabyteDB Anywhere to v2025.2, all universes must be updated to use node agent and provisioned using the node agent script. For more information, refer to Prepare to upgrade.

When YugabyteDB Anywhere (YBA) has access to an SSH user with passwordless sudo privileges (for example, the ec2-user on AWS EC2 instances), then YBA can provision the VMs automatically.

With Internet or Yum connectivity

If your VM has Internet or Yum connectivity, you must provide to YBA a VM with the following pre-installed:

  • Supported Linux OS with an SSH-enabled, root-privileged user. YBA uses this user to automatically perform additional Linux configuration, such as creating the yugabyte user, updating the file descriptor settings via ulimits, and so on.
  • Additional software

Take the time now to prepare the VM.

  • Save the SSH-enabled, root-privileged user credentials (username and SSH Private Key Content PEM file).
  • Save the VM IP addresses for later when creating the on-premises provider.
Save for later To configure
SSH-enabled, root-privileged user name On-premises provider
SSH-enabled, root-privileged Private Key Content PEM file On-premises provider
VM IP addresses On-premises provider

No Internet nor Yum connectivity

If your VM doesn't have Internet or Yum connectivity, you must provide to YBA a VM with the following pre-installed:

Take the time now to prepare the VM.

  • Save the SSH-enabled, root-privileged user credentials (username and SSH Private Key Content PEM file).
  • Save the VM IP or DNS addresses for later when creating the on-premises provider.
Save for later To configure
SSH-enabled, root-privileged user name On-premises provider
SSH-enabled, root-privileged Private Key Content PEM file On-premises provider
VM IP addresses On-premises provider