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