Report idle AWS EC2 Instances.

This workflow send report of all the EC2 instances which are idle from the past 7 days and are launched before 7 days. Instance is identified as idle if its CPU Utilization is less than 2% and Network In/Out is less than 5MB. You can also give other configurations for this workflow.

Adopt Template

Trigger

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

Trigger after every 7 days.

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 running AWS EC2 Instances which were launched 7 days back.

Monitoring

Fetches CloudWatch Metrics of associated resources.

Injects the selected monitoring data from previous resource.

Filter

Enter parameters to filter resources in the workflow.

Filters running AWS EC2 Instances which were launched 7 days back.

Report

Use this node to generate advanced reports

Generates the report and sends it via email.

Trigger

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

Trigger after every 7 days.
Gets Instances in a specific AWS Region for EC2 service.

Resource

Select resources on which you want to work on.

Filter

Enter parameters to filter resources in the workflow.

Filters running AWS EC2 Instances which were launched 7 days back.

Monitoring

Fetches CloudWatch Metrics of associated resources.

Injects the selected monitoring data from previous resource.

Filter

Enter parameters to filter resources in the workflow.

Report

Use this node to generate advanced reports

Trigger

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

Trigger after every 7 days.

Trigger

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

Trigger after every 7 days.

Trigger

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

Trigger after every 7 days.

Trigger

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

Trigger after every 7 days.

Trigger

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

Trigger after every 7 days.
Adopt Template

Workflow Template

Trigger

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

Trigger after every 7 days.

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 running AWS EC2 Instances which were launched 7 days back.

Monitoring

Fetches CloudWatch Metrics of associated resources.

Injects the selected monitoring data from previous resource.

Filter

Enter parameters to filter resources in the workflow.

Filters running AWS EC2 Instances which were launched 7 days back.

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

Remove entries in Security Group which allow https access on public ip

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

Reboot process in EC2 machine if CPUUtilization goes high(Triggered by alarm)

If CPUUtilization of any instance having required cloudwatch alarm set, 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.

Reboot EC2 instances if the CPUUtilization goes High ( Triggered by Alarm )

If CPUUtilization of the machine having an alarm set goes above 90% then that alarm will trigger this workflow. Instances with high CPUUtilizaton will be rebooted that will reduce the CPUUtilization of those machines.