The following system resources are required to install vRealize Automation and VMware Identity Manager.

vRealize Easy Installer supports
  • vRealize Automation 8.0.0 and later.
  • vRealize Suite Lifecycle Manager 8.0.0 and later
  • VMware Identity Manager 3.3.1 (for import only) and later.
Note: vRealize Automation 8 does not support nested virtual environments, such as ESX > ESX > vRA.
Requirements vRealize Suite Lifecycle Manager VMware Identity Manager vRealize Automation
Medium Profile Extra Large Profile
Total Disk Size 78 GB 60 GB 236 GB (Only for single node Installation) 236 GB (Only for single node Installation)
Virtual CPU 2 8 12 24
Memory/RAM Size 6 GB 16 GB 42 GB 96 GB
System Partition 10 GB 8 GB 50 GB 50 GB
Data Partition 50 GB 144 GB 144 GB
Metrics Partition 20 GB 20 GB
Logs Partition 22 GB 22 GB
Swap Size 8 GB 6 GB
Tomcat Partition 10 GB
var Partition 10 GB
db Partition 10 GB 10 GB
Maximum Network Latency 5 ms between each cluster node 5 ms between each cluster node
Maximum Storage Latency 20 ms for each disk IO operation from any vRA node 20 ms for each disk IO operation from any vRA node

For more information on configuration limits, see the VMware Configuration Maximums tool.

Hardware Requirements

  • vRealize Automation hardware requirements
    Table 1. Hardware Requirements
    Component vCPU Memory (GB) Storage (GB)
    vRealize Lifecycle Manager 2 6 48
    VMware Identity Manager

    Note: For more information on the hardware requirements for VMware Identity Manager, see Upgrading to VMware Identity Manager documentation.
    		8 16 100
    vRealize Automation Medium profile: 12

    XL profile: 24

    		 Medium profile: 42

    XL Profile: 96

    		 Medium profile: 222

    XL profile: 222
  • Specifications for Workspace ONE Access are based on the number of users in the directories. For more information, see System and Network Configurations Requirements.
Note: To learn more about the hardware resizing of Workspace ONE Access through Lifecycle Manager, see Hardware Sizing for Workspace ONE Access.

Load Balancer Requirements

Network Requirements

vRealize Automation requires:
  • Single, static IPv4 and Network Address
  • Reachable DNS server set manually
  • Valid, Fully qualified domain name, set manually that can be resolved both forward and in reverse through the DNS server
Note: IP address change or hostname change after installation is not supported and results in a broken setup that is not recoverable.

Ports and Protocols Requirements

vRealize Automation is accessed over port 443. The 443 port is secured with a self-signed certificate that is generated during the installation. When using an external load balancer, it must be set up to balance on port 443. The table provides an overview of the Ports and Port number used for vRealize Automation. For more information on Ports and Protocols for vRealize Automation where you can view port information of various VMware products in a single dashboard and also export an offline copy of the selected data, see VMware Ports and Protocols.

Protocol Port Number
TCP 80
TCP 443
TCP 2379
TCP 2380
TCP 6443
TCP 8008
TCP 10250
TCP 16000
TCP 20849
TCP 30333
TCP 30821
TCP 31090
UDP 500
UDP 4500
UDP 8285
ESP
AH
Table 2. Requirement for Ports for Product and Integration Communications
Product or Integration TCP Port Number
vRealize Automation Appliance 5480, 443, 22
Identity Manager Appliances 8443, 443,

9999, 9898, 9000, 9694 (Use these for a cluster)
vCenter Server Instances 443
ESXi Host Instances 443

For more information on ports, see vRealize Suite Lifecycle Manager Ports