Breeze Agent 3.x Installation
Install Breeze Agent 3.x on Linux and Windows hosts. The installer is built for your Cloudaware account and already contains the agent's certificate and server address, so the agent needs no configuration to start reporting.
If the host runs Breeze Agent 1.x, read Migration From Breeze Agent 1.x to 3.x first.
Before You Begin
- Check Feature Availability for the capabilities your hosts use.
- Confirm that the host runs a supported operating system and architecture. See Compatibility & Support.
- Allow outbound HTTPS over TCP 443 from the host to Cloudaware. See Service Endpoints & Public IPs. No inbound connections are required.
- On AWS, Azure, Google Cloud, and Oracle Cloud, allow the agent to reach the instance metadata service at
169.254.169.254. - If the host reaches the internet through a proxy, see Install Behind a Proxy.
Download the Installer
- In Cloudaware, go to Admin.
- Find Breeze in DevOps Integrations. Click CONFIGURED.
- Download the Breeze Agent 3.x installer for your platform:
- Linux:
breeze-3.x.x-bNNNNN-<key>-linux-x86_64.tgzorbreeze-3.x.x-bNNNNN-<key>-linux-arm64.tgz - Windows:
breeze-3.x.x-bNNNNN-<key>-windows-x86_64.exe
- Linux:
A Breeze Agent 3.x installer appears in the Admin console only after Cloudaware has built one for your account. If it is not there, contact Cloudaware Support.
The installer contains your account's agent certificate and private key. Store and distribute it the way you handle other credentials.
Install on Linux
Run the installer as root or with sudo:
tar xzf breeze-*.tgz
cd breeze
sudo ./install.sh
The installer:
- Copies the agent to
/opt/cloudaware/breeze. - Installs
libxcrypt-compatwithyumon Amazon Linux 2023 and RHEL 10, where the agent requires it. The host must be able to reach its package repositories. - Schedules the agent to run every 15 minutes as
root, with a systemd timer (breeze.timer), or with a cron job (/etc/cron.d/breeze) on hosts without systemd.
Run as a Non-Root User
To schedule the agent as another user, pass the user name with -u:
sudo ./install.sh -u breeze
The user must already exist. The installer makes that user the owner of /opt/cloudaware/breeze. An agent that does not run as root can only collect data: plugins that install or configure software on the host do not work.
Install on Windows
Run the installer from an elevated Command Prompt, or double-click it and accept the elevation prompt:
breeze-3.x.x-bNNNNN-<key>-windows-x86_64.exe
For a silent installation, for example from SCCM, Intune, or AWS Systems Manager, add -gm2:
breeze-3.x.x-bNNNNN-<key>-windows-x86_64.exe -gm2
The installer:
- Copies the agent to
C:\Program Files\Cloudaware\Breeze. - Creates the scheduled task
Cloudaware\Breeze, which runs the agent every 15 minutes asSYSTEM.
Install Behind a Proxy
The agent reads the proxy from the http_proxy variable in its configuration file. There are two ways to set it:
- Before installation: ask Cloudaware Support to build your installer with your proxy URL. The agent then uses the proxy from its first run, and
169.254.169.254is excluded from the proxy so instance metadata stays reachable. - After installation: add
http_proxyto the configuration file. See Proxy.
If the proxy inspects TLS traffic, also set SSL_CERT_FILE. See Custom CA Bundle.
Verify the Installation
Load the agent environment, then check the scheduler and the last run.
-
Linux:
sudo -i. /opt/cloudaware/breeze/bin/env.shbreeze versionbreeze scheduler statusbreeze status -
Windows (elevated Command Prompt):
call "C:\Program Files\Cloudaware\Breeze\bin\env.cmd"breeze versionbreeze scheduler statusbreeze status
breeze scheduler status prints enabled when the scheduled task exists. breeze status prints running while a run is in progress and stopped between runs. It does not tell you whether the last run succeeded: check the log for that.
Scheduled runs write their log to var/log/breeze.log in the agent directory:
- Linux:
/opt/cloudaware/breeze/var/log/breeze.log - Windows:
C:\Program Files\Cloudaware\Breeze\var\log\breeze.log
To run the agent immediately instead of waiting for the next scheduled run, use breeze run -vt. See Command Line.
After the first successful run, the host appears in Cloudaware CMDB with its OS-level facts. If it does not, run breeze troubleshoot.
Upgrades
Breeze Agent 3.x upgrades itself. When Cloudaware raises the minimum agent version, the agent installs that version on its next run. To upgrade on demand, run breeze upgrade. See Command Line.
You do not need to reinstall the agent to upgrade it. Running the installer again reinstalls the agent and replaces its configuration file.
Related
- Configuration
- Command Line
- Uninstall
- Breeze integration for fleet deployment tools