Remote Agents

introduction swimlane remote agents enable the execution of automation actions on networks outside of your primary swimlane environment remote agents allow the execution of actions on remote machines, allowing access to resources that are not directly available to your primary environment rather than a vpn architecture, remote agents dispatch work via secure websockets to your main swimlane turbine instance only connectors and data in and out of the action are transmitted over the network connection, providing additional security and control remote agents require a container host, either docker or podman it is installed with a simple bash script to guide you through the installation communication is done purely through an outbound connection to turbine cloud via https and websockets (tls/443) the only other remote connection required is during installation and upgrades, when the base images will be pulled from quay io remote agents run containerized connectors by running podman inside of your container host, providing process isolation and control remote agents automatically update via a cron process created during installation when the primary instance is updated, older versions of remote agents will be able to connect and function they will then be replaced when the cron job triggers architecture remote agents use containers to isolate data and workloads connectors are run as containers within an internal podman instance, controlled by a turbine engine container running alongside it all communication to the primary swimlane turbine environment is controlled through the turbine agent container, via its secure websocket connection all communications with the primary instance are over tls/443 connectors from the primary instance are downloaded via https during installation the turbine agent and turbine container engine (podman) containers will be downloaded from quay io, unless overridden by installation parameters communication to local resources will be through both the turbine agent container and any sub containers in turbine container engine