2026 has been a wake-up call for anyone running their own object storage. The popular MinIO Community Edition was archived in February 2026 and is now read-only. At the same time, ransomware crews keep going after backups first. For most teams the sensible answer is managed, S3-compatible object storage with immutability built in, kept close to home in Singapore.
Why object storage for backups
- You pay only for what you store, with no fixed disk to over provision
- The S3 API is everywhere, so it works with almost any backup tool
- Versioning and Object Lock keep your backups tamper-proof
- It scales from a few gigabytes to petabytes with no redesign
Connect with the AWS CLI or rclone
Point any S3 client at the Singapore endpoint. Here is what it looks like with rclone:
# ~/.config/rclone/rclone.conf [pevnix] type = s3 provider = Other access_key_id = YOUR_ACCESS_KEY secret_access_key = YOUR_SECRET_KEY endpoint = https://sgp.object.pevnix.com acl = private # list your buckets rclone lsd pevnix:
Make backups immutable with Object Lock
Object Lock plus versioning means that even a stolen server key cannot delete or overwrite your existing backups until the retention window runs out. It is the single most effective defence against ransomware.
# turn on versioning, then set a default 30-day retention aws --endpoint-url https://sgp.object.pevnix.com s3api put-bucket-versioning \ --bucket backups --versioning-configuration Status=Enabled aws --endpoint-url https://sgp.object.pevnix.com s3api put-object-lock-configuration \ --bucket backups \ --object-lock-configuration 'ObjectLockEnabled=Enabled,Rule={DefaultRetention={Mode=COMPLIANCE,Days=30}}'
Automate nightly, deduplicated backups
restic is a great fit here. It encrypts on the client side and stores deduplicated snapshots straight to S3. A simple nightly job looks like this:
#!/usr/bin/env bash # /usr/local/bin/nightly-backup.sh export AWS_ACCESS_KEY_ID=YOUR_ACCESS_KEY export AWS_SECRET_ACCESS_KEY=YOUR_SECRET_KEY export RESTIC_REPOSITORY="s3:https://sgp.object.pevnix.com/backups" export RESTIC_PASSWORD="a-strong-repo-passphrase" restic backup /var/www /etc --tag nightly restic forget --keep-daily 7 --keep-weekly 4 --prune # schedule it with: crontab -e # 15 2 * * * /usr/local/bin/nightly-backup.sh
Why the Singapore region
Keeping backups in Singapore means fast restores for teams around the region, and it keeps your data inside Southeast Asia for residency and compliance. Fewer hops, quicker recovery, and a clear answer when an auditor asks where your data lives.
