Savings & Reports
Trace where each estimate comes from and keep realized savings separate from open opportunities.
The savings model
SnoozeDB separates savings by provenance so a recommendation is never counted as money saved before it is implemented.
| Measure | What it represents |
|---|---|
| automated | Estimated savings from time that SnoozeDB kept managed resources stopped. |
| confirmed | Savings from a recommendation that a user marked as implemented and confirmed with a monthly amount and effective date. |
| realized | Automated savings plus confirmed savings for the selected period. |
| potential | Estimated opportunity from unresolved findings. It remains separate from realized savings. |
Automated savings
Automated savings come from recorded stopped runtime for managed RDS and EC2 resources. SnoozeDB combines that runtime with the available on-demand price for the resource.
A schedule is not counted simply because it exists. The estimate depends on the activity recorded for the selected period.
Confirmed savings
A cost recommendation begins as open potential. After you implement the change outside SnoozeDB, record the decision and confirm the monthly amount when you have evidence for it.
The ledger keeps the effective date and optional end date. This preserves the recommendation history even when later syncs update or close the original finding.
- Review the finding and its supporting evidence.
- Make the change in AWS or through your normal infrastructure workflow.
- Mark the recommendation as implemented and confirm the monthly amount.
- Add an end date if the saving no longer applies.
Monthly calculation
Confirmed savings are prorated independently for each calendar month. Both the effective date and end date count as active days.
Pricing limits
Savings are operational estimates, not AWS invoices. Before using them in a financial report, account for the limits that apply to your environment.
- On-demand RDS and EC2 prices are used when a matching price is available.
- Reserved pricing, Savings Plans, negotiated discounts, taxes, credits, and data transfer can make the AWS bill differ.
- Confirmed recommendation amounts depend on the evidence entered by your team.
- Open potential can change as resources, prices, and findings change.
Reports and billing recaps
Monthly reports summarize the previous period for the active organization.
- Realized savings for the month.
- Stopped hours and estimated CO₂ avoided.
- The number of managed resources.
- Top RDS and EC2 resources by estimated saving.
Troubleshooting
- Unexpected total: compare automated and confirmed savings separately before checking the combined amount.
- Missing confirmed amount: verify the implementation status, monthly value, effective date, and optional end date.
- Missing automated amount: check the resource activity log, pricing coverage, and selected month.
- AWS bill differs: review commitments, discounts, credits, taxes, and services outside SnoozeDB's estimate.