From the billing CSV provided, CloudSaver flagged 4 items worth a human review. We do not state a guaranteed saving figure. Items with clear bill evidence (an unattached Elastic IP, a stale snapshot) can return their cost only after you confirm they are truly unused. The two remaining items are large compute / standard-tier storage where CloudSaver cannot see utilization or access frequency from the bill — those are listed as verify first, no saving claimed. Every item lists what to check before you act, so nothing production-critical is touched blindly.
| Item | Current cost | What we found (bill evidence) | Verify before acting | Blind-delete risk |
|---|---|---|---|---|
| 2 unattached Elastic IPs | $7.20 | Elastic IPs not associated with any running instance (bill shows "unassociated"). | Confirm neither EIP is referenced by a NAT gateway or held for a pending instance. | Low |
| Stale EBS snapshot | $24.50 | Snapshot older than 90 days with no associated active instance in the bill. | Confirm no open restore request and no compliance / retention hold. | Medium |
| Large instance (c5.4xlarge) | $312.10 | Large instance type detected. CloudSaver cannot see CPU / utilization from the bill. | Check CloudWatch: only right-size if utilization is consistently low. No savings claimed without usage data. | Low |
| Standard-tier storage (S3) | $67.80 | Standard-tier storage over $10/mo. CloudSaver cannot see access frequency from the bill. | Check access patterns; move only confirmed-cold data to IA / Glacier. No savings claimed without access data. | Low |
CloudSaver flags items from your billing CSV and gives you the checks to consider before acting — it does not automatically delete anything and does not claim a guaranteed saving. For items that need utilization or access data, you confirm in AWS, then decide. This keeps the decision — and the risk — with you, where it belongs.