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
If you're just getting started with AWS, try creating your first EC2 instance using this this tutorial.
Forgetting to shut down instances can be the cause of unexpected increases in billing amounts. To counter this, we will be creating a workflow to stop all EC2 instances every evening.
- Click on the Editor to start making the workflow. Choose Create workflow from scratch.
- Click on the Trigger Node, and select Edit.
- Choose 'schedule', and select all the days of the week.
- Set the time as 19:00 and click 'Save'.
- This will cause the workflow to trigger at 7:00PM everyday.
- Click the '+' sign to open a new node.
- Select 'Resource' from the list. Click on the Node and select edit.
- Select 'EC2' as the service and 'Instances' as the resource, and click 'Save'.
- This will pull data on all EC2 Instances.
- Click the '+' again, and select 'Filter'
- Edit the node, and select the reference to the previous node in the 'Select data to filter' drop-down.
- Select 'Param' as filter type, enter 'State.Name' as Key, '==' as operator, and value as running.
- Click 'Save'. This will ensure that all the running instances are passed through this filter.
- Clicking '+', open an Action Node.
- Select the '...filter.instances' on from the top drop-down for the node to perform action on.
- Choose 'EC2' as the service and 'Stop Instances' as the action.
- Open a Notification Node, and select the method of notification (email or Slack). Click Save.
- Choose the AWS Account to use, and the region to run the workflow in.
- Click Run on the top-right of the Editor to save and run your workflow.