Object Storage rarely causes a sudden shock. It grows a little every day, and nobody owns the cleanup. That makes it a good place to look for steady, low-risk savings.
Match the tier to the access pattern
OCI offers several storage tiers, from the standard tier for data you read often, to lower-cost tiers for data you read rarely or almost never. The lower-cost tiers trade a lower storage price for access charges and minimum retention periods, so they suit data you really do keep and rarely touch, such as old logs and backups. Check Oracle's current price list before moving large amounts of data.
Let lifecycle rules do the work
Lifecycle policies can move objects to a lower-cost tier or delete them after a set age. Set them once per bucket, and review them when a bucket's purpose changes.
Housekeeping that adds up
Old object versions.: If versioning is on, previous versions keep costing money until a rule removes them.
Incomplete multipart uploads.: Failed uploads can leave parts behind. A rule can clear them out.
Forgotten buckets.: Test and proof-of-concept buckets are rarely deleted. Look for buckets with an unclear owner.
Duplicate backups.: The same data backed up by several teams is common in shared estates.
Make it visible
Break storage cost down by compartment and project, and watch the trend. A bucket whose cost climbs month after month with no matching growth in the business is the one to ask about.