A storage record is the reusable destination for files and recordings. Test credentials with a small object first; a saved form does not prove bucket access.
開始之前
A bucket created in the intended region.
Credentials limited to the required bucket and object operations.
A retention and lifecycle policy owned by your organization.
設定說明
只說明操作員需要的控制項;內部欄位名稱與實作事件不會顯示。
Connection
Identify the external object store.
- Storage name
A clear operator label such as Archive EU or VOD Primary.
- Storage type
Choose the S3-compatible or Backblaze connection expected by the bucket.
- Bucket or endpoint
The bucket address used by this storage connection.
- Access key
Credential identifier permitted to access the bucket.
- Secret key
Write-only secret paired with the access key.
Never place it in screenshots or support messages.
Optional metadata
External metadata storage for workflows that require it.
- Metadata database URL
Optional Redis-compatible URL used by supported metadata workflows.
Leave it empty unless the workflow explicitly requires it.
安全的首次工作流程
- 01
Create a storage record with an operator-friendly name and the correct provider type.
- 02
Enter the bucket endpoint and least-privilege credentials.
- 03
Save the storage, then copy a small non-sensitive test file into it from File manager.
- 04
Confirm the object exists in the bucket and can be read through the expected workflow.
工作流程範例
Send live recordings to external retention
Local disk should not own the only copy of a live program.
驗證結果
- A test copy reaches the intended bucket and can be read back.
- The storage list identifies the correct provider and operator label.
- Failed credentials do not expose their secret value in the UI.
疑難排解
A storage saves but copy fails
檢查- Check bucket endpoint and region.
- Verify object write permission and credential validity.
Correct the bucket policy or credentials and repeat with the same small test file.