Skip to main content
Idle Policy Setup

Learn how to configure automated hibernation for your EC2 instances

Updated over a week ago

This feature allows you to automatically shut down resources that aren't operating at full capacity. You can set the desired CPU utilization percentage, and when your resource falls below that configured threshold, it will be automatically put into hibernation. You no longer have to keep a close watch on CPU usage.

Notes: The idle policy handles only instance hibernation

To begin, go to Cloudsitter and click on the 'Create Policy' button.

Within this new policy, you should provide a name, select the 'Idle Policy' type, and attach the necessary resources. By default, resources will enter hibernation mode when their CPU utilization drops to 10%. You have the flexibility to adjust this percentage to your preference. When CPU utilization is less than or equal to this threshold, the policy will initiate hibernation for your resources. You can also configure the duration a resource should remain idle before being put into hibernation. Once you've filled in all the required details, click 'Save.'

If you add a resource to an existing idle policy, it will only enter hibernation mode after one hour, assuming all necessary conditions are met. If you create a new policy and immediately add a resource to it, the policy will be able to initiate hibernation within 5 minutes.

To receive email notifications, you can enable the 'Email Notifications' slider. By default, the field will display the email address you provided during registration on the site. You will receive an email notification if the policy encounters a failure, which could occur if it cannot power on or off your resources due to specific reasons. You also have the option to add another email address or disable notifications.

Here's an example of what the notification looks like:

Note: Only EC2 instances can be associated with the Idle Policy.

You can switch between an idle policy and a regular one, and vice versa.

You can locate the CPU utilization level of an instance in the AWS console under the monitoring section of a specific EC2 instance.

Did this answer your question?