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
TotalCloud's Resource Scheduling feature allows you to significantly reduce cloud billing by starting and stopping resources according to predetermined schedules. This ensures that your resources are in the active state only when they are required.
Check out a step-by-step tutorial on how to schedule EC2 Instances:
Scheduling resources can save you up to 60% on your cloud bills.
If you have non-essential EC2 Instances that you can stop outside business hours (9AM to 6PM on weekdays):
Before Resource Scheduling
- Number of hours run = 24 X 7 (everyday) = 168 hours
After Resource Scheduling
- Number of hours run = 9 x 5 (9AM to 6PM on weekdays) = 45 hours
You can schedule a variety of resources, including EC2 Instances (with and without Auto Scaling Groups, with and without Instance termination), RDS DB Instances and Redshift Clusters
Setting standard schedules allow you to stop your non-essential resources outside business hours and other periods of low usage. Once you set them, the resources will be parked and unparked on their own.
The smart scheduler allows you even more optimisation, by automatically parking your resources in real-time. This can be done by choosing the resources to be parked when a selected metric goes below the threshold level.
Eg. Setting your EC2 Instances to be parked when CPU Utilisation goes below 10%.
Some other features that can be used to enhance your schedules:
Set schedules to be triggered one after the other by linking two of them. This can be done by selecting the options for any schedule.
Use the HTTP links for start and stop actions to trigger them from outside apps.
- Recommendations (coming soon)
Use smart recommendations that suggest the best resources to schedule, for maximum savings.
To try out Resource Scheduling on TotalCloud, login here.
This gives you an overview of all Groups that have been scheduled, their status and the estimated monthly savings in your billing.
Try creating Groups to test Resource Scheduling: