Storage Optimization Score Calculator

waste = unattached share + 0.5 x orphan snapshot share + 0.6 x noncurrent version share + 0.15 x uncovered bucket share + 0.2 x gp2 share, all x spend, plus abandoned upload GB x rate; score = 100 − 1.2 x waste share. Each lever gets a recovery factor rather than being counted in full, because not every noncurrent version or snapshot is safe to delete: unattached volumes are fully recoverable, orphaned snapshots about half, and a gp2 to gp3 migration saves roughly 20% of the volume line. Multipart uploads are handled separately because abandoned parts are billed as storage but are invisible in the object listing, so they never appear in a bucket size report. Weights and rates here are user-supplied estimates and list prices — confirm the prices for your region and calibrate the factors against your own cleanup results.

It turns a vague sense that storage costs too much into a ranked list with a number attached, so the first cleanup sprint targets the lever with the largest recoverable spend rather than the easiest one.

This calculator takes 8 inputs: Monthly AWS storage spend, Share of buckets with a lifecycle policy, Share of spend on unattached EBS volumes, Share of spend on snapshots of deleted volumes, Share of spend on noncurrent object versions, Share of spend still on gp2 volumes, Incomplete multipart upload data, Storage price for the abandoned uploads. The pre-filled defaults are a realistic starting point — replace them with figures from your own environment for a result you can act on.

Uploaded parts are billed as storage but do not appear as objects in the bucket, so they are absent from ListObjects and from most size dashboards. Only an AbortIncompleteMultipartUpload lifecycle rule or a ListMultipartUploads call reveals them.