- Overview
- Requirements
- Installation
- Post-installation
- Cluster administration
- Monitoring and alerting
- Migration and upgrade
- Product-specific configuration
- Best practices and maintenance
- Troubleshooting
- How to Troubleshoot Services During Installation
- How to Uninstall the Cluster
- How to clean up offline artifacts to improve disk space
- How to disable TLS 1.0 and 1.1
- How to enable Istio logging
- How to manually clean up logs
- How to clean up old logs stored in the sf-logs bucket
- How to debug failed Automation Suite installations
- How to disable TX checksum offloading
- Unable to run an offline installation on RHEL 8.4 OS
- Error in Downloading the Bundle
- Offline installation fails because of missing binary
- Certificate issue in offline installation
- SQL connection string validation error
- Failure After Certificate Update
- Automation Suite Requires Backlog_wait_time to Be Set 1
- Cannot Log in After Migration
- Setting a timeout interval for the management portals
- Update the underlying directory connections
- Kinit: Cannot Find KDC for Realm <AD Domain> While Getting Initial Credentials
- Kinit: Keytab Contains No Suitable Keys for *** While Getting Initial Credentials
- GSSAPI Operation Failed With Error: An Invalid Status Code Was Supplied (Client's Credentials Have Been Revoked).
- Login Failed for User <ADDOMAIN><aduser>. Reason: The Account Is Disabled.
- Alarm Received for Failed Kerberos-tgt-update Job
- SSPI Provider: Server Not Found in Kerberos Database
- Failure to get the sandbox image
- Pods not showing in ArgoCD UI
- Redis Probe Failure
- RKE2 Server Fails to Start
- Secret Not Found in UiPath Namespace
- ArgoCD goes into progressing state after first installation
- Unexpected Inconsistency; Run Fsck Manually
- Missing Self-heal-operator and Sf-k8-utils Repo
- Degraded MongoDB or Business Applications After Cluster Restore
- Unhealthy Services After Cluster Restore or Rollback
- Using the Automation Suite Diagnostics Tool
- Using the Automation Suite support bundle
- Exploring Logs
The the following table describes the IAM roles and policies that the CloudFormation template creates:
| Role | Actions |
|---|---|
|
This role is used to copy objects between S3 buckets. It is a copy of the https://github.com/aws-quickstart/lambda-copyzips AWS repository initially used for the AWS QuickStart. File:
copy-zips.template.yaml |
|
|
The purpose of this role is to create and verify an ACM certificate using DNS validation and Route 53. It is a copy of the https://github.com/aws-quickstart/quickstart-aws-acm-certificate AWS repository used for the AWS QuickStart. File:
quickstart-aws-acm-certificate.template.yml |
|
|
This role serves as the value of the
DeliverLogsPermissionArn parameter in the
AWS::EC2::FlowLog resource type. Is it a copy
of the https://github.com/aws-quickstart/quickstart-aws-vpc
QuickStart repository.
File:
aws-vpc.template.yaml |
|
|
This role is used for various SSM documents (
AWS::SSM::Document), with the following purposes:
Note:
AutomationAssumeRole allows full access to Amazon SSN. For more information, see AmazonSSMFullAccess.
File:
ec2-management.template.yaml |
|
|
This role is used for the
OnDemandRestoreStateMachine resource
(AWS::StepFunctions::StateMachine). This
resource is used for the restore operation.
Note:
StateMachinesAssumeRole allows full access to Amazon SSN. For more information, see AmazonSSMFullAccess.
File:
ec2-management.template.yaml |
Uses the
AmazonSSMFullAccessmanaged policy.
|
|
This role is used for the following event rules (
AWS::Events::Rule):
The rules are for the terminate lifecycle action. File:
ec2-management.template.yaml |
|
|
This role is used for the
ObjectStorageBucketsCleanupFunction lambda function and provides utility for the object storage.
File:
external-storage.template.yaml |
|
|
This role is referenced in the following resources:
File:
uipath-sf.template.yaml |
Uses the
AmazonSSMManagedInstanceCore managed policy.
|
|
This role is used to modify the ASG processes during CF stack creation. File:
uipath-sf.template.yaml |
|
|
This role is used by the
FindAMIFunction lambda function.
File:
uipath-sf.template.yaml |
|
|
This role is used by the
CreateInputJsonFunction lambda function. The function
creates the configuration file for the Automation Suite
installation.
File:
uipath-sf.template.yaml |
|
|
This role is used by the
ComputeResourceSizeFunction lambda function. The
function validates that the input for resources is in accordance
with the hardware requirements.
File:
uipath-sf.template.yaml |
|
| Policy | Actions |
|---|---|
|
Policy for log access. |
|
|
Policy for lifecycle hook access. |
|
|
Policy for EC2 and ASG access. |
|
|
Policy for getting access to the QS S3 bucket. |
|
|
Policy for allowing access to the secret manager. |
|
|
Policy for allowing access to the secret manager. |
|
|
Policy for allowing access to SSM parameters. |
|
|
Policy for allowing access to external storage. |
|