Skip to main content

Fleet Deployment

Deploy Breeze Agent at scale via your existing device‑ and configuration‑management tools. Pair it with the OS‑specific install steps in:

Prerequisites​

Before automating Breeze deployment:

  • Confirm platform support, network, and proxy settings in Requirements.
  • Download the latest Breeze installers from the Cloudaware Admin. For details, see also the Breeze integration guide.
  • Validate a manual installation on a small set of hosts (per OS guides) before rolling out broadly.

AWS Systems Manager (SSM)​

Use AWS Systems Manager (SSM) to deploy Breeze to EC2 or hybrid instances.

Breeze Package Sharing​

Use Breeze package sharing when you want Cloudaware to share a ready-to-use Breeze package with AWS Systems Manager Distributor instead of creating the package manually.

Before you begin:

  • Make sure AWS Systems Manager is enabled and configured for the target AWS account and instances.
  • Make sure the AWS account is added to Cloudaware.

To enable package sharing:

  1. Log in to Cloudaware and open Admin.
  2. In DevOps Integrations, find Breeze and click CONFIGURED.
  3. Under Cloud-based installation, enable Breeze Package Sharing (AWS only) (toggle).
  4. In the AWS Console, open AWS Systems Manager → Distributor → Shared with me and confirm that the Cloudaware Breeze package is available.
  5. Use the shared Distributor package with Run Command for one-time installation or State Manager for ongoing enforcement.

Distributor Package​

  • Build a package that includes:
    • A Linux ZIP archive with install.sh, uninstall.sh, and the Linux Breeze tarball.
    • A Windows ZIP archive with install.ps1, uninstall.ps1, and the signed Windows installer.
  • Use the manifest template and scripts from the breeze-tools AWS SSM helpers to:
    • Set a meaningful "version" value in manifest.json.
    • Fill in sha256 checksums for each archive.
  • Create an Advanced package in AWS Systems Manager Distributor using the manifest and archives.

Run Command/State Manager​

  • Create an SSM document or use the Distributor package so that on each target instance SSM:
    • Downloads the Breeze installer or Distributor payload.
    • Extracts the archive on Linux if needed.
    • Runs the installer (shell script or .exe) with appropriate options.
  • Use Run Command for one‑time deployments and State Manager for ongoing enforcement.
  • Target instances by tags or resource groups and align runs with maintenance windows.

Microsoft Intune​

Use Intune for managed Windows endpoints (laptops, workstations, servers).

  • On a reference device, install Breeze manually and set an Intune descriptor tag (optional but recommended) in C:\Program Files\Breeze\etc\tags, for example:

    preferred.descriptor=intune

  • Package the Breeze Windows installer as a Win32 app:

    • Install command: silent or unattended invocation of the Breeze .exe.
    • Uninstall command: C:\Program Files\Breeze\uninstall.bat.
    • Detection rules: presence of C:\Program Files\Breeze\app.bat, agent.log, or the Breeze Agent scheduled task.

  • Assign the app to device or user groups in rings (pilot → broader) and monitor deployment results.

SCCM/MECM​

Use SCCM/MECM for traditional Windows fleet management.

  • Place the Breeze installer on a file share accessible from target devices.
  • Create an MECM application or package that:
    • Downloads the installer to a temporary directory (for example, via a PowerShell script).
    • Runs the installer silently.
    • Cleans up temporary files.
  • Configure detection rules based on:
    • Presence of C:\Program Files\Breeze\app.bat or agent.log.
    • Existence of the Breeze Agent scheduled task.
  • Roll out to collections in phases and verify compliance before expanding.

AWS Elastic Beanstalk/EC2 User Data​

Use these patterns when Breeze should be present on every application instance as it comes online.

Elastic Beanstalk​

  • Upload the Breeze installer to an S3 bucket accessible from the Elastic Beanstalk environment.

  • Add a .ebextensions configuration to your application that:

    • Downloads the Breeze installer from S3 to the instance.
    • Installs Breeze during provisioning if it is not already present.

  • Example (Linux‑based environment, simplified):

    files:
      "/tmp/breeze-agent.tgz":
        source: https://example-bucket.s3.amazonaws.com/breeze-agent.tgz
        authentication: S3Auth
    commands:
      "install breeze agent":
        test: test ! -d /opt/breeze-agent
        command: tar -xf /tmp/breeze-agent.tgz -C /tmp && /tmp/breeze-agent/install.sh

EC2 User Data​

  • Upload the Breeze installer to S3 and generate a presigned URL for a short‑lived, public download.

  • Use EC2 user data so each new instance:

    • Downloads the installer with curl/wget (Linux) or PowerShell (Windows).
    • Extracts the archive on Linux.
    • Runs the installer.

  • Example (Linux user‑data script, simplified):

    #!/bin/bash
    URL='<presigned URL to Breeze installer>'
    curl "$URL" -o /tmp/breeze-agent.tgz
    tar -xf /tmp/breeze-agent.tgz -C /tmp
    /tmp/breeze-agent/install.sh

Rollout Guidance​

  • Start with a pilot ring; monitor Breeze check‑ins and OS Facts before broad rollout.
  • Use tags, device collections, or groups to control the scope and pace of deployment.
  • Coordinate Breeze deployment with maintenance windows for production workloads.
  • If outbound proxies inspect TLS, prefer explicit exceptions for Breeze endpoints and document proxy settings (see Configuration).
On this page