Stopped EC2s look harmless, but storage and dependencies keep costs alive long after compute is paused.
Most tools stop at visibility. OpsCurb treats findings like work: identify the resource, assign the owner, and keep follow-through visible until it closes.
Start with the Core Scan Role, add optional capabilities later, and review the public permission mapping before you connect.
Frame the issue in monthly and annual impact so the cleanup gets prioritized and tracked.
Use evidence, guardrails, and handoff language instead of raw AWS screenshots alone.
Teams pause instances to save money, then leave them in the queue “for later” until later never comes.
The real drain is usually orphaned storage and ownership handoff, not the stopped node itself.
Before you terminate anything, confirm intent: rollback, audit retention, or true decommission.
Then check stop duration, attached volume usage, and the last deployment or incident reference.
Terminating while dependencies are unclear can remove pre-baked recovery paths.
Even if terminated, snapshots and logs may still be needed for audit replay.
Stopped instance cleanup is usually a steady monthly savings lever because teams can remove them in small batches with low risk.
The larger payoff is process: each resolved stopped instance reduces future "forgotten workbench" noise and rework.
OpsCurb surfaces stale stop-state resources as part of recurring scans and keeps them in the same owner queue you already use for cleanup.
That makes it less likely they drift back into the account and remain dormant for months.
These are the friction points teams usually need to clear before they turn a likely savings opportunity into a real cleanup task.
Yes, if rollback windows are explicit and documented. Put a reason and revisit date in the finding notes so review is intentional.
No. Some are valid backups for release or rollback. The right action is validate intent, then choose stop/archive/release.
No. OpsCurb only gives evidence and prioritization. Your team performs the final action.
Move from research to action with a tutorial, a sample brief, a live review, or an ongoing plan.
Related guide: set up the OpsCurb Core Scan Role
Start with narrow read-only discovery before cleanup decisions.
Open pageHow to audit EBS waste across regions
Pair stopped instance cleanup with storage cleanup for faster monthly wins.
Open pageCompare OpsCurb vs CloudHealth
See why exact resource follow-through still matters after broad reporting.
Open pageSee the sample first-scan report
Preview how stopped-instance findings can be prioritized in context.
Open page