Cost Recommendations

Cost Recommendations requires a paid plan. Enable the permission modules for the AWS services you want SnoozeDB to inspect, update the CloudFormation stack, and complete a sync.

RDS Management is always enabled. Recommendation, commitment, snapshot, and Cost Explorer modules are optional for each connected AWS account.

Each optional module adds read access for one type of analysis. The generated CloudFormation template is the source of truth for the IAM actions.

• RDS and Reserved Instance modules inspect database configuration and commitment coverage.
• EC2, EBS, AMI, and ECR modules inspect compute and storage inventory. CloudWatch metrics support EC2 utilization findings.
• Cost Explorer supplies service spend and Savings Plans coverage. It does not give SnoozeDB permission to purchase a commitment.

Permission modules and findings

• RDS recommendations use database inventory, configuration, tags, and optional commitment coverage.
• EC2, EBS, AMI, and ECR findings require their matching inventory modules.
• CloudWatch metrics provide utilization evidence for idle or right-sizing findings.
• Cost Explorer provides service spend and aggregate Savings Plans coverage for quantified impact.

A finding shows the affected service and resource, severity, evidence, estimated monthly impact, and a suggested action.

SnoozeDB detects RDS sizing or storage issues, idle EC2 instances, EBS waste, stale ECR images, old AMIs, and commitment coverage gaps.

Unknown impact means SnoozeDB has evidence for the finding but no reliable price estimate. The finding still needs review.

How to read the evidence

• Severity indicates review priority, not permission to change the resource automatically.
• Evidence records the observed configuration, age, utilization, or coverage gap behind the finding.
• Monthly impact is an estimate. Unknown means the finding is valid but cannot be priced reliably.
• The suggested action is a review path. SnoozeDB does not execute the remediation.

Eligible production RDS databases can receive a Reserved Instance coverage recommendation. A resource with detected matching coverage appears as protected with the reservation reason.

Savings Plans coverage is an account-level signal. SnoozeDB shows a recommendation when eligible compute spend remains billed On-Demand, but it does not assign aggregate coverage to one EC2 instance.

SnoozeDB does not buy, modify, or cancel Reserved Instances or Savings Plans. Review and purchase commitments in AWS.

Reserved Instances and Savings Plans are different signals

A matching RDS Reserved Instance can protect an eligible database directly. Savings Plans coverage is aggregated at account level, so SnoozeDB reports uncovered eligible compute spend instead of assigning the plan to one EC2 instance.

• Open findings still need review.
• Mark a finding as Implemented after the AWS change is complete. Owners and administrators must confirm an effective date and the monthly saving.
• Ignored findings remain in history and do not count as realized savings.
• Confirmed savings feed the dashboard and billing summaries. Estimated savings remain separate until someone confirms the result.

• Missing service findings: enable the relevant module and update the CloudFormation stack.
• Old or incomplete findings: check whether the latest sync succeeded before reviewing the results.
• Missing commitment recommendation: verify the production tags, selected account, region, and commitment modules.
• Unknown impact: review the evidence directly because the finding cannot contribute to the cost-based Waste Score.
• Locked page: Cost Recommendations requires Team, Startup, or Scale.
• No findings after a completed sync: confirm the selected account and regions, enabled permission modules, deployed CloudFormation update, and availability of the source AWS data.