What is Resource Scheduling?
TotalCloud Resource Scheduler Vs AWS Instance Scheduler
Case 1: EC2 Instances
Case 2: Instances in ASG
Case 3: Instances in ASG (Without Termination)
Case 4: RDS DB Instances
Case 5: Redshift Clusters
Trigger Actions Externally
Advanced Filters in the Resource Node
Add-ons in the Resource Node
Usage Examples of Resource Node
Sample JSON Output
Sample JSON Output II
Types of Filter Node
Security Group Filter
Usage Examples of Filter Node
User Approval Node
Workflow Trigger Node
Getting Started with Nodes
Spot EC2 Instances
Schedule Start AWS EC2 Instances
Schedule Stop AWS EC2 Instances
Delete Unattached AWS EBS Volumes
Periodic Snapshot of EBS Volumes
Terminate Inactive Workspaces
Notify Publicly Open AWS RDS Instances
Notify About Inactive Users
Notify All Public Amazon S3 Buckets
Create a Rule for EC2 Security Group
Revoke Rule From EC2 Security Group
Monitor Amazon EC2 Instances' State
Create Workflows Using Templates
Create Workflows From Scratch
Stopping EC2 Instances Every Evening
Workflow Policy Validation
Use Jira Tickets to Alter EC2 Instances
Use Jira Ticket to Reboot Instance
Use Jira Ticket to Reboot Instance Process
Use Jira Ticket to Upgrade Instance
TotalCloud vs Terraform vs CloudFormation
Listing Workspace Errors In Terraform
Creating Terraform Infrastructure
Table of Contents
What is Filter Node?
The Filter node selectively retains a subset of AWS resources from a large set of particular AWS service as per the conditions and nested conditions defined in this node’s parameter window or according to the parameters derived from the previous Resource node.
Working with Filter Nodes
To define a Filter node in a Workflow, follow the steps below:
- Go to the workflow editor, and start a new workflow or select an existing template
- If you start a new workflow:
- Click on the plus symbol
- Select 'Resource' from the options below
- Click on 'Edit' to access the parameters input window
- If you pick an existing template:
- click on the 'Edit' option existing Filter node to access the parameters input window.
Example: If you need to take action on IAM users whose Access Keys age are greater than 90 days – and want to delete these old IAM roles, you need to define conditions in the Filter node as shown below.
- Use And or Or to define multiple conditions and sub-conditions to refine your workflow as per your needs.
- Click on 'Save' after you set the parameters according to your requirement.
For your convenience, we have pre-configured filters.
Types of Filters
- Param: Helps filter resources by their attributes or their Add-ons attributes.
- Tags: Helps filter resources by their tags.
- Security Group: Helps filter certain resources based on the properties of Security Groups associated with those resources or directly on the Security Groups themselves. Note that it is applicable only to EC2 SGs, Cluster SGs, mount target SGs, Cache SGs, DB SGs and Stale SGs.
- Network ACLs: Helps filter certain resources based on the properties of NACL Rules associated with those resources or directly on NACL. Note that it is applicable to subnets that have associated NACL Rules.
- Function: Helps selectively filter resources using custom Java scripts, when none of the other Filters work.
- Time/Date: Ideal for filtering resources based on date value, such as 'Launch Time'.
For your convenience, we have populated few usage examples showcasing how to apply filters for some common use cases. Check here.