Tenant Media App Backup Retention: Private Object Storage Lifecycle
For a media app, keep each tenant's backups in a private object-storage namespace, make the snapshot key immutable, and let a lifecycle rule expire ordinary snapshots after 30 days. The important decision is tenant isolation, not the deletion syntax: a restore must never be able to select another customer's bytes, and an expiry rule must not be mistaken for an immutable archive. That sounds…
Media applications should store each tenant's backups in a distinct, private object storage namespace. The snapshot key must be immutable to prevent accidental modification. Implement a lifecycle rule to expire regular snapshots after a 30-day retention period. The critical aspect is ensuring tenant isolation, not the specifics of deletion or restoration.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
