The Resource node defines the resources belonging to a particular AWS service that you want to center your workflow around. The node can access any AWS resource and any AWS service available to you on the AWS SDK (for Azure & VMware, we have a separate ‘Azure Resource’ and ‘VMware Resource’ node’, which we’ll cover later).
To add a resource node, click on the ‘+’ and select ‘Resource’. This usually comes initially, as the second or third node of the workflow when you’re defining the resource you want to work on. Click on the node and select ‘edit’ to open the parameters options for the nodes.
In the Resource node, you’ll find the ‘Node Name’ and the ‘Node ID’ as usual. Select appropriate inputs in each drop-down menu to define your requirement. ‘Select a service’ refers to an AWS Service, like “EC2” or “CloudWatch”, and ‘Select a resource’ refers to a resource pertaining to the selected service, like “Instances” or “Alarms” respectively.
Because we’re fanatics of customization, we also offer ‘Additional Parameters’ and ‘Add-ons’. This allows for additional granularity while selecting resources. Like Node IDs, each resource attribute is given an ID; this enables you to perform actions on a specific attribute of a resource, along with actions on a filtered resource. This is called ‘resource referencing’.
Additional Parameters allow you to pass advanced parameters with a query, which changes the way we fetch your resources.
You can refer to the corresponding AWS API documentation page while passing the additional parameters. For example: The additional parameters supported for EC2 Volumes would be whatever AWS supports in describeVolumes API.
Add-ons allow you to enrich the resources data with additional qualities. You can use this enriched data in successor nodes, like the Filter node, to selectively retain the resources required.
For Example: Let's say you want to fetch instances that have port 22 open. When you fetch data of EC2 instances in the Resource node, it has the attributes of instances alone. To filter instances that have an open port, you will need Security Groups associated with each instance. This requires us to fetch additional qualities of a resource, i.e. Add-ons. So, you will select Security Groups in the Add-ons for the fetched EC2 instances in the Resource node. The original data is enriched by the addon data.
Similarly, Volumes can be add-ons for EC2 instances, and Bucket Policies can be add-ons for S3 buckets.
The attributes of Add-ons are the same as returned by the corresponding AWS API. So the data of describeSecurityGroups is available as output in addOns.Securitygroups when you select EC2 instances as resource and Security Groups as Add-ons in the Resource node.