Storage Policy Backends
What this documentation category covers
These tutorials are organized by backend type: how to prepare the external service, create a storage policy, configure policy group rules, move users or teams over, and verify everything before going live.
AsterDrive has two layers of concepts:
- Storage policy: which storage policy backend files are ultimately written to
- Policy group: which storage policy a user or team upload matches, based on rules
If you only want to understand the overall model, start with Storage Policies.
If you have already decided which backend to connect, use the tutorials here.
Current Tutorials
| Backend | Best for | Tutorial |
|---|---|---|
| Local disk | Single-node setups, NAS, small teams, minimum dependencies | Local disk |
| S3 / MinIO / R2 | Object storage, large files, external buckets, cloud storage | S3 / MinIO / R2 |
| Azure Blob Storage | Azure Storage accounts, Blob containers, Azure-managed object storage | Azure Blob Storage |
| Tencent COS | Tencent object storage, COS CI, per-policy native processing | Tencent COS |
| OneDrive | Microsoft 365, OneDrive, SharePoint / group drives, Microsoft Graph authorization | OneDrive |
| SFTP | SSH/SFTP file servers, NAS, traditional server directories, server-side streaming | SFTP |
| Follower node | The control plane stays on the primary node, while real objects are written to another AsterDrive node | Follower Node Storage Policy |
General Configuration Flow
Do Not Rush Production Traffic
For a new backend, create a separate policy first. Do not directly modify an old policy that is already in use.
Recommended flow:
- Create a new backend policy
- Create a test policy group
- Bind one test user or test team
- Run through upload, download, sharing, deletion, and restore
- After confirming there are no issues, move real users or teams to the new policy group
Do not directly change the real destination for policies that already have files
The local directory, S3 bucket / endpoint / prefix, Azure Blob endpoint / container / base path, OneDrive drive / root item / site or group identifiers, SFTP endpoint / base path, and follower node binding determine where old files are located. If you change them directly, old files may no longer be found.