One bucket mixes web assets, SQL dumps, and app logs. A rule "move to Glacier at 30 days, delete at 365" applies to everything — including a backup the client contract requires kept seven years. Lifecycle optimized cost and broke compliance.
Scaleway Object Storage offers S3-compatible lifecycle — powerful if prefixes, versioning, and restore are planned before automation.
Anatomy of a sound rule
| Prefix | Transition | Expiration | Justification |
|---|---|---|---|
assets/ | None or Glacier 90d | No | CDN origin |
logs/YYYY/ | Glacier 30d | 400d | Internal policy |
backup/sql/ | Glacier 7d | 2555d (7 years) | Contract / legal |
tmp/ | — | 7d | Partial uploads |
Enable versioning on critical buckets; lifecycle acts on current versions — check delete marker behavior.
Glacier and restore: test before production
Run a monthly restore test on Glacier sample. Time real availability delay. Estimate restore and outbound transfer — sometimes costlier than warm storage. Document procedure in runbook (CLI or API restore).
Cross-check Scaleway sovereignty if sensitive archives in Poland vs France region.
Frequent traps
Default rule copied from US tutorial. Aggressive multipart abort — long uploads broken. No monitoring on object count per class. Replication to second bucket without aligned lifecycle. Client-side encryption + lifecycle: lost keys = dead archive.
For copy mapping, see Backup location.
The peak: automating deletion
Decide and move forward without blind spots
Inventory prefixes and legal or contractual durations before writing any rule. Create dedicated buckets or prefixes per data type. Enable versioning and test Glacier restore. Version rules in infrastructure as code (Terraform) for team review. See Scaleway profile and our guides.
Frequently asked questions
What does Scaleway Object Storage lifecycle do?
Automatic Glacier transition, expiration, and multipart abort rules — S3-compatible lifecycle API.
Is Scaleway Glacier instantly reversible?
No — restore with delay and cost; plan RTO before switch.
How to protect legal archives?
Versioning, separate prefixes, buckets without expiration, quarterly restore tests.
Lifecycle on shared prod bucket?
Risky — isolate prefixes and rules by content type.
Automate aging, not surprise — every expiration needs a named business owner.