docs/content/v2024.1/yugabyte-platform/prepare/server-nodes-software/software-on-prem-auto.md
{{< warning title="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. {{< /warning >}}
<ul class="nav nav-tabs-alt nav-tabs-yb"> <li> <a href="../software-on-prem-legacy/" class="nav-link"> How to Choose </a> </li> <li> <a href="../software-on-prem-auto/" class="nav-link active"> <i class="fa-regular fa-wand-magic-sparkles"></i> Automatic </a> </li> <li> <a href="../software-on-prem-assist/" class="nav-link"> <i class="fa-regular fa-scroll"></i> Assisted </a> </li> <li> <a href="../software-on-prem-manual/" class="nav-link"> <i class="icon-shell" aria-hidden="true"></i> Fully manual </a> </li> </ul>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.
If your VM has Internet or Yum connectivity, you must provide a VM with the following pre-installed:
yugabyte user, updating the file descriptor settings via ulimits, and so on.Take the time now to prepare the VM.
| 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 |
If your VM doesn't have Internet or Yum connectivity, you must provide to YBA a VM with the following pre-installed:
yugabyte user, updating the file descriptor settings via ulimits, and so on.Take the time now to prepare the VM.
| 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 |