What is Resource Scheduling?
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
Using Jira Ticket
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
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
The goal of this workflow is to create a ticket on Freshdesk( ) if the CPU utilization of an EC2 instance is less then 10%.
- Trigger node
- Resource node
- Filter node
- Monitoring node
- Filter node
- HTTP node
This is how the workflow looks:
This node sets the workflow to trigger everyday (recurrently)
From the resource node you can pick the desired resource - here the example uses EC2.
The filter node separates the running instances from the pool of instances.
The metric of monitoring the instance is CPU utilization. We check if the CPU utilization of the instance is less then 10%.
We use a filter node again to segregate the instances with CPU utilization less than 10% from those with higher CPU utilization.
Lastly we will use the HTTP node:
- Select input collection - here we enter the node reference of the previous node i.e the filter node in this case
- Method - Here we enter the type of HTTP request that we want to make such as GET, PUT, POST, DELETE. So we add POST in the method option as the POST carries request parameter in the message body.
- Endpoint URL- Here we add the final destination where you want the HTTP call to trigger. We have taken our Freshdesk URL as that the endpoint in this usecase.
- Headers - The type of file that we want to send needs to be added here as you can see from the example ours is a JSON file.
- Body- The data that we want to send is to be written here this can vary for each usecase.
- Basic Auth - Basic Auth the authentication that you want to attach with this HTTP request. Using Basic Auth is a helps to secure the data.