Publish process from local to AWS EC2

Hi guys,

Trying to understand what i am doing wrong…
Let me explain…

Created EC2 Environment on AWS with Windows server. Instaled there UiPath Stuido with Orchestrator, for this server i have created machine, robot, environment etc… (as i did on my local which is working fine)

Now from ma local i want publish my code (process) to this aws machine, but how is possible to connect to this robot from my local (if on my locall, uipath assistant(robot) is attached to my local machine)

I would add only that whole process which i am doing on my local is working fine, but wondering if is possible login in my local computer to aws orchestrator account(service) and then run job from my my localc which will run on AWS machine (EC2)

Regards, Luke

Orchestrator / Robot / Studio is no different in cloud infrastructure from your local instance.

Your UiPath Assistant / Robot service can only be connected to one Orchestrator at a time. You can do one of two things

  1. Disconnect from your local Orchestrator and connect to the AWS Orchestrator.
  2. Manually Upload the nuGet to the AWS Orchestrator.

Thank for you replay,

The thing is that machine name is different on my local and on ec2 aws server
So if i want publish my code to orchestartor aws i am receiving error message:
Error: Publish of Process project to Orchestrtor failed. The machine key is linked to other machine


I thought that i can have server (as ec2 in aws) where code will be executed, and i and for example two my team member can publish code to AWS server from local computer… I think that i missed something…

For clarity can you confirm that I have the correct understanding of your current infrastructure.

You have two hosts:

  • Host L (local)
  • Host A (AWS EC2 Instance)

On both of these machines you have installed Orchestrator, Studio, and Robot?

If you are using a Standard Machine the name of the Machine must match the hostname of the host in which the Robot is connected from. So if you have two hosts where Studio or Robot Service is installed then you should have two Machine records in Orchestrator each having a unique Machine Key.

If you are leveraging Machine Template for use with Floating Robots you would have one Machine key for each group of hosts.

In order to publish a process / package to Orchestrator you must

A) Successfully connect your local Robot to an Orchestrator instance and publish directly from Studio.
B) Manually Upload the nuGet package to Orchestrator by the WebUI or another location if you’ve configured Orchestrator differently from the default setup.

Hello Tim,
Yes. your understanding is correct regarding to hosts.

I think i resolved my problem.
I am using UiPath Community cloud version - so i have 1 licence for Orchestrator.
When Robot was connected on AWS host maching (licence was attached to AWS machine) - so i cound not publish my code from my local even if Robot was connected -> Robot status was Connected but Unlicensed

So on AWS Machine i Disconnected Robot
Then i connected with Robot on my local, next i have published my Code from local, then i disconnected robot on my local, Connected with Robot on AWS, and from my local i run job with published process - like this i could run test(process) on my AWS Machine

Correct me if i am wrong - all these steps seems crazy and awkward in teamwork…
Or still i am doing something wrong

Regards, Luke

If my previous post make sense then…

I came up with idea.
If i have one license and publish operation is possible only from one host so maybe souce code will be on AWS machine as git repository, so all team member can clone this code on their local host (computer) and locally they can work and all changes can be push on git repository, then on AWS machine they can login there, get latest code, and do publish their process from UiPath Studo on AWS machine.

Does it make sense and is it a kind of solution?

Regards, Luke

Okay, so it sounds like my previous assumption is not correct then. Orchestrator is another component, in your last two replies it sounds like you haven’t installed Orchestator in either your local machine or in the AWS host and are solely using Cloud Orchestrator Community.

If that is the the case you will then only have licenses for the following unless you requested an Enterprise Trial or have an active Enterprise license
2 Attended
1 Unattended
2 Studio Named

With a classic / non-concurrent runtime, as soon as you create a Robot record a license is consumed

So if you have more user then available licenses you will need to be adding/removing Robots to connect and license them.

If the users will remain the same but each user could use more than one computer, you would want to use a Machine Template instead of a Standard Machine, and so long as the user is disconnecting the UiPath Assistant / Studio / UiRobot Service it will free up the robot to be connect by that user on another computer that is using the same machine key associated with the machine record that is defined in the Robot record.

I think it would sense if you were to lay out what your use case is and how your team functions

  • These team members is the intent only to develop projects and not run them? Or are these same individuals the ones that will be running them in an attended fashion?

  • Are your processes intended to be ran in an attended state or unattended?

  • What is the purpose of the EC2 Host in your setup? If it’s to run the processes in either Attended or Unattended, you shouldn’t need to connect / disconnect it all the time. You could ether have this registered with 1 Unattended Robot or 2 Attended Robots. You would then solely use Studio licenses on your local machine where you are developing the processes.

If you have multiple users working on the same project or at least need access to the same source code, it makes sense to have some sort of code repository, if it makes sense for you to host that on your AWS EC2 instance, I don’t see why not, but you could just as easily use something like or

If you have more users then you have licenses for you will need to juggle them or purchase an Enterprise license in which case you could I think still purchase stand-alone Studio/Robot [External] licenses or licenses managed via Orchestrator. I’m not up to speed on the new licensing model so take that like a grain of salt.

1 Like

Thank you for your comprehensive answer :slight_smile:

Now all make sense, but apart of that… I have to understand the difference between the types of robots (attended, unattended, studio) and reflect it somehow on the example (because this is the best way for me to understand)

Thank you again for your help

Regards, Luke

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.