---
title: "Legacy provisioning"
url: "https://docs.yugabyte.com/stable/yugabyte-platform/prepare/server-nodes-software/software-on-prem-legacy/"
---

# Legacy provisioning

Software requirements for on-premises provider legacy provisioning.

Prepare a VM for deploying universes on-premises

Legacy provisioning deprecated

Legacy automatic and fully manual provisioning are deprecated. For new nodes, use the [node agent script](/stable/yugabyte-platform/prepare/server-nodes-software/software-on-prem/#run-the-provisioning-script "node agent script"). Existing universes provisioned with these methods continue to work, and you can upgrade YugabyteDB Anywhere to v2025.2 and later without moving them. Assisted manual provisioning has been removed. For more information, refer to [Prepare to upgrade](/stable/yugabyte-platform/upgrade/prepare-to-upgrade/ "Prepare to upgrade").

- [How to Choose](/stable/yugabyte-platform/prepare/server-nodes-software/software-on-prem-legacy/)
- [Automatic](/stable/yugabyte-platform/prepare/server-nodes-software/software-on-prem-auto/)
- [Fully manual](/stable/yugabyte-platform/prepare/server-nodes-software/software-on-prem-manual/)

How you provision nodes for use with an on-premises provider depends on the SSH access that you can grant YugabyteDB Anywhere to provision nodes.

SSH mode Description Notes For more details 

Permissive You can allow SSH to a root-privileged user, AND  
You can provide YugabyteDB Anywhere with SSH login credentials for that user. For example, the ec2-user for AWS EC2 instances meets this requirement. In this mode, YugabyteDB Anywhere will sign in to the VM and automatically provision the nodes. See [Automatic Provisioning](/stable/yugabyte-platform/prepare/server-nodes-software/software-on-prem-auto/ "Automatic Provisioning"). 

Restrictive All other cases (you disallow SSH login to a root-privileged user at setup time). In this mode, you'll manually install each prerequisite software component. See [Fully Manual Provisioning](/stable/yugabyte-platform/prepare/server-nodes-software/software-on-prem-manual/ "Fully Manual Provisioning").

Note that, for Permissive mode, the root-privileged SSH user can have any username except `yugabyte`. When YugabyteDB Anywhere later uses the provided SSH user to sign in and prepare the node, it will automatically create and configure a second user named `yugabyte`, which will be largely de-privileged, and will have very limited sudo commands available to it. YugabyteDB Anywhere uses the `yugabyte` user to run the various YugabyteDB software processes.

SSH access is required for initial setup of a new database cluster (and when adding new nodes to the cluster). After setup is completed, SSH can be disabled, at your option. Leaving SSH enabled, however, is still recommended to provide access to nodes for troubleshooting.

## Best practices

When creating your VMs, create at least two virtual disks: one as the boot disk, and another for data and logs.