Allow Automation Anywhere communications ports

As part of the Automation 360 Cloud prerequisites, you must allow Automation Anywhere communications ports and protocols from the customer network.

Cloud communications ports

You can set the following connection modes between the customer network and the Control Room:

Note:

You do not need an inbound connection for a regular bot execution. The inbound connection is only required when you have configured any integrations to: Git repository, On-Premises external key vault, or SIEM server with your cloud-hosted Control Room.
You must open the Cloud communications ports to unidirectional (outbound connection) to transmit traffic from the customer network to the cloud-hosted Control Room.

The following table describes the required Cloud communications ports:


Automation 360 Cloud communications ports
From	To	Port	Protocol	Connection type
Bot Agent (customer hosted)	Control Room (Automation Anywhere hosted)	443	HTTPS	Outbound
Bot Agent (customer hosted)	Control Room (Automation Anywhere hosted)	443	WebSocket	Outbound
Access to Control Room through browser	Control Room (Automation Anywhere hosted)	443	HTTPS	Outbound
Control Room (Automation Anywhere hosted) where Control Room connects from these Automation 360 IP addresses for external integrations	Third-party Keystore (customer hosted and optional)	443	HTTPS	Inbound
Control Room (Automation Anywhere hosted) where Control Room connects from these Automation 360 IP addresses for external integrations	Git Repository (customer hosted and optional)	443	HTTPS	Inbound
Control Room (Automation Anywhere hosted) where Control Room Room connects from these Automation 360 IP addresses for external integrations	SIEM server (customer hosted and optional)	443	HTTPS	Inbound