- Automation Management
- Automation Management Permissions
- Automation Management Playbooks
- Automation Management Playbook Triggers
- Pre-Built Automation Management Playbooks
- Automation Management Advanced Playbooks
- Automation Management Rule-Based Playbooks
- Filter Automation Management Playbooks
- Find Automation Management Playbooks
- Enable or Disable an Automation Management Playbook
- Reorder an Automation Management Playbook
- Delete an Automation Management Playbook
- Automation Management Services
- Automation Management Actions
- Create an Automation Management Action
- Clone an Automation Management Action
- Edit an Automation Management Action
- Deploy an Automation Management Action
- Preview Automation Management Action Code
- View Automation Management Action Version History
- View Automation Management Action Audit Log
- Refresh Automation Management Action List
- Automation Agents
Automation Agents
Securely connect Automation Management to segmented networks using automation agents.
An automation agent is a process that securely connects Automation Management to on-premises or network-segmented systems so you can run advanced playbooks and actions remotely on those systems.
To connect Automation Management to a segmented network, you create an automation agent, then run the automation agent using Docker. When you run an automation agent, it's assigned a JSON Web Token (JWT) for authenticating HTTP requests to your network.The JWT is valid for 365 days, after which it expires. When the JWT is deleted, revoked, or expired, you can delete the automation agent.
After you create an automation agent, you assign a given action the specific automation agent it uses to connect to your network.
View all automation agents in the Automation Agents tab.
For each automation agent, view:
Agent name – The name of the automation agent.
Version – The version of the Automation Management image used to run the automation agent.
Status – The health and availability of the automation agent:
Running – The automation agent has started running and is actively connecting Automation Management to your network.
In progress – The automation agent has been created but hasn't started running. When the automation agent starts running and is actively connecting Automation Management to your network, the status changes to Running.
Heartbeat failed – The automation agent is stopped, offline, or terminated; or the automation agent has been created but hasn't started running within one minute after it was created.
Token expiration – The date and number days of left until the automation agent JWT expires. After the JWT expires, you can delete the automation agent and create a new one.
Created – The date and time the automation agent was created.