Usecase Universe

A collective of use cases for DevOps teams

Browse a variety of 200+ predefined templates to automate all your AWS actions

Create Template
Solutions
All Categories

Remediation

24 Times Used
22 MAY 2019
Increase EBS Volume size if Instance disk utilisation reaches 90%
EC2
Remediation
AWS Best Practices
Remediation

Increases EBS Volume size when the instance's disk utilisation exceeds 90%

Modify Instance Type if CPU Utilization <10% For a Week
EC2
Cost Saving
Remediation
Cost Saving
Remediation

If CPU utilization is less than 10% for a week, you are not utilizing the instance efficiently. This workflow identifies such instances and switches them to another instance type.

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

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.

Copy EC2 Logs Data to S3 and Delete the Log Folder
S3
EC2
Remediation
AWS Best Practices
Remediation

Moves the logs present in the log folder of EC2 machine and transfers them into a specified S3 Bucket. This practice helps you to store the logs you want, without worrying about the disk space in the machine.

Reboot RDS DB instances (Triggered by JIRA)
RDS
Remediation
Remediation

Objective of this workflow is to reboot the RDS DB instances whose DBConnections goes high. Jira ticket with required summary will trigger this workflow. RDS DB Instances having the same tag that are mentioned in the description of jira ticket will get rebooted. This will reduce the CPUUtilization of the DB instance.