S3-compatible storage¶
The S3 Storage integration mirrors locally created wireops backups to an S3-compatible bucket. The local backup remains the primary copy; the remote object is an additional off-host copy for recovery.
Configure¶
Enable S3 Storage in Settings → Integrations.
| Field | Required | Description |
|---|---|---|
| Bucket | Yes | Bucket that receives backup objects. |
| Region | Yes | Provider region, such as us-east-1. |
| Endpoint | No | Custom S3 endpoint for R2, MinIO, B2 or another compatible service. |
| Prefix | No | Object prefix, such as wireops. |
| Access Key / Secret Key | Yes | Credentials allowed to write and restore only this bucket/prefix. |
| Force Path Style | No | Usually needed by MinIO and some compatible endpoints. |
| Encrypt Content | No | Enabled by default; encrypts backup content before upload. |
| AWS KMS | No | Optional AWS KMS key ID and region for managed key wrapping. |
Validate and recover¶
Create a backup, verify that its object appears under the expected prefix, then test a restore according to disaster recovery. A backup is not proven until a restore has been tested.
Security¶
Use a dedicated, least-privilege bucket credential. Restrict its prefix, enable provider-side versioning where appropriate, and retain encryption keys for as long as the backups they protect must remain recoverable.