This section outlines the configurable preferences used by the Waste Detector engine to surface optimization recommendations for idle, underutilized, or misconfigured cloud resources. These preferences ensure that the recommendations are relevant, aligned with business policies, and actionable.

❓

Notes

1. The updated preferences will be used from the next invoice for new recommendations.
2. The updated preferences will be immediately close an existing recommendation, it will be effective after 8 days due to a timeout mechanism.

Key Capabilities

Some of the

• 🗓️ Loopback Period (Days to Check)
  Defines the historical timeframe the engine analyzes to detect waste patterns.
• 📅 Activity Days
  Specifies the number of days a resource must be idle to be considered a waste candidate.
• 📉 Thresholds
  Set the utilization limits below which a resource is considered underutilized or idle.
• 💰 Potential Saving Calculation
  Estimates the monthly cost savings achievable by deleting, stopping, or resizing the resource.
• 🧠 Instance Type & Architecture Exclusions
  Lets you exclude specific instance families or architectures from waste detection logic.