Use Aliyun OSS to Sync infolio: Object Storage for a Local-First Knowledge Base
Learn how Aliyun OSS can work as an infolio custom sync source for documents, whiteboards, private vaults, and multi-device knowledge workflows.
Best for
- Users with an existing Alibaba Cloud account and OSS bucket.
- People who want the storage layer in a cloud account they control.
- Personal knowledge bases that need configurable sync.
Setup notes
- Prepare a dedicated bucket or prefix for infolio.
- Use credentials with a narrow permission scope.
- Record the region, endpoint, bucket, and access policy for future devices.
Privacy boundary
- Do not store access keys in regular notes.
- Put sensitive accounts and IDs in encrypted vaults.
- Object storage sync does not replace backup and permission hygiene.
OSS is for people who want storage control
Some users do not want every sync path to depend on an app vendor cloud. Aliyun OSS is useful when you already understand buckets, credentials, regions, and cloud billing.
Using OSS does not turn infolio into a cloud-only app. Your docs, whiteboards, and vaults still work locally; OSS moves changes between devices.
Keep infolio sync data isolated
A dedicated bucket or prefix makes it easier to reason about permissions, storage usage, and troubleshooting. Avoid mixing sync data with website assets, logs, or unrelated backups.
If you often set up new devices, keep recovery notes in a safe place. Credentials themselves should go into a vault, not a normal document.
- Dedicated storage reduces accidental deletion risk.
- Narrow credentials are easier to audit.
- Costs and capacity are easier to attribute.
Separate sync configuration from private records
Cloud configuration is infrastructure information. Passwords, API keys, IDs, and contracts are sensitive records. infolio encrypted vaults are the better place for the latter.
That separation lets OSS handle sync while vaults protect records that should not sit in ordinary pages.
FAQ
Does infolio support Aliyun OSS as a sync source?
Yes. Aliyun OSS is listed on the site as a supported custom sync source for people who want to bring their own object storage.
Is OSS sync a good fit for non-technical users?
Official cloud or iCloud is simpler if you do not want to manage buckets, access keys, and policies. OSS is better for users comfortable with cloud storage.