How to Use Tencent Cloud COS to Sync an infolio Knowledge Base
A setup checklist for using Tencent Cloud COS as an infolio custom sync source: bucket, APPID, region, endpoint, SecretId, SecretKey, permissions, and recovery testing.
Quick answer
Tencent Cloud COS fits users who already manage object storage in Tencent Cloud. For infolio, the critical fields are the full bucket identity, region, endpoint, SecretId, SecretKey, and scoped permissions.
Steps
Create a dedicated COS bucket for infolio
Create a separate COS bucket for infolio. COS bucket names commonly include both BucketName and APPID, so record the complete bucket identifier shown in the console.
- Record the full bucket name and APPID.
- Record the bucket region.
- Do not mix infolio sync data with website assets, logs, or backups.
Confirm endpoint and region
Tencent COS endpoints are region-specific. When using S3-compatible access, configure an endpoint that matches the bucket region, such as a cos.{region}.myqcloud.com style endpoint.
- Confirm the endpoint from the COS console or official docs.
- Keep region aligned with the bucket location.
- Use an internet-reachable endpoint for cross-device sync.
Prepare SecretId and SecretKey
Prepare a dedicated Tencent Cloud access key for infolio. COS permanent keys consist of a SecretId and SecretKey. Temporary credentials can be more secure for short-lived access, but long-running sync typically needs stable credentials.
- Do not reuse a high-permission root key.
- Scope the credential to the infolio bucket.
- Store SecretKey safely, not in ordinary documents.
Configure COS sync in infolio
Enter the bucket, region, endpoint, SecretId, and SecretKey in infolio sync settings. Test with a small knowledge base before moving important material.
- Check keys and access policy if you see 403 errors.
- Check endpoint and region if connection fails.
- Confirm the bucket policy allows the required reads and writes.
Verify recovery and record maintenance details
Connect another device to the same COS sync source and confirm documents, workspaces, whiteboards, and vaults recover. Keep region, bucket, and key rotation notes in a safe place.
- Confirm a new device can recover the knowledge base.
- Record credential creation and rotation dates.
- Review COS storage and request usage periodically.
Related pages
FAQ
Why does a COS bucket name include APPID?
Tencent Cloud COS identifies buckets with account-specific information. Use the complete bucket details shown in the console and official docs when configuring sync.
Does COS sync mean infolio is self-hosted?
No. COS is only a custom sync storage layer. infolio remains a local-first app, not a web service you deploy yourself.