Sync Agent setup¶
The Sync Agent is a lightweight software component installed within a client's own infrastructure. It acts as the secure bridge between the client's source systems and Aunsight Data Services, allowing data to be ingested for analytics without exposing the client's internal systems directly to the platform.
This section covers how to create, install, and maintain a Sync Agent.
Before you begin¶
Recommended server requirements¶
The machine the Sync Agent runs on should be dedicated exclusively to sync agents and configured with at least:
- 8 cores
- 32 GB RAM
- 100 GB disk space
- Windows Server 2022 or newer
Choosing an installation method¶
There are two ways to create and install a Sync Agent. Both produce the same result — a registered agent running as a service in the client environment — so choose whichever fits your access and tooling:
- Using the Console — a guided, mostly point-and-click flow in the Aunsight Console. Best when you have access to the console UI and want the simplest path. You create the agent in the UI, download the Agent Manager, and run a couple of commands to configure and install it.
- Using the CLI — a fully command-line flow using the Sync Agent Manager together with the Toolbelt (or direct API calls). Best for scripted or headless installs, and available for Windows, macOS, and Linux.
Common configuration values¶
Regardless of method, the agent is configured to talk to these platform endpoints:
- API URL:
https://api-au3.aunsight.com - RTM URL:
wss://rtm-au3.aunsight.com - Console:
https://console-au3.aunsight.com/
Maintaining an agent¶
Once an agent is installed, you can generate new registration tokens, edit or update it, and restart it if needed. The how-to steps for these live on the method pages:
- Generating a new token and modifying an agent — see Using the Console
- Restarting an agent (Windows Services or the Manager process) — see Using the Console
Feature release & third-party app notice
To deliver new features, the platform uses trusted third-party applications to manage feature releases. As part of this you may notice activity from foreign IP addresses. This is a normal and secure part of the deployment system and does not pose a risk to data or account security.