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
Trigger types lets you configure the workflow start time. You can either schedule or set up a recurrent trigger. There are following trigger types:
The Trigger node is the first node of any workflow.
Let's look at each of them:
- Time: Initiates a workflow based on time. You can perform the following configurations in the Time trigger type.
- Schedule: It triggers the workflow on a specific day of the week, at a specific time. If you want a workflow to start everyday at a specific time, you must select all the days of the week. This trigger is suitable for CRON jobs, Ops tasks, DR tasks, periodic auditing tasks, etc.
- Recurrent: It triggers the workflow at periodic intervals. This trigger is suitable for workflows invoking Lambda functions, Ops , or monitoring tasks. For example,
- Trigger the workflow every 5 minutes
- Trigger the workflow every hour
- Custom (Coming soon): This trigger type triggers the workflow according to a "CRON expression.” With this, you have the flexibility to define your CRON jobs according to your requirements. This trigger is suitable for a detailed schedule control that a normal Schedule trigger cannot fulfill.
- HTTP: This trigger helps initiate a workflow by calling the HTTPS URL. Each workflow has a unique HTTPS endpoint that can be used to trigger the workflow either by calling it manually or using a programmed script.
- Alarm: This triggers lets you start a workflow when a CloudWatch Alarm goes off. You can select the details from the drop down list of the following fields to configure and initiate the trigger.
- Select a region
- Select an AWS account
- Select a SNS Topic Configuration
- Select Alarm
- Event: (Coming Soon): This initiates a workflow when an API call is made logged in CloudTrail. <Place holder>
- Start a workflow at 8 am on the first Monday of each month during the year 2019. The CRON expression you could use for this is "cron(00 08 ? * 2L 2019)."
- Start a workflow at 9 am, very Friday of the month to shutdown a test env EC2 instance. The CRON expression you could use for this is "cron(00 09 ? * 6L 2019-2025)."
For more usage examples, click here.