Endpoints that the data broker contacts Edit on GitHub Request doc changes

Contributors netapp-bcammett

The NetApp data broker requires outbound internet access over port 443 to communicate with the Cloud Sync service and to contact a few other services and repositories. If you need to limit outbound connectivity, refer to the following list of endpoints when configuring your firewall for outbound traffic.

The data broker contacts the following endpoints:

Endpoints Purpose

olcentgbl.trafficmanager.net:443

To contact a repository for updating CentOS packages for the data broker host. This endpoint is contacted only if you manually install the data broker on a CentOS host.

rpm.nodesource.com:443
registry.npmjs.org:443
nodejs.org:443

To contact repositories for updating Node.js, npm, and other 3rd party packages used in development.

tgz.pm2.io:443

To access a repository for updating PM2, which is a 3rd party package used to monitor Cloud Sync.

sqs.us-east-1.amazonaws.com:443
kinesis.us-east-1.amazonaws.com:443

To contact the AWS services that Cloud Sync uses for operations (queuing files, registering actions, and delivering updates to the data broker).

s3.region.amazonaws.com:443

For example: s3.us-east-2.amazonaws.com:443
See AWS documentation for a list of S3 endpoints

To contact Amazon S3 when a sync relationship includes an S3 bucket.

cf.cloudsync.netapp.com:443
repo.cloudsync.netapp.com:443

To contact the Cloud Sync service.

support.netapp.com:443

To contact NetApp support when using a BYOL license for sync relationships.