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
What is a workflow trigger node?
A workflow trigger node triggers one workflow as a result of another. So a workflow is triggered based on the needs of the first workflow.
This can be understood with an example:
Our goal is to copy an RDS DB cluster from a single availability zone to multi availability zone to increase reliability and then convert it back to a single availability zone for frugal usage.
For the first workflow
- Workflow trigger
For the 2nd workflow
This is how the workflow will look:
The trigger is set to activate this workflow everyday (this may vary for each use-case).
In the resource node we pick the AWS resource on which we want to work. We have chosen RDS clusters.
In the filter node there are two parameters on the basis of which we separate the RDS clusters - the clusters that are in a single availability zone and the nodes which don't have an aurora engine.
The Action node is performing the action of converting the RDS cluster from single availability zone to multi-availability zone.
After the RDS clusters are converted from single availability zone to multi availability zone we will convert them back to single availability zone for frugal utilisation of our resource. This can be done with an existing workflow which we trigger through this node. The node has a drop down of all the workflows that you have in your account, and you can choose the next workflow to be triggered.
The second workflow that is being triggered looks like this:
Let's look at all the nodes:
The trigger node runs everyday (this may vary for different use cases)
In the resource node we pick the AWS resource on which we want to work - RDS instances in this case.
The Action node converts the RDS instance from multi-availability zone to single availability zone.
This node send a report of the workflow to the desired E-mail ID or Slack.