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
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

Reboot Process in EC2 instances (Triggered by Jira)
EC2
Remediation
Remediation

Jira ticket with required summary will trigger this workflow. Apache (httpd) server inside the Instances will be rebooted for those instances which have the same tag that are mentioned in the description of Jira ticket. This rebooting of the process will decrease the CPUUtilization of the machine.

Bundle And Archive - S3 Glacier Movement
S3
S3 Glacier
Remediation
Automation
Cost Saving

Significantly reduce cost incurred when moving objects to S3 Glacier by automatically bundling the objects and then moving them

AutoScaling Group Automation
AWS Auto Scaling
Remediation
Automation
Automation

Create an AMI from an EC2 instance. Update the Launch template version for the AMI created. Update the Auto scaling group with latest version of updated AMI. Detach/Terminate the old EC2 resources.

Reboot EC2 instances - Any Source (Jira, Manual)
Remediation
EC2

Reboot EC2 Instances from Jira (based on tags mentioned in the ticket description) or by manually entering the variable values. Values passed through tickets will override the default values.

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%

Reboot process in EC2 machine (Triggered by alarm)
EC2
Remediation

If CPUUtilization of any instance having required cloudwatch alarm set, If CPUUtilization goes high then this workflow will be triggered and it will lower down the CPUUtilization of the machine by rebooting the process inside the machine.

Upgrade EC2 Machines ( Triggered by JIRA )
EC2
Remediation

Jira ticket with required summary will trigger this workflow. Instances having the same tag that are mentioned in the description of jira ticket will upgrade to their next level once the CPUUtilization goes high . This will reduce the CPUUtilization of that machine.

Upgrade EC2 Machines ( Triggered by Alarm )
EC2
Remediation

If CPUUtilization of instances having an alarm set goes above 90% then this workflow will be triggered and it will upgrade the EC2 machine to their next level if CPUUtilization goes high. This will eventually reduce the CPUUtilization.

Backup and Terminate EC2 Instances ( Triggered by JIRA )
EC2
Remediation

Jira ticket with required summary will trigger this workflow. AMI backup and EBS snapshot of Instances will be taken as a backup of the instances having the same tag that are mentioned in the description of jira ticket

Launch EC2 instances from AMI ( Triggered by JIRA )
EC2
Remediation

Jira ticket with required summary will trigger this workflow. Instances will be launched on AMI's having the same tag that are mentioned in the description of jira ticket

Reboot EC2 instances ( Triggered by JIRA )
EC2
Remediation

This workflow will reboot EC2 instances if CPUUtilizatin goes high and Jira ticket with required summary will trigger this workflow. Instances having the same tag that are mentioned in the description of jira ticket will get rebooted. This will reduce the CPUUtilization of that machine.

Reboot process of unhealthy servers associated with a target group
EC2
Remediation

Reboots the process running in unhealthy EC2 machines associated with a target group.

Unrestricted Elasticsearch(9200) Access
EC2
Security
Remediation

It is AWS best practice to remove entries in security group which allows Elastic Search access from public IP to reduce possibility of breach. Allowing unrestricted Elastic Search access can increase threats like hacking, denial-of-service (DoS) attacks and loss of data.

Remove Entries in Security Groups Which Allow RPC (TCP Port 135) Access From Public IP
EC2
Security
Remediation

It is AWS best practice to remove entries in security group which allows RPC access from public IP to reduce possibility of breach. Allowing unrestricted RPC access can increase threats like hacking, denial-of-service (DoS) attacks and loss of data.