Skip to main content

Breeze

Use this guide to leverage simple, automated deployment of the Cloudaware Breeze Agent across Windows, Linux, macOS, and Kubernetes using your existing device‑management and automation tooling.

info
  • Audience: Cloudaware administrators, infrastructure and endpoint teams
  • Outcome: Breeze is installed automatically at scale, and rollout workflows are repeatable across supported environments

High-Level Setup Flow​

  • Install Breeze using platform tools instead of manual, one‑off installs.
  • Reuse the same installer artifacts you would use for manual installation.
  • Keep rollout steps small and predictable: obtain installer, distribute, install, verify.
tip

For detailed OS‑specific commands and options, see Breeze Installation and its Windows, Linux, macOS, and Kubernetes sub‑pages.

Prerequisites​

Before you begin, make sure you have:

  • Access to a Cloudaware account.
  • A user with access to the Admin Console and permissions to manage cloud accounts, organizations, and integrations (Cloudaware Administrator).
  • Outbound network access for Breeze per the Cloudaware Service Endpoints & Public IPs guide.
  • Service accounts, groups, and permissions in your automation tools (SSM, Intune, SCCM, config management, etc.).

Download the Installer​

  1. In Cloudaware, go to Admin.
  2. Find Breeze in DevOps Integrations. Click CONFIGURED.
  3. Download the appropriate installer for your target OS (Windows, Linux, or MacOS).
  4. Store the installer(s) in a secure location used by your automation tool (for example, S3, internal package repository, or file share).

Choose an Automation Channel​

Pick one or more channels based on where your workloads run and which tools your organization already uses:

  • Cloud management: AWS Systems Manager (SSM), Elastic Beanstalk, EC2 user data, Azure Run Command/VM extensions.
  • Endpoint/device management: Microsoft Intune, SCCM/MECM.
  • Configuration management: Ansible, Chef, Puppet.
  • Platform‑specific: Kubernetes DaemonSet, golden images/VM templates, vCenter templates (where applicable).

The sections below outline simple steps for each pattern. Use them with the OS‑specific install commands referenced in the Breeze installation docs.

AWS Systems Manager (SSM)​

Typical pattern for EC2 or hybrid instances:

  1. Upload the Breeze installer to a location reachable by SSM (for example, S3 or Distributor package).
  2. Create an SSM document or Distributor package that:
    • Downloads the installer.
    • Extracts it on Linux, if applicable.
    • Runs the install script or executable with the required parameters.
  3. Use Run Command or State Manager to target instances by tags or resource groups.
  4. Confirm installation status via SSM output and Breeze check‑ins in Cloudaware.

For details on package sharing options, see Breeze Package Sharing.

AWS Elastic Beanstalk/EC2 User Data​

For workloads launched through Elastic Beanstalk or raw EC2:

  1. Place the Breeze installer in S3 or another accessible location.
  2. For Elastic Beanstalk:
    • Add a .ebextensions configuration that downloads the installer during instance provisioning.
    • Run the installation command (Linux shell script or Windows executable) as part of instance bootstrap.
  3. For EC2 user data:
    • Use user data (cloud‑init or PowerShell) to download the installer.
    • Extract and run the installer before the application starts.
  4. Verify that new instances register with Breeze and appear in Cloudaware CMDB.

Microsoft Intune​

For managed Windows endpoints:

  1. Package the Breeze Windows installer as a Win32 application in Intune.
  2. Define the install command (for example, running the Breeze .exe silently).
  3. Configure detection rules (for example, presence of Breeze program files or the scheduled task).
  4. Assign the application to device or user groups and monitor deployment success.

SCCM/MECM​

For traditional Windows endpoint management:

  1. Create an application or package in SCCM pointing to the Breeze installer.
  2. Specify the silent install command appropriate for the Breeze executable.
  3. Configure detection logic (for example, Breeze program directory, log file, or scheduled task).
  4. Deploy to device collections in waves (pilot, broader rings) and monitor compliance.

Configuration Management (Ansible, Chef, Puppet)​

For configuration‑as‑code environments:

  1. Store the Breeze installer in a repository or artifact store accessible to your agents.
  2. Implement a role/cookbook/module that:
    • Downloads the installer to the target host.
    • Extracts it on Linux if needed.
    • Runs the installer idempotently (skip if Breeze is already present and healthy).
  3. Apply the configuration to the desired host groups or environments.

Azure VM Run Command/Extensions​

For Azure virtual machines:

  1. Ensure the VM has outbound connectivity to Cloudaware endpoints.
  2. Use Azure VM Run Command or a custom script extension to:
    • Download the Breeze installer from a secure location.
    • Run the installation script or executable with appropriate flags.
  3. Convert successful patterns into reusable policies or ARM/Bicep/Terraform modules.

Kubernetes Nodes​

For Kubernetes‑based deployments:

  1. Prepare the DaemonSet or equivalent manifests by following the Breeze Installation on Kubernetes guide.
  2. Ensure nodes can reach the Breeze service endpoint listed in Service Endpoints & Public IPs.
  3. Deploy the DaemonSet to run a Breeze pod on each node.
  4. Verify node coverage and health in Cloudaware.

For private-network Kubernetes clusters, install Breeze with proxy support by following the Breeze Agent With TunHub Installation on Private Kubernetes guide.

Golden Images/VM Templates​

For environments using templates or images:

  1. Install Breeze on a reference image or template (Windows, Linux, or virtual appliance).
  2. Validate that the agent runs correctly and can reach Cloudaware.
  3. Generalize the image according to your platform requirements.
  4. Use the updated image/template for new workloads.
  5. Verify that new instances appear in CMDB with unique identifiers.

Validate Rollout​

  • Confirm that new hosts appear with Breeze data in Cloudaware CMDB.
  • Check Breeze health metrics (last check‑in, version, OS facts) on a CI for a pilot group before expanding.
  • Review logs on sample hosts for connectivity or proxy issues.

Operate and Maintain​

  • Standardize Breeze deployment as part of onboarding for new servers, endpoints, and clusters.
  • Include Breeze in change management for image updates and automation scripts.
  • Periodically review and update automation workflows when Breeze agent versions or installer formats change.