How to Use Google Cloud Storage to Sync an infolio Knowledge Base
A setup checklist for using Google Cloud Storage as an infolio custom sync source: bucket, project, location, HMAC key, endpoint, permissions, and recovery testing.
Quick answer
Google Cloud Storage fits users who already manage storage in Google Cloud. If infolio asks for S3-compatible fields, prepare Cloud Storage HMAC keys and the matching endpoint; if it asks for native GCS fields, follow the product UI.
Steps
Create a dedicated Cloud Storage bucket
Create a separate bucket for infolio inside your Google Cloud project. Choose a location and storage strategy you can maintain over time.
- Record the project, bucket, and location.
- Do not mix sync data with public website assets.
- Confirm billing and ownership are clear.
Identify the access method infolio requires
Cloud Storage supports HMAC keys for authenticating XML API requests, which is useful for S3-compatible tooling. Use the fields shown in infolio: prepare HMAC keys if it asks for access-key style credentials, or native fields if the UI asks for native GCS configuration.
- Check the exact fields shown in infolio settings.
- Prepare HMAC keys when S3-compatible fields are required.
- Do not store service account secrets or HMAC secrets in plain notes.
Use a least-privilege credential
Google documents HMAC keys for Cloud Storage XML API authentication. Prefer a dedicated, scoped identity instead of a broad personal account credential.
- Restrict access to the infolio bucket.
- Record key purpose and creation date.
- Review and disable unused HMAC keys regularly.
Fill in the GCS sync source in infolio
Enter the bucket, endpoint, HMAC access ID, secret, or other GCS fields requested by infolio. Test upload, download, and recovery with a small knowledge base first.
- Check HMAC key state if authentication fails.
- Check bucket IAM if permission fails.
- Confirm the relevant Cloud Storage endpoint is reachable.
Verify recovery and ongoing maintenance
Connect another device to the same GCS sync source and confirm knowledge-base recovery. Over time, review bucket cost, lifecycle rules, and credential rotation.
- Confirm documents, whiteboards, workspaces, and vaults recover.
- Record key rotation steps.
- Review Cloud Storage usage and cost periodically.
Related pages
FAQ
Does GCS always require HMAC keys for infolio?
Not always. It depends on the current infolio configuration fields. If the app asks for S3-compatible access-key fields, HMAC keys are usually the GCS equivalent; if it asks for native fields, follow the native setup.
Should I keep a personal-account HMAC key long term?
Prefer a scoped, dedicated identity and review, rotate, or disable keys that are no longer needed.