- Overview
- Requirements
- Installation
- Post-installation
- Cluster administration
- Managing products
- Managing the cluster in ArgoCD
- Setting up the external NFS server
- Automated: Enabling the Backup on the Cluster
- Automated: Disabling the Backup on the Cluster
- Automated, Online: Restoring the Cluster
- Automated, Offline: Restoring the Cluster
- Manual: Enabling the Backup on the Cluster
- Manual: Disabling the Backup on the Cluster
- Manual, Online: Restoring the Cluster
- Manual, Offline: Restoring the Cluster
- Additional configuration
- Migrating objectstore from persistent volume to raw disks
- Monitoring and alerting
- Migration and upgrade
- Migration options
- Step 1: Moving the Identity organization data from standalone to Automation Suite
- Step 2: Restoring the standalone Orchestrator database
- Step 3: Backing up the platform database in Automation Suite
- Step 4: Merging organizations in Automation Suite
- Step 5: Updating the Orchestrator connection strings
- Step 6: Deleting the default tenant
- B) Single tenant migration
- 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 clear Redis data
- How to enable Istio logging
- How to manually clean up logs
- How to clean up old logs stored in the sf-logs bundle
- How to disable streaming logs for AI Center
- How to debug failed Automation Suite installations
- How to delete images from the old installer after upgrade
- How to automatically clean up Longhorn snapshots
- How to disable NIC 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
- First installation fails during Longhorn setup
- SQL connection string validation error
- Prerequisite check for selinux iscsid module fails
- Azure disk not marked as SSD
- Failure After Certificate Update
- Automation Suite not working after OS upgrade
- Automation Suite Requires Backlog_wait_time to Be Set 1
- Volume unable to mount due to not being ready for workloads
- RKE2 fails during installation and upgrade
- Failure to upload or download data in objectstore
- PVC resize does not heal Ceph
- Failure to Resize Objectstore PVC
- Rook Ceph or Looker pod stuck in Init state
- StatefulSet volume attachment error
- Failure to create persistent volumes
- Storage reclamation patch
- Backup failed due to TooManySnapshots error
- All Longhorn replicas are faulted
- Setting a timeout interval for the management portals
- Update the underlying directory connections
- Cannot Log in After Migration
- 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).
- Alarm Received for Failed Kerberos-tgt-update Job
- SSPI Provider: Server Not Found in Kerberos Database
- Login Failed for User <ADDOMAIN><aduser>. Reason: The Account Is Disabled.
- ArgoCD login failed
- 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
- After the Initial Install, ArgoCD App Went Into Progressing State
- MongoDB pods in CrashLoopBackOff or pending PVC provisioning after deletion
- Unexpected Inconsistency; Run Fsck Manually
- Degraded MongoDB or Business Applications After Cluster Restore
- Missing Self-heal-operator and Sf-k8-utils Repo
- Unhealthy Services After Cluster Restore or Rollback
- RabbitMQ pod stuck in CrashLoopBackOff
- Using the Automation Suite Diagnostics Tool
- Using the Automation Suite Support Bundle Tool
- Exploring Logs
Step 1: Preparing the AWS deployment
This page lists the steps you need to take before deploying Automation Suite to AWS.
The AWS deployment requires a moderate level of familiarity with AWS services.
If you are new to AWS, you can start by reading the following introductory materials to get familiar. They provide basic materials for how to design, deploy, and operate infrastructure and applications on the AWS Cloud.
This Quick Start also assumes familiarity with AWS Services listed in the Request resources quotas section of this guide. For a detailed diagram and description of the architecture, see:
If you don’t already have an AWS account, create one by following the step-by-step instructions. Your AWS account is automatically signed up for all AWS services. You are charged only for the services you use.
The following sections walk you through the steps you need to take to configure your AWS Account specific to the Automation Suite deployment requirements.
You need at least one EC2 key pair in the AWS account in the Region where you will deploy the Quick Start.
To create a key pair, see Amazon EC2 key pairs and Linux instances.
Take note of the key-pair name as it is needed during the deployment.
This Quick Start requires you to have established ownership of the parent domain under which the web application will be served. If you want to register a domain, see Registering a public domain.
If you have registered the domain using AWS Route 53, then the hosted zone is preconfigured, and no additional configuration is necessary.
Otherwise, you should set up a hosted zone in your AWS account, with the required name server, start of authority, CNAME, and text records. For further details on how to create a public hosted zone, see Working with public hosted zones.
WaitConditionHandle
resource in the routing stack. The Physical Id
of this resource is an URL. Execute a POST
request as described here.
If necessary, request service quota increases for the following resources. You might need to request increases if your existing deployment currently uses these resources and if this Quick Start deployment could result in exceeding the default quotas. The Service Quotas console displays your usage and quotas for some aspects of some services.
For more information, see What is Service Quotas? and AWS service quotas.
Resource |
Requirement |
---|---|
VPCs |
1 |
Subnets |
Up to 6 |
NAT gateways |
2 |
VPC endpoints |
1 |
Internet gateways |
1 |
Elastic IP addresses |
Up to 6 |
AWS Identity and Access Management (IAM) security groups |
1 |
IAM roles |
Up to 7 |
Auto Scaling groups |
Up to 2 |
Application Load Balancers |
Either 0 or 1 |
Network Load Balancers |
Either 1 or 2 |
Public certificate authorities (CA) |
1 |
Hosted zone |
1 |
RDS instances |
1 |
Bastion hosts |
1 |
Secrets |
4 |
Parameters in Parameter Store |
3 |
SSM documents |
Either 0 or 3 |
Lambda Functions |
3 |
Instance Profiles |
2 |
Security Groups |
3 |
In order for the Quick Start to work in a Region other than its default Region, all the services that are part of the deployment must also be supported in that Region.
For an up-to-date list of AWS Regions and the AWS services they support, see AWS Regional Services.
Unrecognized resource type
error, then Quick Start is not supported in that Region.
Before launching the Quick Start, you must sign in to the AWS Management Console with IAM permissions for the resources that the templates deploy. The AdministratorAccess managed policy within IAM provides sufficient permissions, although your organization may choose to use a custom policy with more restrictions.
For more information, see AWS managed policies for job functions.