Identify any Amazon EC2 instances that appear to be idle and stop or terminate them to help lower the cost of your monthly AWS bill. By default, an EC2 instance is considered 'idle' when meets the following criteria (to declare the instance 'idle' both conditions must be true):
This rule can help you with the following compliance standards:
This rule can help you work with the AWS Well-Architected Framework
This rule resolution is part of the Cloud Conformity Cost Management tool for AWS
Idle instances represent a good candidate to reduce your monthly AWS costs and avoid accumulating unnecessary EC2 usage charges.
To identify any idle EC2 instances currently available in your AWS account, perform the following:
Option 1: stop or terminate the idle instances. To shutdown/terminate any AWS EC2 instances that are currently running in idle mode, perform the following commands:
Option 2: turn off the idle instances at night. To implement a shutdown/startup routine for your expensive (large or xlarge) AWS EC2 instances that are currently available in idle mode to run only during the daytime, perform the following commands:
Option 3: stop or terminate automatically the idle instances using AWS CloudWatch alarms. More details about this method can be found on the AWS documentation page.Note: These CloudWatch alarms can use only the CPU usage (CPUUtilization metric) as input data, therefore the method does not satisfy the conditions set by this conformity rule.
Option 4: disable the rule check. If the selected idle EC2 instance is needed (its role within your application stack/environment is important), you should turn off the conformity rule check for the instance from the Cloud Conformity console.