Navigate to Playbooks > Add Playbook and then Create playbook screen would show up
Let’s say you want to check if any risk is found in your platform then the playbook successfully automates it or not.
Objective: “Enable S3 bucket versioning if it’s disabled”
- Enter Playbook name as “Enable S3 bucket versioning” and then add description for a better understanding of the trigger.
- Selecting a Trigger
There are three most commonly used triggers or you can also pick a template which has further three types.
- Blank Playbook: You can create a trigger by setting your own choice of conditions or actions.
- Enforce S3 bucket encryption: By selecting this template you can ‘Send AWS Request’ to enforce the encryption of the S3 bucket
- Escalate an alert: Through this you can automate cloudnosys system alerts to your platform via different emails.
In the above display, we have selected “When a Risk is generated”
3. Add Playbook screen would show up with a card “Trigger”
Now from Trigger type you can decide whether you want to receive a Risk or System Alert
To apply a condition to the trigger, click on the Success button, a card for multiple actions will appear:
Select Condition(Here you can define what happens when you trigger the playbook. You can add an action, logical condition, switch case conditions, or loops.)
and add fields based on your trigger type.
Now, add nodes for both conditions(True/False)
If the condition is true(risk status is high), it’ll Send AWS Request else (risk status is medium or low) Send Email node will be triggered and then SAVE.
Testing your Playbook
Test your playbook by clicking on the ‘Test’ button and a card would show up.Add required fields and hit ‘Run Test’
To check the result of your playbooks, check logs by clicking on the “View Details”.
Runs History: shows success or failure logs
Trigger node and Test playbook node:
In the trigger node, you are setting up for multiple resources with different conditions
whereas in the test node, you are testing for a specific resource in a specific cloud account.
Basically, in a test node you fake a violation(risk) to check if it’s detected then the playbook should automatically run(if enabled ) and generate success/failure logs.
Finally, all you need to do is to move your cursor to the button to save the first playbook you just created.
And there you go! Try different templates to get a better hold of our Playbooks feature.