Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Installing the Breeze Agent on AWS Elastic Beanstalk can be done using .ebextension configuration files. In this example, we will use EB CLI to deploy new configuration.

1. Upload the Breeze Agent installer file somewhere your ElasticBeanstalk environment can reach. We recommend using any S3 bucket with restricted access or the one created by Elastic Beanstalk (used in the example below).

...

3. Deploy application with new .ebextension config.

Code Block
eb deploy

AWS EC2 User Data Script

You can install Breeze agent on AWS EC2 instances using 'EC2 instance user data' during the initial launch of an instance. The script involves the following steps:

...

Generate a presigned object URL for each installer

AWS CLI tool and preconfigured profile in your AWS account are required. Use this line command to generates Presigned object URL:

...

Windows must have Powershell preinstalled. This script will work for all Windows Server versions starting 2012 R2 and newer.

AWS Systems Manager Distributor

You can install Breeze agent on AWS EC2 instances using AWS Systems Manager Distributor.

...

In the file manifest.json find the field "version" and change its value to something a meaningful one. This is also the value of Version name that should be specified when the package will be is added to the Distributor (it becomes part of the AWS Systems Manager document). A version value can contain letters, numbers, underscores, hyphens, and periods, and be from 3 to 128 characters in length. It is recommended to use a human-readable value.

...

Note

Ensure that the script files have the correct lines breaks, namely LF (\n == 0x0A) on Linux and CRLF (\r\n == 0x0D 0x0A) on Windows.

...

Create an Advanced package in AWS Systems Manager as described in AWS documentation.

SCCM

To install Breeze Agent via SCCM, we recommend using PowerShell script that will download the agent installer to a target machine and install it.

...

Code Block
function New-TemporaryDirectory {
  $parent = [System.IO.Path]::GetTempPath()
  [string]$name = [System.Guid]::NewGuid()
  New-Item -ItemType Directory -Path (Join-Path $parent $name)
}

$url = "\\10.0.0.69\d\breeze-agent.exe"
$tmp_dir = New-TemporaryDirectory
$agent_sfx = "$tmp_dir\breeze-agent.exe"

# download agent installer
(New-Object System.Net.WebClient).DownloadFile($url, $agent_sfx)

# install agent
Start-Process $agent_sfx -ArgumentList '-gm2' -NoNewWindow -Wait

# clean up
Remove-Item "$tmp_dir" -recurse

Chef

1. Clone the public-utilities repo to your server:

...

Next chef-client will apply the changes on the nodes. Please note that it may take some time.

Puppet

1. Put the Puppet module folder to the /etc/puppetlabs/code/environments/production/modules/.

...

4. Add the required variables breeze_package_linux and breeze_package_windows.

Ansible

1. Put Breeze Agent installer files to the 'files' directory.

...

1. Create a file etc/tags in the Breeze agent’s directory:

Linux: /opt/breeze-agent/etc/tags

Windows: C:\Program Files\Breeze\etc\tags

...

To add the proxy support to Breeze agent, you need to edit the startup script:

On Linux:

Open file /opt/breeze-agent/app.sh

...

Code Block
export http_proxy="http://1.2.3.4:3128"
./app.rb # this line already exist in file

On Windows:

Open file C:\Program Files\Breeze\app.bat

...