Find likely-unused cloud resources by combining inventory, billing data, service activity, and lifecycle records—then confirm each candidate’s purpose and dependencies with its owner before changing or deleting it. Low or zero activity is a reason to investigate, not proof that a resource is safe to remove.
What counts as an unused cloud resource?
A resource may be unused because its project ended, its workload moved, or its owner left. It may also be quiet but still needed for seasonal demand, standby disaster recovery, backups, compliance, or scheduled work. “Unused” therefore cannot be established by one cloud-wide activity threshold.
Separate resources that are genuinely unnecessary from underutilized resources whose workload still matters. The first may be retired; the second may be right-sized, scheduled to run only when needed, or moved to a lower-cost service mode.
Build an inventory that shows what each resource supports
Start with a cross-environment inventory covering accounts, subscriptions, projects, regions, and production and nonproduction environments. Include attached and separately billed components where possible, such as storage and licenses. AWS recommends accounting for associated items during decommissioning, while Microsoft’s Azure guidance calls for inventorying workload resources and identifying orphaned assets (AWS Well-Architected decommissioning guidance; Microsoft Azure cost-optimization guidance).
Free tools Windows power users keep installed
One-click scans. No signup required.
#1 Best Overall
Enrich the inventory with tags or records for the workload, accountable owner, environment, lifecycle state, and cost center. Compare those records with current project and employee lifecycle information: an untagged resource or one tied to a completed project or departed employee is a lead to investigate, not a deletion instruction. AWS describes using tags alongside project and employee lifecycle tracking to find orphaned assets (AWS decommissioning guidance; AWS cost-allocation tagging guidance).
Use cost and activity data to shortlist candidates
Look at billing and cost-and-usage reports to find ongoing spend, then use service-specific telemetry to see how resources are being used. Native recommendations and cost workbooks can help surface idle or orphaned assets; Microsoft specifically points Azure users to Azure Advisor recommendations and cost workbooks (Microsoft Azure cost-optimization guidance).
Choose a review window that fits the service and workload. A brief quiet period may miss seasonal, infrequent, or standby use. AWS’s DynamoDB documentation gives 30 days as an example period for reviewing consumed read and write capacity metrics—not a universal rule. A sum above zero indicates traffic during that period; a zero does not establish that the table has no purpose. A global-table replica used for active/standby disaster recovery may correctly have no read traffic (Amazon DynamoDB metrics documentation).
Do not assume that stopping or deallocating a resource ends its charges. In Azure, a deployed idle resource may continue to incur costs depending on the resource, so check the service’s billing behavior before choosing an action (Microsoft Azure cost-optimization guidance).
Rank #3
- Your Personal Streaming Server - Build your own Netflix-style media library and stream 4K movies, shows and photos to any device without monthly fees
- Create Your Own Cloud - Store your entire photo, video and music collection; access from anywhere with fast 282 MB/s transfer speeds
- Creator-Grade Backup Solution - Protect your irreplaceable content with automated backups to cloud services, external drives and remote NAS
- Multi-Layered Data Protection - Combine RAID redundancy, automated backups and snapshot technology to prevent data loss from any cause
- Smart Home Surveillance - Support up to 30 IP cameras with AI detection, instant alerts and secure remote monitoring
Confirm the resource’s purpose and dependencies
Ask the workload owner to verify both workload use and the resource’s role. Check whether it supports production traffic, scheduled or seasonal jobs, backups, disaster recovery, compliance, or another infrequent need. Review dependencies and operational runbooks before making a change.
Also establish whether data must be retained, whether licenses or attached storage are involved, and whether regulatory obligations apply. AWS recommends a standardized decommission process that accounts for usage verification, compliance, and associated items (AWS Well-Architected decommissioning guidance).
Choose the least disruptive cost action
Match the action to the resource’s confirmed purpose rather than treating deletion as the default.
| Action | Best fit | Check before acting |
|---|---|---|
| Retain | The resource has a valid production, standby, backup, compliance, or other operational role. | Confirm its owner, purpose, and expected review point. |
| Right-size | The workload is still needed, but capacity or configuration exceeds its requirements. | Validate performance, resilience, and recovery requirements with the workload owner. |
| Schedule shutdown | A resource is needed only during predictable periods, often in nonproduction. | Confirm the schedule matches actual use; automatic restarts can waste money on holidays or days the resource is not needed (Microsoft FinOps usage-pattern guidance). |
| Move to a lower-cost mode or archive | The workload or data must remain available, but not in its current operating mode. | Check retrieval, recovery-time, retention, and service-specific charges. |
| Delete | The owner confirms there is no remaining need and dependencies and retention obligations are addressed. | Check backup needs, infrastructure-as-code recreation, and any deletion fees. Some Glacier archives deleted before a minimum storage duration can incur early deletion fees (Amazon S3 Glacier early-deletion documentation). |
Decommission through a controlled process
- Record the candidate. Capture its identifier, location, owner, workload, cost, activity evidence, and reason it is being reviewed.
- Confirm impact. Obtain the owner’s confirmation, check dependencies and runbooks, and verify data retention, compliance, licenses, attached storage, and recovery requirements.
- Check recreation and removal consequences. Determine whether infrastructure as code will recreate the resource and whether the service applies deletion or early-removal fees.
- Choose and approve the action. Follow the organization’s approval and notification requirements. Back up data first if it must be retained.
- Test the process before broad automation. AWS recommends validating a decommission process in a nonproduction environment before rolling it out more widely (AWS Well-Architected decommissioning guidance).
- Verify and document the result. After the change, check that dependent workloads still operate, the resource is not recreated unexpectedly, and the audit record reflects the decision and outcome.
Make cleanup part of lifecycle management
Repeat reviews when projects finish, products reach end of life, workloads are replaced, or owners change. Keep inventory, tags, and ownership records current so candidates can be traced to someone able to confirm their purpose. AWS recommends sizing review frequency and effort to potential savings rather than prescribing a universal calendar interval (AWS cost-allocation tagging guidance).
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Best Value
- COMPATIBILITY: Specially designed to mount Ubiquiti UniFi Cloud Gateway models UCG-Ultra and UCG-Max securely in place
- RACK SPECIFICATIONS: Standard 1U height rack mount bracket engineered for 10-inch rack installations, offering efficient space utilization
- MOUNTING SOLUTION: Provides stable and secure placement for your UniFi Cloud Gateway UCG Max or UCG Ultra device in server room or network cabinet setups
- PACKAGE CONTENTS: Includes one (1x) 1U 10-inch rack mount bracket specifically designed for UniFi UCG Ultra & UCG Max Gateway installations
- INSTALLATION: Purpose-built bracket ensures proper device positioning and reliable mounting in standard 10-inch rack environments
Automate candidate discovery and reporting only after owners and operators have validated the review and decommission workflow. Keep human confirmation in the path wherever a mistaken change could affect service availability, retained data, or recovery capability.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
