Firewall and network proxy requirements

All communications for Robocorp applications are outbound: there is no need to open any incoming firewall rules.

Robocorp Assistant and Robocorp Workforce Agent

All communications are standard HTTPS (TLS 1.2) so, in most cases, no special firewall setup is needed.

The following list is relevant if your outbound connections are controlled by a firewall.

Note: We expect the outgoing request headers to be unaltered; we have hit some rare cases of proxies stripping request headers, so please find out your settings and contact us as needed.

Robocorp applications that handle the execution of robots use the following endpoints for communication with Robocorp Control Room in the EU region:

Service  Host name  Port & technology  Robocorp Workforce Agent  Robocorp Assistant  Description 
Control Room API 443 / HTTPS
AWS API Gateway 
 X  X Several services such as Vault and Assistants 
Control Room API api.eu1.robocloud.eu443 / HTTPS
AWS API Gateway 
 X  X Workforce Agent linking and service access during runs
Robocorp Worker
Control Websocket 443 / HTTPS
AWS API Gateway 
 X    Worker control channel (Websocket) 
Task Data API task-data-api.eu1.robocloud.eu443 / HTTPS
AWS API Gateway 
 X  X Data processed by robots such as Work Items and Run Artifacts 
Telemetry API 443 / HTTPS
AWS API Gateway 
 X  X Technical metrics, error reports, usage information 
Robocorp 443 / HTTPS  X  X Tool dependencies
Feedback API 443 / HTTPS
AWS API Gateway 
 O  O Contact Robocorp dialog 
Amazon S3   443 / HTTPS  X  X Amazon S3 is accessed with pre-signed requests.
AWS IP ranges 

X = Required, O = Optional Last updated 2022-04-26

Robocorp VS Code extensions and RCC

Development and execution tools need to contact the following domains to load packages, self-update, etc. Make sure they are accessible for outbound traffic:

Service  Host name  Port & technology  Description 
Robocorp Services and Tools* 443 / HTTPSTool downloads, auto-updates, technical metrics, error reports, usage information 
Control Room API 443 / HTTPS Robocorp Control Room services like Vault 
Amazon S3*.amazonaws.com443 / HTTPS Package downloads
For more strict limitations see AWS IP address ranges 
conda-forge packages*.anaconda.org443 / HTTPS Download robot dependencies 
443 / HTTPS Download robot dependencies 
npm*.npmjs.org443 / HTTPS Download robot dependencies 

Last updated 2021-05-12
Note that package managers like pip, conda-forge and npm as well as the implementations of automation processes can re-direct file downloads or may need access to other network sites, so a fully comprehensive list is impossible to state here.


For the tooling to work behind a local proxy, the HTTP_PROXY and HTTPS_PROXY settings are needed on the system level.

Your IT -department should do this setting, so please consult them for help, just like the rest of the items on this page.

When working behind a local proxy, the proxy settings are often only defined for the browser. When the proxy settings are not on the system level, the tooling cannot check HTTPS certificates and will fail the standard environment setups. Essentially every tool in the toolchain expects HTTPS traffic to function.


In the Windows Command Line environment, you can use the below commands to set HTTP and HTTPS proxy.

set http_proxy=protocol://ip:port set https_proxy=protocol://ip:port

The commands below are for cases where if you have a local SOCKS5 proxy:

set http_proxy=socks5:// set https_proxy=socks5://

To test if the settings are valid, you can echo these variables to confirm.

echo %http_proxy% echo %https_proxy%

On Windows 10 or Windows Server 2019 or later, you can also test the functionality and HTTPS traffic using a simple curl command

curl --cert-status

If the output is other than: Used to testing connections ...things are not set up correctly.

MacOS & Linux

Same as for Windows above, but commands are a bit different

export http_proxy=socks5:// # Set HTTP Proxy export https_proxy=socks5:// # Set HTTPS Proxy export all_proxy=socks5:// # Set HTTP & HTTPS Proxy
Last edit: January 24, 2021