> For clean Markdown of any page, append .md to the page URL. > For a complete documentation index, see https://docs.meetstream.ai/llms.txt. > For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.meetstream.ai/_mcp/server. # MeetStream Guide: Alibaba Cloud OSS Custom Object Storage By default, MeetStream stores bot media—audio, video, transcripts, screenshots, chat logs, and meeting manifests—in a MeetStream-managed bucket. Fetch endpoints return presigned download URLs for those files. Custom object storage lets you send those artifacts directly to your own storage account while keeping the same MeetStream bot and fetch APIs. Use the `alibaba_oss` provider for Alibaba Cloud Object Storage Service (OSS), through its S3-compatible API. Authenticate with an Alibaba Cloud RAM AccessKey pair. Only one S3-compatible custom provider is active at a time. Saving a new `aws` or `alibaba_oss` configuration activates it and deactivates the other one. Artifacts written before the change remain pinned to their original provider, bucket, and prefix. Custom storage is useful for compliance, regional data storage, lifecycle control, or direct ingestion into your data platform. --- ## 1) Prerequisites All providers require: 1. A bucket owned by your organization. 2. Credentials that can write to the prefix you configure. 3. A MeetStream API key. For `read_write` access, the credentials also need to read uploaded objects so MeetStream can generate download URLs and retrieve JSON artifacts. 1. Create an OSS bucket in the target OSS region. 2. Create a RAM user or RAM role with an AccessKey pair. RAM identities have no OSS access until you attach a RAM or bucket policy. 3. Use the OSS region ID in `region` (for example, `us-east-1` or `ap-southeast-1`). MeetStream uses OSS's S3-compatible API with virtual-hosted bucket addressing. For OSS buckets in Chinese mainland regions, new OSS users may need a HTTPS custom domain (CNAME) rather than the default public endpoint; see Alibaba's [AWS SDK compatibility guidance](https://www.alibabacloud.com/help/en/oss/developer-reference/use-aws-sdks-to-access-oss). --- ## 2) Configure custom storage ```http PUT /api/v1/admin/configs?config_type=storage Authorization: Token Content-Type: application/json ``` ```json { "provider": "alibaba_oss", "bucket_name": "your-oss-bucket", "region": "us-east-1", "access_key_id": "LTAI...", "secret_key": "...", "access_mode": "read_write", "prefix": "meetstream", "prefixes": { "audio": "meetstream/audio", "video": "meetstream/video", "transcript": "meetstream/transcripts", "metadata": "meetstream/metadata" } } ``` `endpoint_url` is optional for Alibaba OSS. If omitted, MeetStream uses: ```text https://s3.oss-.aliyuncs.com ``` For example, the default endpoint for `region: "us-east-1"` is `https://s3.oss-us-east-1.aliyuncs.com`. Set `endpoint_url` only when you must use an approved HTTPS custom domain or another compatible endpoint. ### Parameters | Parameter | Required | Description | |---|---:|---| | `provider` | Yes | `"alibaba_oss"`. | | `bucket_name` | Yes | Name of your OSS bucket. | | `region` | Yes | OSS region ID. | | `access_key_id` | Yes | Alibaba Cloud RAM AccessKey ID. | | `secret_key` | Yes | Alibaba Cloud RAM AccessKey secret. | | `access_mode` | No | `"read_write"` (default) or `"write_only"`. See [Access modes](#4-access-modes). | | `prefix` | No | Base object-key prefix. Defaults to `"meetstream"`. Leading/trailing slashes are removed and `..` is rejected. | | `prefixes` | No | Per-category overrides for `audio`, `video`, `transcript`, and `metadata`. A missing category inherits `prefix`. | | `endpoint_url` | No | HTTPS endpoint override. Omit it to use the S3-compatible regional default. | Secrets are stored as encrypted parameters and are never returned by the API. --- ## 3) Grant bucket permissions Scope policies to the configured prefix. If you use distinct category prefixes, include one object resource for each distinct prefix. For a `read_write` configuration using the `meetstream` prefix: ```json { "Version": "1", "Statement": [ { "Effect": "Allow", "Action": [ "oss:PutObject", "oss:GetObject", "oss:DeleteObject" ], "Resource": "acs:oss:*:*:your-oss-bucket/meetstream/*" } ] } ``` For `write_only`, remove `oss:GetObject`; keep `oss:PutObject` and `oss:DeleteObject`. MeetStream does not require `oss:ListObjects` to upload or fetch a known object. You may still need it when browsing the bucket through the OSS console or CLI. Alibaba documents the distinction between bucket-level listing and object-level access in its [RAM policy guide](https://www.alibabacloud.com/help/en/oss/user-guide/access-control-base-on-ram-policy). --- ## 4) Access modes | Mode | MeetStream uploads to your bucket | MeetStream fetch APIs | |---|---|---| | `read_write` (default) | Yes | Return presigned URLs or read JSON artifacts from your bucket | | `write_only` | Yes | Return `403`; retrieve objects directly through your own storage access | Use `write_only` when you want MeetStream to deliver files to your bucket but do not want it to read them back. ### Configuration validation MeetStream validates credentials before saving them: - `alibaba_oss` first attempts the compatible `HeadBucket` request. If a RAM policy intentionally omits bucket-level access, MeetStream instead verifies the required object operations with a temporary object under each configured prefix. - `write_only` configurations use temporary write probes under each distinct effective prefix. Successful probes are cleaned up. Grant `oss:DeleteObject` to prevent a failed cleanup from leaving a probe object behind. --- ## 5) File layout in your bucket MeetStream writes every artifact below the resolved prefix for its category, followed by the bot ID: ```text // ``` With the default `prefix: "meetstream"` and no per-category overrides: ```text meetstream/ abc123/ audio.wav meeting_recording.mp4 manifest.json participants.json chats.json screenshot/ transcription/ ``` With the OSS example configuration above: ```text meetstream/audio/abc123/ audio.wav audio_manifest.json audio_participants/.wav meetstream/video/abc123/ meeting_recording.mp4 video_manifest.json participants/.mp4 meetstream/metadata/abc123/ manifest.json participants.json chats.json screenshot/ meetstream/transcripts/abc123/ transcription///processed_transcript.json ``` The exact provider, bucket, and category prefix used for each processed artifact are recorded with the bot or transcript. Updating a storage configuration later does not break retrieval of existing media. --- ## 6) Fetch media after configuration Your MeetStream API calls do not change when custom storage is enabled. With `read_write`, the API returns a presigned URL generated by the configured provider. OSS URLs use the configured S3-compatible OSS endpoint. | Endpoint | `read_write` | `write_only` | |---|---|---| | `GET /api/v1/bots/{bot_id}/get_audio` | Presigned mixed-audio URL | `403` | | `GET /api/v1/bots/{bot_id}/get_video` | Presigned recording URL | `403` | | `GET /api/v1/bots/{bot_id}/get_audio_streams` | Per-participant audio URLs, when requested for the bot | `403` | | `GET /api/v1/bots/{bot_id}/get_recording_streams` | Per-participant video URLs, when requested for the bot | `403` | | Screenshot, chat, participant, manifest, and transcript fetch endpoints | Read from the configured bucket | `403` | Presigned media URLs expire after one hour. Call the fetch endpoint again to obtain a fresh URL. --- ## 7) View, change, or delete configuration ### View ```http GET /api/v1/admin/configs Authorization: Token ``` The response includes non-sensitive metadata under `StorageConfig`, for example: ```json { "StorageConfig": { "alibaba_oss": { "active": true, "bucket_name": "your-oss-bucket", "region": "us-east-1", "endpoint_url": "https://s3.oss-us-east-1.aliyuncs.com", "access_mode": "read_write", "prefix": "meetstream", "prefixes": { "audio": "meetstream/audio", "video": "meetstream/video", "transcript": "meetstream/transcripts", "metadata": "meetstream/metadata" } } } } ``` ### Delete ```http DELETE /api/v1/admin/configs?key_name=alibaba_oss Authorization: Token ``` Deleting a configuration affects only future processing; MeetStream does not delete objects already written to your bucket. --- ## 8) Troubleshooting **Saving an OSS configuration returns `400`** - Confirm `region` is the OSS region ID for the bucket. - Omit `endpoint_url` to use the default `https://s3.oss-.aliyuncs.com`, or supply a valid HTTPS custom endpoint. - Confirm the RAM AccessKey belongs to an identity with `oss:PutObject`, and also `oss:GetObject` for `read_write`. - For Chinese mainland buckets, ensure your required OSS custom-domain/CNAME setup is complete. **OSS `HeadBucket` is denied** This can be expected for a prefix-scoped RAM policy. In `read_write` mode, MeetStream falls back to an object write/read probe. Ensure the policy grants the object-level actions shown in [Grant bucket permissions](#3-grant-bucket-permissions). **A fetch endpoint returns `403` with `"access_mode": "write_only"`** The configured provider is intentionally write-only. Download the object through your own storage workflow, or update it to `read_write` with read permissions. **A presigned URL returns `403`** - It may have expired; fetch a new one from MeetStream. - Verify the configured credentials still have object read access. - For OSS, verify the configured endpoint and region match the bucket. **Files are not in the newly configured bucket** Only artifacts processed after a configuration change use the new active provider. Existing artifacts remain in their original bucket. --- ## 9) Provider references - [Alibaba Cloud: Access OSS with AWS SDKs](https://www.alibabacloud.com/help/en/oss/developer-reference/use-aws-sdks-to-access-oss) - [Alibaba Cloud: S3 API compatibility](https://www.alibabacloud.com/help/en/oss/developer-reference/compatibility-with-amazon-s3) - [Alibaba Cloud: RAM policies for OSS prefixes](https://www.alibabacloud.com/help/en/oss/user-guide/access-control-base-on-ram-policy)