Reboot EC2 instances if CPUUtilization Goes High (Triggered by Alarm)

If CPUUtilization of the machine having an alarm set goes above 90%, the alarm will trigger this workflow. Instances with high CPUUtilizaton will be rebooted to reduce their CPUUtilization.

Adopt Template

Trigger

Use this to initiate a workflow based on time, events or call.

trigger by alarm

Resource

Select resources on which you want to work on.

Gets Instances in a specific AWS Region for EC2 service.

Filter

Enter parameters to filter resources in the workflow.

Filters the data

Filter

Enter parameters to filter resources in the workflow.

Filters the data

Action

Select action to be done on resources in the workflow.

Reboot Instances in a specific AWS Region for EC2 service.
Adopt Template

Workflow Template

Trigger

Use this to initiate a workflow based on time, events or call.

trigger by alarm

Resource

Select resources on which you want to work on.

Gets Instances in a specific AWS Region for EC2 service.

Filter

Enter parameters to filter resources in the workflow.

Filters the data

Filter

Enter parameters to filter resources in the workflow.

Filters the data

Action

Select action to be done on resources in the workflow.

Reboot Instances in a specific AWS Region for EC2 service.

Create A Template

Thank you! Your submission has been received!
Oops! Something went wrong while submitting. Please Try Again.

Request for a template

You can publish templates created by you on this platform.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Similar Templates

Create Alarms based on previous data

EC2
CloudWatch
Operational Excellence

Takes all the EC2 server and calculates the average CPUUtilization of last one month for all the Servers. Using this average CPUUtilization as threshold, new alarms are being created for the servers that doesn't have an alarm already.

Stop RDS DB Instance - Create And Close Jira Ticket

Remediation
Automation
RDS

Create a Jira ticket with DB Instance Identifiers of all Instances that will be stopped, stop the DB Instance, and then close the Jira ticket

Create an EKS Cluster and Node Group (Part 2)

Automation
Release and Deployment
EC2

Automated Deployment of a Container application in a Kubernetes cluster in AWS, including logging and monitoring attributes. Part 2 of 2.

Create a 3-Tier Application (Part 3)

Automation
Release and Deployment
EC2

Provision a 3 tier application in AWS Cloud involving a CDN, DNS, Load Balancer, VPC, Web Server, Application and Database layer, Integrated with AWS Logging and Auditing services like Cloudwatch and CloudTrail. Part 3 of 3.