Appearance
Object storage (S3)
Object Storage gives each hosting account S3-compatible buckets on the server itself: media offload for WordPress, downloads, application assets, or a target for your own tooling. It needs the MinIO component, installed with --object-storage (rerun the installer with that flag on an existing server).
How do I create a bucket?
Object Storage → New bucket. Pick a name (lowercase letters, digits, dashes); the bucket is created as <account>-<name>, so names never clash between accounts. Optional: a quota in MB (a hard limit enforced by the storage server) and public downloads, which lets anyone read objects by URL while uploads still need a key.
How do I connect an application?
Create an access key (label it after the application). The secret is shown once, together with the endpoint and ready-made rclone settings. Every key of an account can read and write all of that account's buckets and nothing else.
| Setting | Value |
|---|---|
| Endpoint | https://<panel hostname>:9000 (the panel certificate) |
| Region | us-east-1 |
| Addressing | Path-style (https://host:9000/<bucket>/<key>) |
Works with the AWS CLI, rclone, s3cmd, WordPress offload plugins, Laravel's S3 driver and anything else that speaks S3. An example with the AWS CLI:
bash
aws --endpoint-url https://srv1.example.com:9000 s3 ls s3://johndoe-media/What happens on suspension or deletion?
Suspending an account disables its access keys; unsuspending enables them again. Deleting an account deletes its buckets, objects and keys. Resellers see and manage the buckets of their customers.
Where is the data?
Under /var/lib/aiopanel/objects on the server (the aio-minio service, user minio). Include it in your server backups; the panel's own backups do not copy object storage.