Skip to content

Network Requirements

This section describes the network requirements for Hyperscale Compliance. Ensure that you meet all the network requirements before you install the Hyperscale Compliance Engine.

The following are the inbound/outbound rules for the Hyperscale Compliance Engine:

Type (Inbound/Outbound) Port Reason
Inbound and Outbound 80 HTTP connections to/from the Hyperscale Compliance Engine to/from the Continuous Compliance Engines part of the Continuous Compliance Engine Cluster and to access the Hyperscale Compliance API.
Inbound and Outbound 443 HTTPs connections to/from the Hyperscale Compliance Engine to/from the Continuous Compliance Engines part of the Continuous Compliance Engine Cluster and to access the Hyperscale Compliance API.
Outbound 53 Connections to local DNS servers.
Inbound 22 SSH connections to the Hyperscale Compliance Engine host.

Hyperscale Compliance Engine Host Requirement on Linux

Type Host Requirement Explanation
User A user (hyperscale_os) with the following permissions are required:
  • Should have permissions to install docker and docker-compose.
  • Should be part of the ‘docker’ OS group or must have the permission to run docker and docker-compose commands.
  • Permission to run mount, unmount, mkdir, rmdir, and ping as a super-user with NOPASSWD.
This will be a primary user responsible to install and operate the Hyperscale Compliance.
Installation Directory There must be a directory on the Hyperscale Compliance Engine host where the Hyperscale Compliance can be installed. This is a directory where the Hyperscale Compliance tar archive file will be placed and extracted. The extracted artifacts will include docker images(tar archive files) and a configuration file(docker-compose.yaml) that will be used to install the Hyperscale Compliance.
Log File Directory An optional directory to place log files. This directory (can be configured via docker-compose.yaml configuration file) will host the runtime/log files of the Hyperscale Compliance Engine.
NFS Client Services NFS client services must be enabled on the host. NFS client service is required to be able to mount an NFS shared storage from where the Hyperscale Compliance Engine will be able to read the source files and write the target files. For more information, see NFS Server Installation.
Hardware Requirements Minimum:
8 vCPU, 16 GB of memory, 100GB data disk.

Recommended:
16 vCPU, 128GB of memory, 500GB data disk.
OS disk space: 50 GB