This project provide a CDK app to deploy UiPath base architecture to AWS. The architecture deployed is shown below and is based on the UiPath architecture described in this blog post
No. This project provide a good quickstart to use UiPath on AWS, but you need to change it to your needs before using UiPath on AWS.
"Change" meaning for example: provide UiPath software+licence, use your EC2 keypair, set the correct TCP ports, check your desired hardware and software requirements and check if you prefer a different architecture (maybe you prefer an hybrid architecture where UiPath studio is installed on-premises)
Regarding UiPath servers, you may want (and I would recommend) that you prepare an image of your UiPath server, so that you can create them automatically and to be sure they're identical (no undocumented late night changes to fix an issue).
To do this you may want to use EC2 Image Builder, and this blog provide you a step by step example of EC2 Image Builder pipeline.
Sure! This project is based on UiPath architecture, but is generic and simple enough to be adjusted to different deployments of UiPath, other tools or your custom application. On the other hand, if you need to deploy something significantly different from the architecture shown above, such as a serverless or container architecture, you should look somewhere else (maybe check the examples below).
They're not here at the moment, because you can either:
- easily and quickly add them (for example, just duplicate/configure studio asg)
- use on-premises robots (running against on-premises applications) and connect them to UiPath orchestrator on AWS.
Read here what is CDK and then how to get started with CDK.
https://docs.aws.amazon.com/cdk/latest/guide/examples.html
https://github.com/aws-samples/aws-cdk-examples
Don't forget to check the API Reference, which also contains some examples: https://docs.aws.amazon.com/cdk/api/latest/docs/aws-construct-library.html
Sure! Don't forget to add CDK Intellisense to your IDE! Here you have some references: https://cdkworkshop.com/15-prerequisites/400-ide.html
This configuration allows studio instances to connect directly to windows orchestrator instances (i.e. bypassing NLB) in addition to use NLB, you may want to remove this option. I left this configuration because can be useful to test/debug communication between instances.
I tested successfully this architecture in different AWS regions. The only known issue is that using this architecture with multi-az RDS in North Virginia will cause subnet issue.
cdk synthemits the synthesized CloudFormation templatecdk deploydeploy this stack to your default AWS account/regioncdk diffcompare deployed stack with current state
