Huawei Cloud OBS
Use the Huawei Cloud OBS connector to index approved files from Object Storage Service. Create one connector per knowledge directory and restrict the IAM policy to the bucket and object prefix that AIvis should read.
What You Need
OBS endpoints are regional. Bucket domain names use BucketName.Endpoint, for example bucketname.obs.ap-southeast-1.myhuaweicloud.com. AIvis needs the regional endpoint and bucket name separately, not the full bucket domain.
Prepare Huawei Cloud
- Sign in to Huawei Cloud and open IAM.
- Create an IAM user dedicated to AIvis, such as
aivis-obs-reader. - Create an AK/SK for programmatic access and store the secret securely.
- Open the OBS bucket and confirm its region ID.
- Upload approved files under a dedicated prefix, for example
knowledge/. - Attach a custom OBS policy with only list and read permissions for that scope.
Minimum IAM Policy
For classic IAM policy syntax, use obs:bucket:ListBucket and obs:object:GetObject. New identity-policy environments may use lower-case action names such as obs:bucket:listBucket and obs:object:getObject; match the syntax required by your Huawei Cloud IAM edition.
Do not grant upload, delete, bucket policy management, or broad obs:*:* permissions. If your bucket uses KMS or another encryption dependency, validate decrypt permissions with the same IAM user before production indexing.
Credential Fields
Create a Huawei Cloud OBS credential in AIvis:
Connector Fields
The connector uses S3-compatible signed requests with virtual-hosted addressing. If using intranet, Direct Connect, dual-stack, or a custom endpoint, test reachability from the AIvis worker network before creating a broad connector.
Verify
- Confirm the credential validates.
- Create a connector for a small prefix, such as
knowledge/test/. - Run one index attempt and confirm only objects under the configured prefix appear.
- Search for a known sentence from an uploaded document.
- Confirm unselected prefixes and sensitive files are absent.
- Test as an unauthorized AIvis user and confirm private connector content is not searchable.