Environment & Proxy

Configure outbound proxies and related environment settings for Breeze Agent.

Objectives

• Allow Breeze to reach breeze-server.cloudaware.com and other Cloudaware endpoints through your corporate proxy.
• Avoid breaking access to cloud metadata services (for example, 169.254.169.254) that Breeze uses for discovery.
• Provide custom certificate authority (CA) bundles when TLS interception or private CAs are in use.

Linux/macOS

Set proxy variables in the launcher script:

# /opt/breeze-agent/app.sh
export HTTPS_PROXY=https://proxy.example.com:8443
export HTTP_PROXY=http://proxy.example.com:8080
export NO_PROXY=169.254.169.254,localhost,127.0.0.1

Note that:

• http_proxy/HTTPS_PROXY are read by the underlying runtime and HTTP libraries.
• NO_PROXY should always include the cloud metadata IP(s) used by your platform so Breeze can query instance metadata directly.
• HTTP_CA_FILE points to a CA bundle file to trust when your proxy performs TLS inspection.

Windows

Update the launcher batch file:

:: C:\Program Files\Breeze\app.bat
set HTTPS_PROXY=https://proxy.example.com:8443
set HTTP_PROXY=http://proxy.example.com:8080
set NO_PROXY=169.254.169.254,localhost,127.0.0.1

Certificate Trust

• If TLS interception is used, ensure the proxy CA is trusted by:
  • The OS trust store, and
  • The user context under which the Breeze scheduler runs.
• Use HTTP_CA_FILE or OS‑level trust configuration to provide the correct CA bundle.
• Always include cloud metadata addresses in NO_PROXY (for example, 169.254.169.254) so discovery can read instance metadata directly.

For allowlisting Cloudaware service endpoints and public IPs, see the Service Endpoints & Public IPs guide.