Agent Smith
Rewst's lean, open-source command executor that fits right into your Rewst workflows.
Last updated
Rewst's lean, open-source command executor that fits right into your Rewst workflows.
Last updated
Built with Python and leveraging Microsoft Azure IoT Hub, Agent Smith is all about keeping things fast, simple, and within your control. Agent Smith steps in to fill any gaps in your ability to execute scripts and syncs smoothly within your workflows.
Share feedback, and help us buff out any rough edges by joining the early birds.
Speedy Script Execution: Overcomes traditional RMM task execution speed challenges.
Open Source Customization: Available on GitHub, fully manageable through your Azure Tenant and Rewst workflows.
Free and Cost-Effective: Operates potentially under Azure's free tier, depending on usage.
Easy Setup: Simple device and service provisioning via Rewst Crates, suitable for domain controllers and endpoints.
Secure CI/CD: Ensures security and validity with automated builds, cryptographic signing, and SHA256 hashing.
Seamless Integration: Waits for JSON messages, fitting effortlessly into existing automations.
Agent Smith relies on the Microsoft Azure IoT Hub for the majority of the heavy lifting.
The setup process will create an IoT hub instance in your top-level Azure environment.
All Agents will become registered devices in your top-level IoT Hub, and their connection properties remain within that instance.
Agent installation sets the organization id for the Agent to be registered with so that workflows can identify agents according to their Rewst organization.
Agents will establish a connection to your IoT Hub instance for receiving messages triggered by Rewst workflows. These messages will contain IDs that refer to specific workflow executions that expect shell code to be executed.
Your IoT Hub will be established with its own hostname, such as myiothub.azure-devices.net
The Agents will communicate with the IoT Hub using the MQTT protocol (tcp/8883).
The results of shell code will be sent directly back to Rewst via webhook (HTTP POST) to the workflow executions for processing.
The URLs that the agents will be sending data to are ephemeral, single-use paths.
They will correspond to the "back-end application handling" hostnames listed in the Security Page in the Rewst docs.
This combination of discrete one-way communication channels separates the message data, removing the requirement for the IoT Hub to have visibility to resulting data. The data is sent only direct to the workflow that requires it via a direct POST to an ephemeral URL.
You will need to obtain your own Microsoft Azure subscription, and integrate it to Rewst at your top-level organization. You can refer to our documentation here.
Follow the setup instructions here
Zero Cost, Zero Guarantees. While we're confident Agent Smith won't cause any tech havoc, please ensure you'll be able to test in a lab environment first.
Remember, this is your agent. Modify it, tweak it, make it yours. And if you're up for sharing, we'd love to include your expertise in the repository! Join the #agent-smith channel on our Discord for more details and updates.
Check out the Agent Smith Configuration Overview page to set up and configure!
