- Overview
- Requirements
- Pre-installation
- Installation
- Post-installation
- Migration and upgrade
- Upgrading Automation Suite
- Migrating standalone products to Automation Suite
- Step 1: Restoring the standalone product database
- Step 2: Updating the schema of the restored product database
- Step 3: Moving the Identity organization data from standalone to Automation Suite
- Step 4: Backing up the platform database in Automation Suite
- Step 5: Merging organizations in Automation Suite
- Step 6: Updating the migrated product connection strings
- Step 7: Migrating standalone Orchestrator
- Step 8: Migrating standalone Insights
- Step 9: Deleting the default tenant
- Performing a single tenant migration
- Migrating between Automation Suite clusters
- Migrating from Automation Suite on EKS/AKS to Automation Suite on OpenShift
- Monitoring and alerting
- Cluster administration
- Performing database maintenance
- Configuring the FQDN post-installation
- Forwarding logs to external tools
- Switching to the secondary cluster manually in an Active/Passive setup
- Disaster Recovery: Performing post-installation operations
- Converting an existing installation to multi-site setup
- Guidelines on upgrading an Active/Passive deployment
- Guidelines on backing up and restoring an Active/Passive deployment
- Product-specific configuration
- Troubleshooting
Automation Suite on EKS/AKS installation guide
Accessing Automation Suite
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.
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:
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:
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:
To access the ArgoCD account using a username and password, take the following steps:
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 |
|
|
|
Dashboard |
Grafana |
|
|
|
Alert Management |
Alert Manager |
|
|
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 ; echokubectl get secret -n <uipath> dex-static-credential -o jsonpath='{.data.password}' | base64 -d ; echoTo 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 ; echokubectl get secret -n monitoring grafana-creds -o jsonpath='{.data.admin-password}' | base64 -d ; echoYou 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 --decodekubectl -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
