Skip to main content
Cloud Manager 3.7
A newer release of this product is available.

Cloud Manager host requirements

Contributors netapp-bcammett

If you install Cloud Manager on your own host, then you must verify support for your configuration, which includes operating system requirements, port requirements, and so on.

Note You can install Cloud Manager on your own host in GCP, but not in your on-premises network. Cloud Manager must be installed in GCP in order to deploy Cloud Volumes ONTAP in GCP.
A dedicated host is required

Cloud Manager is not supported on a host that is shared with other applications. The host must be a dedicated host.

Supported AWS EC2 instance types
  • t2.medium

  • t3.medium (recommended)

  • m4.large

  • m5.xlarge

  • m5.2xlarge

  • m5.4xlarge

  • m5.8xlarge

Supported Azure VM sizes

A2, D2 v2, or D2 v3 (based on availability)

Supported GCP machine types

A machine type with at least 2 vCPUs and 4 GB of memory.

Supported operating systems
  • CentOS 7.2

  • CentOS 7.3

  • CentOS 7.4

  • CentOS 7.5

  • Red Hat Enterprise Linux 7.2

  • Red Hat Enterprise Linux 7.3

  • Red Hat Enterprise Linux 7.4

  • Red Hat Enterprise Linux 7.5

    The Red Hat Enterprise Linux system must be registered with Red Hat Subscription Management. If it is not registered, the system cannot access repositories to update required 3rd party software during Cloud Manager installation.

    Cloud Manager is supported on English-language versions of these operating systems.

Hypervisor

A bare metal or hosted hypervisor that is certified to run CentOS or Red Hat Enterprise Linux
Red Hat Solution: Which hypervisors are certified to run Red Hat Enterprise Linux?

CPU

2.27 GHz or higher with two cores

RAM

4 GB

Free disk space

50 GB

Outbound internet access

Outbound internet access is required when installing Cloud Manager and when using Cloud Manager to deploy Cloud Volumes ONTAP. For a list of endpoints, see Networking requirements for Cloud Manager.

Ports

The following ports must be available:

  • 80 for HTTP access

  • 443 for HTTPS access

  • 3306 for the Cloud Manager database

  • 8080 for the Cloud Manager API proxy

    If other services are using these ports, Cloud Manager installation fails.

    Note There is a potential conflict with port 3306. If another instance of MySQL is running on the host, it uses port 3306 by default. You must change the port that the existing MySQL instance uses.

    You can change the default HTTP and HTTPS ports when you install Cloud Manager. You cannot change the default port for the MySQL database. If you change the HTTP and HTTPS ports, you must ensure that users can access the Cloud Manager web console from a remote host:

    • Modify the security group to allow inbound connections through the ports.

    • Specify the port when you enter the URL to the Cloud Manager web console.