Creating Automations
To create automations, in Key Manager GUI, navigate to Automation→Automations page and click Create a new automation.
The automation must have a target, the type of which is one of the following:
- Authorized key
- Private key
- Host
You can define the scope of the automation using the Include if and Exclude if options. These options are defined using client style filter string. For examples of filtering strings, see list-authorized-keys. If no inclusions or exclusions are specified, the automation defaults to global coverage.
Triggers
To add triggers that start the automation, click Add Trigger. Triggers can be activated by a raising or clearing of a policy violation, raising of an alert, or a host deployment or state change. When multiple triggers are specified, the automation will run if any one of them is triggered.
You can only select existing policies for policy-based triggers. To create a policy, navigate to Policy → Policy rules, and click Create new policy rule.
An automation rule will only execute an automation when a new alert is raised, or a new policy violation or clearance is detected. Old/existing violations/clearances or alerts will not trigger an automation rule.
Steps
To add steps, click Add Steps. The steps will run sequentially. The Condition setting on each step can be used to limit the scope of the step, for example to run only on certain subset of users or hosts. The conditions are set using filter strings similar to the ones used by the Include if and Exclude if options.
To see logs of previously run automations, you can view them at Automation → Automation executions.