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 HTTP node?
HTTP node can be used to make HTTP(S) calls from a workflow. The HTTP node has several abilities that help one integrate to tools like calling an API endpoint or a ticketing system such as JIRA, Freshdesk to name a few. This can also be used to trigger one of Totalcloud's workflows. You can add new collections, update existing collections, override existing databases, or delete the database directly through this node. Predominantly any software system that has a HTTP end point can be triggered through this node.
An API request lets you contact a server with API endpoints that you want to reach and perform some action. Those actions are HTTP methods. If you are using APIs to build client-side applications - mobile apps, websites or desktop applications - you might want to see the actual HTTP request traffic that is being sent and received in the application.
Lets look at all the parts of a HTTP node:
Select input collection
Each node in workflow can refer to the output of any other node in a workflow that was executed before it. lets say in a workflow A->B->C->D , C can refer to B’s output and A’s output, similarly D can refer to A,B, and C’s output as it’s input. We select this using “Select Input Collection”
There are various methods that correspond to any valid HTTP request method. One can capture the HTTP requests using the following: GET, PUT, POST, DELETE. As the name suggests the GET method lets you fetch data from a specified resource, the POST method lets you extract data from a specified resource and so on with the PUT and DELETE methods. For more details on the basics of what they do click here.
An Endpoint URL is the final location where you want all the work done to reflect.
For a usecase example click here.