Agent-Cloud link (ACLK)

The Agent-Cloud link (ACLK) is the mechanism responsible for securely connecting a Netdata Agent to your web browser through Netdata Cloud. The ACLK establishes an outgoing secure WebSocket (WSS) connection to Netdata Cloud on port 443. The ACLK is encrypted, safe, and is only established if you claim your node.

The Cloud App lives at which currently resolves to However, this IP or range of IPs can change without notice. Watch this page for updates.

Netdata is a distributed monitoring system. Very few data are streamed to the cloud, such as data about:

  • All configured alarms and their current status
  • Metrics that are requested by the cloud user
  • A list of the active collectors

For a guide to claiming a node using the ACLK, plus additional troubleshooting and reference information, read our get started with Cloud guide or the full claiming documentation.

Enable and configure the ACLK

The ACLK is enabled by default, with its settings automatically configured and stored in the Agent's memory. No file is created at /var/lib/netdata/cloud.d/cloud.conf until you either claim a node or create it yourself. The default configuration uses two settings:

enabled = yes
cloud base url =

If your Agent needs to use a proxy to access the internet, you must set up a proxy for claiming.

You can configure following keys in the netdata.conf section [cloud]:

statistics = yes
query thread count = 2
  • statistics enables/disables ACLK related statistics and their charts. You can disable this to save some space in the database and slightly reduce memory usage of Netdata Agent.
  • query thread count specifies the number of threads to process cloud queries. Increasing this setting is useful for nodes with many children (streaming), which can expect to handle more queries (and/or more complicated queries).

Disable the ACLK

You have two options if you prefer to disable the ACLK and not use Netdata Cloud.

Disable at installation

You can pass the --disable-cloud parameter to the Agent installation when using a kickstart script ( or, or a manual installation from Git.

When you pass this parameter, the installer does not download or compile any extra libraries. Once running, the Agent kills the thread responsible for the ACLK and claiming behavior, and behaves as though the ACLK, and thus Netdata Cloud, does not exist.

Disable at runtime

You can change a runtime setting in your cloud.conf file to disable the ACLK. This setting only stops the Agent from attempting any connection via the ACLK, but does not prevent the installer from downloading and compiling the ACLK's dependencies.

The file typically exists at /var/lib/netdata/cloud.d/cloud.conf, but can change if you set a prefix during installation. To disable the ACLK, open that file and change the enabled setting to no:

enabled = no

If the file at /var/lib/netdata/cloud.d/cloud.conf doesn't exist, you need to create it.

Copy and paste the first two lines from below, which will change your prompt to cat.

cd /var/lib/netdata/cloud.d
cat > cloud.conf << EOF

Copy and paste in lines 3-6, and after the final EOF, hit Enter. The final line must contain only EOF. Hit Enter again to return to your normal prompt with the newly-created file.

To get your normal prompt back, the final line must contain only EOF.

enabled = no
cloud base url =

You also need to change the file's permissions. Use grep "run as user" /etc/netdata/netdata.conf to figure out which user your Agent runs as (typically netdata), and replace netdata:netdata as shown below if necessary:

sudo chmod 0770 cloud.conf
sudo chown netdata:netdata cloud.conf

Restart your Agent to disable the ACLK.

Re-enable the ACLK

If you first disable the ACLK and any Cloud functionality and then decide you would like to use Cloud, you must either reinstall Netdata with Cloud enabled or change the runtime setting in your cloud.conf file.

If you passed --disable-cloud to during installation, you must reinstall your Agent. Use the same method as before, but pass --require-cloud to the installer. When installation finishes you can claim your node.

If you changed the runtime setting in your var/lib/netdata/cloud.d/cloud.conf file, edit the file again and change enabled to yes:

enabled = yes

Restart your Agent and claim your node.

Last updated on