Learn about Connectors

Contributors netapp-bcammett netapp-tonacki juliantap

In most cases, an Account Admin will need to deploy a Connector in your cloud or on-premises network. The Connector is a crucial component for the day-to-day use of Cloud Manager. The Connector enables Cloud Manager to manage the resources and processes within your public cloud environment.

When a Connector is required

A Connector is required to use any of the following features within Cloud Manager:

  • Amazon FSx for ONTAP advanced management features

  • Amazon S3 bucket discovery

  • Cloud Backup

  • Cloud Data Sense

  • Cloud Tiering

  • Cloud Volumes ONTAP

  • Global File Cache

  • Kubernetes clusters

  • Monitoring

  • On-premises ONTAP clusters

A Connector is not required for Azure NetApp Files, Cloud Volumes Service, Cloud Sync, or Active IQ Digital Advisor.

Note While a Connector isn’t required to set up and manage Azure NetApp Files, a Connector is required if you want to use Cloud Data Sense to scan Azure NetApp Files data.

Supported locations

A Connector is supported in the following locations:

  • Amazon Web Services

  • Microsoft Azure

  • Google Cloud

  • On your premises

  • On your premises, without 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.

Connectors should remain running

A Connector should remain running at all times. It’s important for the continued health and operation of the services that you enable.

For example, a Connector is a key component in the health and operation of Cloud Volumes ONTAP PAYGO systems. If a Connector is powered down, Cloud Volumes ONTAP PAYGO systems will shut down after losing communication with a Connector for longer than 14 days.

How to create a Connector

An Account Admin needs to create a Connector before a Workspace Admin can create a Cloud Volumes ONTAP working environment and use any of the other features listed above.

An Account Admin can create a Connector in a number of ways:

Cloud Manager will prompt you to create a Connector if one is needed to complete an action.

Permissions

Specific permissions are needed to create the Connector and another set of permissions are needed for the Connector instance itself.

Permissions to create a Connector

The user who creates a Connector from Cloud Manager needs specific permissions to deploy the instance in your cloud provider of choice. Cloud Manager will remind you of the permissions requirements when you create a Connector.

Permissions for the Connector instance

The Connector needs specific cloud provider permissions to perform operations on your behalf. For example, to deploy and manage Cloud Volumes ONTAP.

When you create a Connector directly from Cloud Manager, Cloud Manager creates the Connector with the permissions that it needs. There’s nothing that you need to do.

If you create the Connector yourself from the AWS Marketplace, the Azure Marketplace, or by manually installing the software, then you’ll need to make sure that the right permissions are in place.

Number of working environments per Connector

A Connector can manage multiple working environments in Cloud Manager. The maximum number of working environments that a single Connector should manage varies. It depends on the type of working environments, the number of volumes, the amount of capacity being managed, and the number of users.

If you have a large-scale deployment, work with your NetApp representative to size your environment. If you experience any issues along the way, reach out to us by using the in-product chat.

When to use multiple Connectors

In some cases, you might only need one Connector, but you might find yourself needing two or more Connectors.

Here are a few examples:

  • You’re using a multi-cloud environment (AWS and Azure), so you have one Connector in AWS and another in Azure. Each manages the Cloud Volumes ONTAP systems running in those environments.

  • A service provider might use one NetApp account to provide services for their customers, while using another account to provide disaster recovery for one of their business units. Each account would have separate Connectors.

Using multiple Connectors with the same working environment

You can manage a working environment with multiple Connectors at the same time for disaster recovery purposes. If one Connector goes down, you can switch to the other Connector to immediately manage the working environment.

To set up this configuration:

  1. Switch to another Connector

  2. Discover the existing working environment.

  3. Set the Capacity Management Mode to Manual on any additional Connectors.

    Only the main Connector should be set to Automatic Mode. If you switch to another Connector for DR purposes, then you can change the Capacity Management Mode as needed.

When to switch between Connectors

When you create your first Connector, Cloud Manager automatically uses that Connector for each additional working environment that you create. Once you create an additional Connector, you’ll need to switch between them to see the working environments that are specific to each Connector.

The local user interface

While you should perform almost all tasks from the SaaS user interface, a local user interface is still available on the Connector. This interface is needed if you install the Connector in an environment that doesn’t have internet access, and for a few tasks that need to be performed from the Connector itself, instead of the SaaS interface:

  • Setting a proxy server

  • Installing a patch (you’ll typically work with NetApp personnel to install a patch)

  • Downloading AutoSupport messages (usually directed by NetApp personnel when you have issues)

Connector upgrades

The Connector automatically updates its software to the latest version, as long as it has outbound internet access to obtain the software update.