AWS · Storage and costs
S3 storage optimisation
Summary
A regular cost review showed that several buckets were keeping versions and data that were no longer needed. I analysed the growth, defined lifecycle rules and reviewed a replication that no longer provided value.
- My role
- Analysis, rule design and implementation of changes.
- Result
- Several TB of storage removed.
- Reduction
- More than 80% in the analysed buckets.
- Validation
- Monitoring of storage and later invoices.
DetectionCosts and growth
AnalysisVersions and replication
ChangeLifecycle policies
ControlMetrics and invoice
The problem
The visible data volume did not explain the cost by itself. Part of the growth came from old versions and inherited configurations that continued to keep or replicate objects.
Deleting data manually would only solve the symptom once. The goal was to understand the growth and leave rules in place to prevent the same problem.
What I changed
- I reviewed versioning and storage distribution.
- I defined lifecycle rules for versions that no longer needed to be kept.
- I removed accumulated historical versions in a controlled way.
- I disabled a replication that no longer had an operational need.
- I then checked storage use and the effect on costs.
Result
The total volume of the analysed buckets decreased by more than 80%. I later confirmed that the reduction was also visible in the following invoices.
Several TBless accumulated storage
>80 %volume reduction
Activelifecycle rules to prevent the issue returning