Install the Connector on an existing Linux host that has internet access

Contributors netapp-bcammett

The most common way to create a Connector is directly from Cloud Manager or from a cloud provider’s marketplace. But you have the option to download and install the Connector software on an existing Linux host in your network or in the cloud. These steps are specific to hosts that have internet access.

Note If you want to create a Cloud Volumes ONTAP system in Google Cloud, then you must have a Connector that’s running in Google Cloud as well. You can’t use a Connector that’s running in AWS, Azure, or on-prem.

Verify host requirements

The Connector software must run on a host that meets specific operating system requirements, RAM requirements, port requirements, and so on.

A dedicated host is required

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


4 cores or 4 vCPUs


16 GB

AWS EC2 instance type

An instance type that meets the CPU and RAM requirements above. We recommend t3.xlarge.

Azure VM size

An instance type that meets the CPU and RAM requirements above. We recommend DS3 v2.

GCP machine type

An instance type that meets the CPU and RAM requirements above. We recommend n1-standard-4.

The Connector is supported in Google Cloud on a VM instance with an OS that supports Shielded VM features

Supported operating systems
  • CentOS 7.6

  • CentOS 7.7

  • CentOS 7.8

  • CentOS 7.9

  • Red Hat Enterprise Linux 7.6

  • Red Hat Enterprise Linux 7.7

  • Red Hat Enterprise Linux 7.8

  • Red Hat Enterprise Linux 7.9

    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 Connector installation.

    The Connector is supported on English-language versions of these operating systems.


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?

Disk space in /opt

100 GiB of space must be available

Disk space in /var

20 GiB of space must be available

Outbound internet access

Outbound internet access is required to install the Connector and for the Connector to manage resources and processes within your public cloud environment. For a list of endpoints, see Networking requirements for the Connector.

Install the Connector

After you verify that you have a supported Linux host, you can obtain the Connector software and then install it.

Required privileges

Root privileges are required to install the Connector.

About this task
  • The installation installs the AWS command line tools (awscli) to enable recovery procedures from NetApp support.

    If you receive a message that installing the awscli failed, you can safely ignore the message. The Connector can operate successfully without the tools.

  • The installer that is available on the NetApp Support Site might be an earlier version. After installation, the Connector automatically updates itself if a new version is available.

  1. Download the Cloud Manager software from the NetApp Support Site, and then copy it to the Linux host.

    For help with connecting and copying the file to an EC2 instance in AWS, see AWS Documentation: Connecting to Your Linux Instance Using SSH.

  2. Assign permissions to run the script.

    chmod +x
  3. Run the installation script.

    If you have a proxy server, you will need to enter the command parameters as shown below. The installer doesn’t prompt you to provide information about a proxy.

     ./ [silent] [proxy=ipaddress] [proxyport=port] [proxyuser=user_name] [proxypwd=password]

    silent runs the installation without prompting you for information.

    proxy is required if the host is behind a proxy server.

    proxyport is the port for the proxy server.

    proxyuser is the user name for the proxy server, if basic authentication is required.

    proxypwd is the password for the user name that you specified.

  4. Unless you specified the silent parameter, enter Y to continue with the installation.

    Cloud Manager is now installed. At the end of the installation, the Cloud Manager service (occm) restarts twice if you specified a proxy server.

  5. Open a web browser and enter the following URL:


    ipaddress can be localhost, a private IP address, or a public IP address, depending on the configuration of the host. For example, if the Connector is in the public cloud without a public IP address, you must enter a private IP address from a host that has a connection to the Connector host.

  6. Sign up at NetApp Cloud Central or log in.

  7. If you installed the Connector in Google Cloud, set up a service account that has the permissions that Cloud Manager needs to create and manage Cloud Volumes ONTAP systems in projects.

  8. After you log in, set up Cloud Manager:

    1. Specify the NetApp account to associate with the Connector.

    2. Enter a name for the system.

      A screenshot that shows the set up screen that enables you to select a NetApp account and name the system.


The Connector is now installed and set up with your NetApp account. Cloud Manager will automatically use this Connector when you create new working environments.

After you finish

Set up permissions so Cloud Manager can manage resources and processes within your public cloud environment: