Deployment examples can be found here
The quickstart provisions all required infrastructure elements, configures them and then installs the UiPath Automation Suite on the EC2 instances.
Depending on the configuration being deployed, some components may not be provisioned. The total number of individual components is much larger and have been omitted for brevity.
The deployment uses AWS CloudFormation stacks to aggregate infrastructure elements together. These stacks are aggregated, nesting them in higher level stacks to provide functionality.
The ALB stack is nested inside the Routing stack to provide the routing functionality.
Client traffic on port 443, routed through the load balancer at the edge of the VPC, can be served by both server and agent instances. The client facing load balancer can be either an Application Load Balancer, or a Network Load Balancer.
Internally, an additional load balancer is deployed, to route kube-api and rke2 registration traffic. These requests can only be served by Server EC2 instances.
The compute used for the execution of the workloads are EC2 instances, deployed via AutoScaling groups. These are defined in the Server stack and fall into 2 major categories:
- Server instances
- Agent instances
The Launch Templates provide both the configuration and the initialization procedure, which allows the EC2 instances to automatically configure and join the existing cluster.
Each installation requires a cluster config json file containing all the configuration necessary to successfully join the existing cluster. The config file is stored as a secret in AWS Secrets Manager.