Action Node

Updated 3 hours ago by Totalcloud

What is Action Node?

Action node performs a specific action automatically on a specific set of AWS resources fetched from the previous node. Each action in this node is unique to an AWS service and is dependent on the inputs defined in the preceding node as well as current specs.

Working with Action Nodes

To define an Action node in a Workflow, follow the below steps:

  1. Go to workflow editor, after starting a new workflow or picking a new template
  2. If you start a new workflow:
    1. Click on the Action icon available on the left navigation menu.
    2. Double click on the Action node to access the parameters input window.
  3. If you pick an existing template:
    1. Double click on existing Action node to access the parameters input window.

  1. Select the service you want to act on.
  2. Select the action you want to take.
  3. Click on Save Node.
You can customize or fine tune your Action node, using Additional Parameters option. You can pass all the additional parameters supported in the AWS API SDK Doc here.

What happens in Action Node?

Action node inherits the properties of the previous node and takes timely action on filtered resources as per the user's command. The input to Action node is typically from Resource node, filter node, and/or User Approval node.

Let's look at each input scenario using an use case example of taking snapshots of either all or specific EC2 volumes belonging to Oregon region, and check out how Action node behaves.

Scenario 1: If the preceding node is a Resource node

If the preceding node is a Resource node, the Action node will:

  1. Fetch all the EC2 Volumes' snapshots from the Resource node.
  2. Create snapshot of all the filtered volumes using Create Snapshot action command.

Please find below the sequence of steps essential to carry out this use case.

Outcome

In this node, the action 'Create Snapshot' will run on all the EC2 volumes belonging to Oregon region.

​​Scenario 2: If the preceding node is a Filter node

If the preceding node is a Filter node, the Action node preforms action on the resources retained post filteration in Filter Node.

Example: Suppose, you want to create snapshots of only those EC2 volumes that belong to Tags User.Stack: Testing. You can use Tag filter prior to Action node and use the action Create Snapshot only for those volumes. Observe the below sequence of steps essential to carry out this use case.

Outcome

In this node, the action 'Create Snapshot' will be only on EC2 volumes belonging to Oregon region with Tags User.Stack: Testing.

Scenario 3: If the preceding node is a User Approval node

If the preceding node is a User Approval node, the Action node executes and takes appropriate action only upon receiving "Approved" command from the approver via an email. If the approver "Disapproves" the command, the action goes void.

Example: Suppose, you want to take snapshots of EC2 volumes that belong to Tags User.Stack: Testing only upon approval from the CloudOps Lead engineer. Use the User Approval Node to take approval before taking any action on the resources.

Outcome

In this node, the action 'Create Snapshot' will run on EC2 volumes belonging to Oregon region and having Tags User.Stack: Testing only upon Approve command from the email address CloudOpsLead@TotalCloud.io.

Usage Examples

For your convenience, we have populated several usage examples of how to use this node and how to set their parameters. Do check them out.


How did we do?