Unattached EBS Volumes Still Cost Money: How to Find and Safely Remove Them
Unattached EBS volumes keep charging by provisioned GB-month even when no instance uses them.
CloudPrune resources
Short, practical guides that turn AWS cost questions into read-only checks, impact analysis, and safe next steps.
Start a read-only CloudPrune scanUnattached EBS volumes keep charging by provisioned GB-month even when no instance uses them.
Small teams want savings without buying heavy enterprise FinOps platforms.
User sees an unexpected bill and needs to identify which service caused it.
User asks the community how to identify the services behind an unexpected AWS bill.
Buyers are skeptical that tools only provide dashboards and generic recommendations.
CloudWatch charges rise because of logs, custom metrics, metric streams, dashboards, or alarms.
Practitioners want concrete alternatives and retention strategies for expensive CloudWatch Logs.
Users are confused which AWS-native recommendation source they should trust.
Users want a centralized list of AWS savings recommendations across accounts and regions.
Idle EC2 instances keep charging even when CPU, network, and application traffic show little or no useful work.
Small scheduled jobs often keep an EC2 instance running all day even though the useful runtime is only minutes or seconds.
Teams want lower AWS bills, but unsafe cost cleanup can cause downtime, data loss, or hidden operational risk.
NAT Gateway charges can surprise small teams because hourly cost and processed data charges continue even when traffic is not tied to obvious application features.
Low-use RDS instances keep charging for compute, storage, backups, and sometimes Multi-AZ capacity, but database cleanup is risky without application and rollback context.
A small AWS account can suddenly cost money because free-tier limits expired, public IPv4 addresses were allocated, storage was left behind, logs grew, or an instance kept running.