Automation Suite on Linux installation guide

Step 3: Post-deployment steps

Validating the installation​

1. Under CloudFormation > Stacks, you can find all of your deployments.
2. Select the stack you deployed, a status of CREATE_COMPLETE indicates the deployment has completed successfully.

Updating certificates​

Enabling FIPS 140-2​

Accessing the installer package​

Accessing the deployment outputs​

1. From the Stack you selected, select the Output tab on the top. On this tab, you should have access to all the information you need for next steps.

2. For any of the credentials, you can access them via the secrets link provided in the table. Select on the link and go to Retrieve Secret Value for the credentials.

   Key	Value	Description
   ArgoCD	https://alm.${CONFIG_CLUSTER_FQDN}	You can use the ArgoCD console to manage installed products.
   ArgoCD Secret	< See link in console >	Credentials for ArgoCD
   Automation Suite Secret	< See link in console >	Credentials for Automation Suite Portal
   Cluster Administration URL	https://${CONFIG_CLUSTER_FQDN}/uipath-management	Portal centralizes the resources required to complete an Automation Suite installation and perform common post-installation operations.
   Automation Suite URL	https://${CONFIG_CLUSTER_FQDN}	Automation Suite Portal
   Host Administration Portal	https://${CONFIG_CLUSTER_FQDN}	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.
   Host Administration Secret	< See link in console >	Credentials for Host Administration
   Interface Tour	Interface tour	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 the Automation Suite areas: administration pages, platform-level pages, service-specific pages, and user-specific pages.
   Rancher	https://monitoring.${CONFIG_CLUSTER_FQDN}	Automation Suite uses Rancher to provide cluster management tools out of the box. This helps you manage the cluster and access monitoring and troubleshooting.
   Dashboard (Grafana) Monitoring URL	https://monitoring.${CONFIG_CLUSTER_FQDN}/dashboard	The URL to dashboard (Grafana) monitoring tools
   Metrics (Prometheus) Monitoring URL	https://monitoring.${CONFIG_CLUSTER_FQDN}/metrics	The URL to metrics (Prometheus) monitoring tools.
   Alertmanager Monitoring URL	https://monitoring.${CONFIG_CLUSTER_FQDN}/alertmanager	The URL to Alertmanager monitoring tools.

Accessing the Cluster Administration portal​

Accessing the Automation Suite portal​

1. Go to the following URL: https://{CONFIG_CLUSTER_FQDN}.
2. Switch to the Default organization.
3. The username is orgadmin.
4. Retrieve the password by selecting the secrets link provided in the output table for AutomationSuiteSecret. Go to Retrieve Secret Value for the credentials.

Accessing host administration​

1. Go to the following URL: https://{CONFIG_CLUSTER_FQDN}.
2. Switch to the Host organization.
3. The username is admin.
4. Retrieve the password by selecting the secrets link provided in the output table for HostAdministrationSecret. Go to Retrieve Secret Value for the credentials.

Accessing ArgoCD​

1. Go to the following URL: https://alm.${CONFIG_CLUSTER_FQDN}.
2. The username is admin if you want to use the ArgoCD admin account, or argocdro if you want to use the ArgoCD read-only account.
3. Retrieve the password by selecting to the secrets link provided in the output table for ArgoCdSecret. Go to Retrieve Secret Value for the credentials.

Accessing the monitoring tools​

• Username: admin

• Password: to retrieve the password , run the following command:

  assignment

  kubectl get secrets/dex-static-credential -n uipath -o "jsonpath={.data['password']}" | base64 --decode
  kubectl get secrets/dex-static-credential -n uipath -o "jsonpath={.data['password']}" | base64 --decode
  

1. Run the following command by replacing newpassword with your new password:

   assignment

   password="newpassword"
   password=$(echo -n $password | base64)
   kubectl patch secret dex-static-credential -n uipath --type='json' -p="[{'op': 'replace', 'path': '/data/password', 'value': '$password'}]"
   password="newpassword"
   password=$(echo -n $password | base64)
   kubectl patch secret dex-static-credential -n uipath --type='json' -p="[{'op': 'replace', 'path': '/data/password', 'value': '$password'}]"
   

2. Run the following command to update the password:

   assignment

   ./bin/uipathctl manifest apply /opt/UiPathAutomationSuite/cluster_config.json --versions versions/helm-charts.json
   ./bin/uipathctl manifest apply /opt/UiPathAutomationSuite/cluster_config.json --versions versions/helm-charts.json
   

Accessing cluster VMs​

1. Navigate to EC2 and find your Automation Suite instance(s) depending if you deployed single-node or multi-node.

2. Find the public IP of the Bastion or instance you want to connect to.

   

3. Open a terminal and use SSH to connect to Bastion.

   assignment

   ssh -i <path_to_private_key> <username>@<bastion_ip>
   ssh -i <path_to_private_key> <username>@<bastion_ip>
   

4. From Bastion, you can access other nodes via SSH using the following command. The username must be the same as the one used to connect to Bastion.

   assignment

   ssh -i .ssh/private_key <username>@<node_address>
   ssh -i .ssh/private_key <username>@<node_address>
   

Performing cluster operations​

Using Systems Manager documents​

1. Go to the Systems Manager service.

   

2. In the left menu, select Documents.

   

3. In the Owned by me tab, select the SSM document you want to run.

   

4. Select the Execute automation button.

   

5. Fill in the parameters and select the Execute button.

   

UpdateAMIDocument​

Description​

Usage​

• ImageName (e.g.: RHEL-8.6*_HVM-20*) - If the ImageName parameter is provided and AMI that matches the ImageName will be set on the Automatic Scaling Groups;
• AmiId (e.g.: ami-032e5b6af8a711f30) - If provided, the AmiId takes precedence over ImageName and is set on the Automatic Scaling Groups.

RegisterAiCenter​

Description​

Usage​

OnDemandBackup​

Description​

Usage​

Execution logs​

GetAllBackups​

Description​

Usage​

Execution logs​

OnDemandRestore​

Description​

Usage​

Execution logs​

1. See the restore flow by selecting State machines.

   

2. Select OnDemandRestoreStateMachine.

   

3. Select the name of the running execution.

   

4. Select the step for which you want to check the execution logs and look in the output section for the CommandInformation.CommandId and copy it.

   

5. Go to the Run Command service.

   

6. In Command history, search for the command ID you copied earlier.

   

7. Select the instance ID.

   

8. In the output section, select CloudWatch Logs to see the full logs.