How do you control storage costs as data grows over time?

Question

Accepted Answer

Storage grows forever if you let it, so I manage it by access pattern rather than by deleting things in a panic. The core idea is tiering. I match the storage class to how often the data is really read. Hot for frequently accessed data, an infrequent access tier for data touched maybe once a month, and an archive or cold tier for data that is rarely read but must be kept for compliance, each step roughly 3 to 5 times cheaper per GB. Then I automate it with lifecycle policies, rules that transition objects as they age and expire them at the end of retention. On a logs bucket that usually looks like standard for 30 days, infrequent access at 30, archive at 90, delete at 365, so cost management runs itself instead of depending on someone remembering. Alongside that I hunt orphaned storage, which is pure waste. Unattached volumes left behind when instances were deleted, snapshots kept years past their retention, incomplete multipart uploads, forgotten datasets. On one account that cleanup alone took the storage bill from about 4,000 dollars a month to 1,600. The trade off to respect is that cold tiers are cheap to store but charge for retrieval and add latency, minutes to hours for archive, so I tier on genuine access data and check that retrieval charges would not erase the savings if the data gets read more than expected. So, tier by access frequency, automate transitions and expiry, and continuously clean up orphans.

Answer

What is the trade-off of moving data to a cold/archive tier?

Much cheaper storage, but retrieval costs money and is slower (sometimes hours). Only tier data there if it is genuinely rarely accessed; otherwise retrieval fees can exceed what you saved on storage.

Answer

What orphaned storage commonly racks up cost?

Unattached volumes from deleted instances, old snapshots/backups beyond retention, incomplete multipart uploads, and forgotten buckets/datasets. They bill monthly with no value, so sweep for them regularly.

How do you control storage costs as data grows over time?

How do you control storage costs as data grows over time?

The follow-ups they ask next

What the interviewer is listening for

What sinks the answer

If you genuinely do not know

Keep going with cost

Knowing the answer is not the same as recalling it under pressure