vRealize Code Stream uses designated ports for communication and data access.

Although vRealize Code Stream uses only port 443 for communication, there might be other ports open on the system. Because open, unsecure ports can be sources of security vulnerabilities, review all open ports on your system and ensure that only the ports that are required by your business applications are open.

vRealize Automation Appliance

The following ports are used by the vRealize Automation appliance.

Table 1. Incoming Ports for the vRealize Automation appliance

Port

Protocol

Comments

22

TCP

Optional. SSH.

80

TCP

Optional. Redirects to 443.

111

TCP, UDP

RPC

443

TCP

Access to the vRealize Automation console and API calls.

5480

TCP

Access to virtual appliance Web management interface

5480

TCP

Used by Management Agent

5488, 5489

TCP

Internal. Used by vRealize Automation appliance for updates.

4369, 25672,5671,5672

TCP

RabbitMQ messaging

8230, 8280, 8281

TCP

Internal vRealize Orchestrator instance

8444

TCP

Console proxy communication for vSphere VMware Remote Console connections

Table 2. Outgoing Ports for the vRealize Automation Appliance

Port

Protocol

Comments

25, 587

TCP, UDP

SMTP for sending outbound notification emails

53

TCP, UDP

DNS

67, 68, 546, 547

TCP, UDP

DHCP

80

TCP

Optional. For fetching software updates. Updates can be downloaded separately and applied.

110, 995

TCP, UDP

POP for receiving inbound notification emails

143, 993

TCP, UDP

IMAP for receiving inbound notification emails

123

TCP, UDP

Optional. For connecting directly to NTP instead of using host time.

902

TCP

ESXi network file copy operations and VMware Remote Console (VMRC) connections

5432

TCP, UDP

Optional. For communicating with an Appliance Database.

7444

TCP

Communication with SSO service over HTTPS

8281

TCP

Optional. For communicating with an external vRealize Orchestrator instance .

Other ports might be required by specific vRealize Orchestrator plug-ins that communicate with external systems. See the documentation for the vRealize Orchestrator plug-in.