Skip to main content

Use Case for AWS RDS Idle DBInstance Check

  1. Configure AWS RDS Idle DBInstance Check
  2. Use Case for AWS RDS Idle DBInstance Check
  3. Triage Guides by Violation Type
    1. Triage AWS RDS Idle DBInstance Check IDLE_INSTANCE_DETECTED

AWS RDS Idle DBInstance Check Policy Content

Why use this policy?​

This policy is designed to identify AWS RDS DBInstances that are potentially underutilized, which we'll refer to as 'idle'. Identifying idle RDS instances can help organizations reduce waste and save costs. Having instances that are not actively used still incurs cost, and this policy aids in recognizing such instances so appropriate actions can be taken.

Pros and Cons​

Pros:

  • Cost Optimization: Helps in significantly cutting down unnecessary expenses on unused resources.
  • Resource Management: Allows for better allocation and utilization of resources within AWS.

Cons:

  • False Positives: May incorrectly flag instances that have periodic, yet vital usage outside the observation window.

How does the policy work?​

The policy uses AWS CloudWatch to observe and gather the average CPU and memory utilization over a 7-day period for AWS RDS DBInstances. It flags instances where both CPU and memory utilization are below the specified thresholds.

Variables and their defaults​

  • cpuThreshold: Default is 2. Specifies the threshold for average CPU utilization percentage below which the instance is considered idle.
  • memoryThreshold: Default is 2. Specifies the threshold for average memory utilization percentage below which the instance is considered idle.

Violation Types​

The policy defines one violationTypeId:

  • IDLE_INSTANCE_DETECTED: This violation type is used when an RDS DBInstance's CPU and memory utilization are both below the defined thresholds.