Skip to content

CLOUDflex Agent

CLOUDflex Agent is a small command-line utility that runs inside a production instance. It applies operating-system-level settings that CLOUDflex Studio cannot change through the cloud provider API alone.

The agent is available as packaged x64 binaries for Windows and Linux. It runs a requested task and exits; it is not a continuously running monitoring or remote-control service.

Studio can deploy infrastructure and store environment settings, but some production applications read configuration from files on the local machine. The agent bridges that gap. It converts deployment settings into the local format expected by NDI or DCV without requiring an administrator to edit each instance by hand.

The current agent is used for two host-level responsibilities:

  • configuring how an instance participates in an NDI environment;
  • installing CLOUDflex-provided certificate files for NICE DCV on Windows.

It does not start or stop cloud instances, manage Flow Manager flows, monitor the machine continuously, or replace the CLOUDflex Studio control plane.

The ndi-access capability manages the standard ndi-config.v1.json file on the instance. It can set:

  • the NDI machine name;
  • one or more NDI Discovery Server addresses;
  • the NDI receive group;
  • the NDI send group.

On Windows, the agent manages the configuration under C:\ProgramData\NDI\. On Linux, it manages the .ndi directory in the account’s home directory. The agent loads an existing configuration when present and updates the selected values.

The CLOUDflex NDI multiviewer deployment template downloads the Linux agent and uses it to apply the Discovery Server address supplied by the deployment. This keeps the deployed router on the same discovery path as the rest of the environment.

After the agent runs, verify that the expected NDI sources are visible. If they are not, check the Discovery Server state, configured address, security rules, routing, and NDI group names.

The cert-manager capability can download the CLOUDflex-provided DCV certificate and private key to the location used by NICE DCV on Windows. This is needed when a DCV host must use the centrally provided certificate rather than its existing local certificate.

Run certificate management with the permissions required to write to the Windows system profile. Protect the downloaded private key according to your organization’s credential-handling policy.

The current implementation manages DCV certificate files only. Do not rely on it to update Nimble certificates.

  • Use the Windows x64 binary on Windows and the Linux x64 binary on Linux.
  • Run the agent as the same account whose Linux NDI configuration should be changed, or with the Windows permissions required for the destination path.
  • Allow outbound HTTPS to the approved CLOUDflex deployment-resource endpoint when a template downloads the agent.
  • Allow outbound HTTPS to scripts.cloudflex.studio when updating DCV certificate files.
  • Confirm the local application or service has loaded the new configuration. The agent writes the files but does not restart NDI applications or DCV.