Prerequisite checks

It is recommended to run prerequisite checks to ensure that you properly configured the cloud infrastructure and to validate input.json before starting the Automation Suite installation.

You can run a prerequisite check using the command. By default, this command verifies all the prerequisites. If you want to exclude components from the execution, use the --excluded flag.

The checks in the following table are run on each node:

Check	Description
SQL Connection	Validates that Automation Suite can successfully connect to SQL server for UiPath products and shared services (such as Identity, Portal, Org Mamagement, etc.) using the SQL connection strings provided in input.json. This is mandatory for a successful installation.
SQL DB roles	Validates the necessary roles and permissions required by UiPath products. This is mandatory for a successful installation.
SQL DB compatibility	Validates SQL DB compatibility requirements.
FQDN resolution	Validates that the FQDN and the sub-domains are successfully resolvable.
Object Storage API	Validates that Object store APIs are accessible based on access information provided in input.json. This is mandatory for a successful installation of UiPath Services.
Cache / Redis	Validates the connection to Cloud Redis or ElastiCache. This is mandatory for a successful installation.
Capacity	Validates you have minimum worker nodes' CPU and RAM capacity based on products enabled in input.json.
Storage Class	Validates the storage classes for File Storage are configured as required for Automation Suite Robots.
Optional Components	Validates that your cluster has components that you chose to exclude from the Automation Suite installation.
Ingress	Validates that the cluster ingress is configured correctly and the FQDN URL requests can reach UiPath products.
Network Policies	Checks if network policies configured in Automation Suite are compatible with the cluster.
Registry	Validates that Automation Suite can access the UiPath docker registry. This is mandatory for a successful installation.
Cluster Connectivity	Validates whether the cluster communication is configured properly: Between two random pods completed Between pod to a multinode ClusterIP Between pod to a multinode ClusterIP without a clusterIP Between pod to a multinode ClusterIP using HostNetwork Between pod to a multinode ClusterIP without a clusterIP set using HostNetwork Between two pods colocated on the same node via ClusterIP