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
Smart Scheduling allows you to automatically park your resources, when the metric (set by you) falls below the threshold value.
This ensures that you get maximum savings on your cloud bills, by parking the resources in real-time. The resources will be unparked again according to the schedule.
We can use the smart scheduling feature on any resource that can be scheduled - just pick the CloudWatch metric to be measured, and set a threshold below which it will be parked.
Setting Smart Scheduling to active for a schedule means that the resources will be stopped when according to the metric.
They will again be started according to the schedule that is set for unparking.
We will try this by setting a EC2 Instances to be parked when their Average CPU Utilization falls below 2%:
- Create a schedule to park EC2 Instances (find out how to do that here)
- After setting the parking and unparking actions, click next to view Smart Scheduling
- Namespace refers to the service being scheduled. Choose AWS/EC2.
- Set Metrics (CPUUtilization), Operator, Threshold (in %)
- Dimension is used to differentiate the various Instances in the service
- Set Statistics to Average to use the average CPU Utilization over the measured interval
- Click Save and Deploy