Provider configurations

After installing YugabyteDB Anywhere, the next step is to create provider configurations.

A provider configuration describes your cloud environment (such as its security group, regions and availability zones, NTP server, SSH credentials for connecting to VMs for provisioning, the Linux disk image to be used for configuring the nodes, and so on). The provider configuration is used as an input when deploying a universe, and can be reused for many universes.

{{<lead link="../yba-overview/#provider-configurations">}} Not sure what type of provider to use? Refer to Provider configurations. {{</lead>}}

{{< tip title="Automatic on-premises provisioning" >}}

If you are deploying on premises (private cloud), on-premises providers are created automatically when provisioning nodes. Refer to Automatically provision on-premises nodes.

{{< /tip >}}

Before you can deploy universes using YugabyteDB Anywhere, you must create a provider configuration.

To Deploy universes to	Create provider	Description
- Private cloud

• Bare metal/racks
• Cloud provider (limited SSH) | On-premises | Deploy universes to your own infrastructure, or to cloud providers where (due to security policies or other restrictions) you can't provide YBA with cloud permissions or SSH access to cloud VMs. Provides maximum flexibility. On-premises providers are created automatically when provisioning nodes. Refer to Automatically provision on-premises nodes. | | Cloud provider (full SSH) | AWS GCP Azure | Deploy universes to cloud providers where you can provide YBA with cloud permissions and SSH access to cloud VMs for full automation. Provides maximum automation. | | Kubernetes | Kubernetes VMware Tanzu OpenShift | Deploy universes on Kubernetes. |