- Overview
- Requirements
- Installation
- Post-installation
- Migration and upgrade
- Upgrading Automation Suite on EKS/AKS
- Migration options
- Step 1: Moving the Identity organization data from standalone to Automation Suite
- Step 2: Restoring the standalone product database
- Step 3: Backing up the platform database in Automation Suite
- Step 4: Merging organizations in Automation Suite
- Step 5: Updating the migrated product connection strings
- Step 6: Migrating standalone Insights
- Step 7: Deleting the default tenant
- B) Single tenant migration
- Monitoring and alerting
- Cluster administration
- Product-specific configuration
- Troubleshooting
Accessing Automation Suite
Enabling kubectl
Before running any kubectl commands, make sure you have downloaded and installed kubectl on your client machine. This allows you to run commands for retrieving passwords and configuration details for the cluster.
Managing certificates
The installation process generates self-signed certificates on your behalf. You should replace them with certificates signed by a trusted Certificate Authority (CA) as soon as installation completes.
For instructions, see Managing certificates.
If you try to access the cluster with a web browser, and the certificates are not from a trusted CA, then you will see a warning in the browser. You can rectify this by importing and trusting the cluster SSL certificate on the client computer running the browser.
To manage certificates, take the following steps:
-
To retrieve the current certificate, run the following command:
kubectl get secret -n istio-system istio-ingressgateway-certs -o jsonpath='{.data.ca\.crt}' | base64 --decode | openssl x509 -text -nooutkubectl get secret -n istio-system istio-ingressgateway-certs -o jsonpath='{.data.ca\.crt}' | base64 --decode | openssl x509 -text -noout -
To update the certificates, see Managing certificates.
Accessing Automation Suite general interface
You need to accept the self-signed certificate in the web browser to be able to access a cluster that is still configured with self-signed certificates.
The general-use Automation Suite user interface serves as a portal for both organization administrators and organization users. It is a common organization-level resource from where everyone can access all of your Automation Suite areas: administration pages, platform-level pages, product-specific pages, and user-specific pages.
To access Automation Suite, take the following steps:
-
Go to the following URL:
https://<FQDN> -
Switch to the Default organization.
-
The username is orgadmin.
-
Retrieve the password using the following command:
kubectl get secret platform-service-secrets -n uipath -o jsonpath='{.data.identity\.hostAdminPassword}' | base64 --decode ; echokubectl get secret platform-service-secrets -n uipath -o jsonpath='{.data.identity\.hostAdminPassword}' | base64 --decode ; echoNote:Using the same command to retrieve the organization admin and the host admin passwords is by design.
This is because the two passwords are initially the same. If Change password on the first login is set to Required at the host level, the organization administrator must set a new password when they log in for the first time.
Accessing host administration
The host portal is for system administrators to configure the Automation Suite instance. The settings that you configure from this portal are inherited by all your organizations, and some can be overwritten at the organization level.
To access host administration, take the following steps:
-
Go to the following URL:
https://${INPUT_JSON_FQDN} -
Switch to the Host organization.
-
The username is admin.
-
Retrieve the password using the following command:
kubectl get secret platform-service-secrets -n uipath -o jsonpath='{.data.identity\.hostAdminPassword}' | base64 --decode ; echokubectl get secret platform-service-secrets -n uipath -o jsonpath='{.data.identity\.hostAdminPassword}' | base64 --decode ; echoNote:Using the same command to retrieve the organization admin and the host admin passwords is by design.
This is because the two passwords are initially the same. If Change password on the first login is set to Required at the host level, the organization administrator must set a new password when they log in for the first time.
Accessing ArgoCD
You can use the ArgoCD console to have an overview of the cluster, configurations, applications status, and health, all via a user-friendly UI.
To access the ArgoCD account using a username and password, take the following steps:
-
Access the following URL:
https://alm.${CONFIG_CLUSTER_FQDN}. -
Enter the following username: admin.
-
Access your password:
kubectl -n argocd get secret argocd-initial-admin-secret -o jsonpath="{.data.password}" | base64 -d ; echokubectl -n argocd get secret argocd-initial-admin-secret -o jsonpath="{.data.password}" | base64 -d ; echo
Accessing monitoring
Automation Suite uses Prometheus, Grafana, and Alert Manager to provide cluster management tools out of the box. This helps you manage the cluster and access monitoring and troubleshooting.
For details on how to use monitoring tools in Automation Suite, see Using the monitoring stack.
You can access the Automation Suite monitoring tools individually using the following URLs:
| Application | Tool | URL | Example |
|---|---|---|---|
| Metrics | Prometheus | https://monitoring.<FQDN>/metrics | https://monitoring.automationsuite.mycompany.com/metrics |
| Dashboard | Grafana | https://monitoring.<FQDN>/grafana | https://monitoring.automationsuite.mycompany.com/grafana |
| Alert Management | Alert Manager | https://monitoring.<FQDN>/alertmanager | https://monitoring.automationsuite.mycompany.com/alertmanager |
Authentication
To access Prometheus and Alert Manager, the username is admin.
To retrieve the password for Prometheus and Alert Manager, use the following command:
kubectl get secret -n uipath dex-static-credential -o jsonpath='{.data.password}' | base64 -d ; echo
kubectl get secret -n uipath dex-static-credential -o jsonpath='{.data.password}' | base64 -d ; echo
To access Grafana dashboard, the username is admin.
To retrieve the password for Grafana, use the following command:
kubectl get secret -n monitoring grafana-creds -o jsonpath='{.data.admin-password}' | base64 -d ; echo
kubectl get secret -n monitoring grafana-creds -o jsonpath='{.data.admin-password}' | base64 -d ; echo
Accessing service database connection strings
You can access the database connection strings for each service as follows:
kubectl -n uipath get secret aicenter-secrets -o jsonpath='{.data.sqlConnectionString}' | base64 --decode
kubectl -n uipath get secret orchestrator-secrets -o jsonpath='{.data.sqlConnectionString}' | base64 --decode
kubectl -n uipath get secret automation-hub-secrets -o jsonpath='{.data.sqlConnectionString}' | base64 --decode
kubectl -n uipath get secret automation-ops-secrets -o jsonpath='{.data.sqlConnectionString}' | base64 --decode
kubectl -n uipath get secret insights-secrets -o jsonpath='{.data.sqlConnectionString}' | base64 --decode
kubectl -n uipath get secret platform-service-secrets -o jsonpath='{.data.sqlConnectionString}' | base64 --decode
kubectl -n uipath get secret test-manager-secrets -o jsonpath='{.data.sqlConnectionString}' | base64 --decode
kubectl -n uipath get secret aicenter-secrets -o jsonpath='{.data.sqlConnectionString}' | base64 --decode
kubectl -n uipath get secret orchestrator-secrets -o jsonpath='{.data.sqlConnectionString}' | base64 --decode
kubectl -n uipath get secret automation-hub-secrets -o jsonpath='{.data.sqlConnectionString}' | base64 --decode
kubectl -n uipath get secret automation-ops-secrets -o jsonpath='{.data.sqlConnectionString}' | base64 --decode
kubectl -n uipath get secret insights-secrets -o jsonpath='{.data.sqlConnectionString}' | base64 --decode
kubectl -n uipath get secret platform-service-secrets -o jsonpath='{.data.sqlConnectionString}' | base64 --decode
kubectl -n uipath get secret test-manager-secrets -o jsonpath='{.data.sqlConnectionString}' | base64 --decode