New See exactly what you're overpaying AWS in under 60 seconds. Try the Calculator for free

Orphaned Snapshots

An orphaned snapshot is an Amazon EBS (Elastic Block Store) backup that continues to incur storage charges after the EC2 instance or volume it was created from has been deleted.

How It Works

When you create a snapshot of an EBS volume in AWS, that snapshot is stored independently in Amazon S3 at a per-GB monthly cost. If you later terminate an EC2 instance or delete the underlying EBS volume without also deleting the associated snapshots, those snapshots remain in your account and continue to accumulate charges. Because snapshots are not automatically removed when their source volumes are deleted, they can quietly persist for months or years. Teams rarely notice them because they do not appear alongside running resources in the EC2 console and are easy to overlook in billing reports.

Why It Matters for Cloud Cost

Orphaned snapshots are one of the most common sources of invisible cloud waste. Each individual snapshot may cost only a few dollars per month, but accounts with high instance churn, frequent deployments, or long-running automated backup jobs can accumulate hundreds or thousands of orphaned snapshots. The cost compounds over time because nobody is actively tracking them. Unlike idle EC2 instances, orphaned snapshots generate no alerts and cause no performance issues, so they rarely surface without a deliberate audit. Cleaning them up requires identifying which snapshots have no associated active volume, confirming they are no longer needed, and deleting them. Without a systematic process, this waste continues to grow invisibly alongside legitimate infrastructure spend.

Usage AI: ClearCost is Usage AI’s visibility and showback reporting layer, giving teams the cost transparency needed to identify and address waste across their AWS environment.

See how Usage AI saves 30 to 50% on AWS, GCP, and Azure.