Read and Review Automation Anywhere Documentation

Automation 360

Close Contents


Open Contents

Ports, protocols, and firewall requirements

  • Updated: 2022/05/20
    • Automation 360 v.x
    • Install
    • RPA Workspace

Ports, protocols, and firewall requirements

View the default and configurable firewall, port, and protocol requirements for Automation Anywhere deployment.

  • Add Automation Anywhere to the Windows Firewall exception list. Follow the steps as directed by Microsoft for your Windows version.
  • Configure the firewall rules and add the Control Room URLs to safe recipients list.

Refer to the following tables for lists of required ports and their use.

Control Room

Warning: It is critical that communication between the Control Room servers is properly protected. These Control Room servers contain security sensitive information that is not encrypted. Therefore, excluding the Control Room servers, you should block all other network hosts from accessing the listed Automation Anywhere cluster communication ports.
Protocol Port Usage Clients

Web browsers



Web Socket

Web browsers

TCP 5672 Cluster Messaging Control Room Services
TCP 47100 - 47200 Cluster Messaging and Caching Control Room Services
TCP 47500 - 47598 Cluster Messaging and Caching Control Room Services
HTTP 47599 Elasticsearch Control Room Services
TCP 47600 Elasticsearch Control Room Services

4569 - 4571

Automation Anywhere Robotic Interface Web browsers

5800 - 5900

Automation Anywhere Robotic Interface Control Room Services

Internal ports for localhost services

Note that the following internal ports are used for Automation 360 localhost services:
Port Protocol
4567 - 4571 HTTPS REST
5678 - 5707 gRPC

Data center ports and protocols for Automation 360

Configure each of the data center components that are required for Control Room integration. In the image below, Control Room components are shown in orange and data center components provided by your organization are shown in blue.

Data center components labeled with port numbers for communications with Control Room

Default ports are listed for illustration purposes. Some ports can have alternative port numbers specified during Control Room installation. Some port numbers can be modified after Control Room installation. Active Directory ports are listed as an example of an enterprise identity management.

The configured ports are bidirectional (inbound and outbound) for Control Room.

All three objects, the web browser, Bot agent, and external applications communicate directly with the Control Room. A user logs into the Control Room through a browser, to do tasks, such as creating users, or bot related tasks, such as creating, deploying, and scheduling bots. Bot agent establishes a connection with the Control Room on registration and keeps it alive in order to receive bot deployments from the Control Room. External applications talk to the Control Room directly through the Control Room APIs to perform tasks such as creating users or running bots.

Data center object Port default Protocol default Notes
Load balancer
  • 443
  • 80
HTTP, HTTPS, and web socket
  • 443
  • 80
HTTP, HTTPS, and web socket
Enterprise identity management

Example: Active Directory ports

  • 389
  • 636
  • 3268
  • 3269
  • 88
  • TCP (LDAP)
  • TCP (LDAP Global controller)
  • TCP (LDAP Global controller SSL)
  • TCP/UDP (Kerberos)
File share with Microsoft Server Message Block (SMB) protocol (SMB 2.0 and SMB 3.0)