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

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.

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

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

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

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.

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.

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.

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

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

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.

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

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.

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.