Storage security & limits
Access and credentials
Dashboard project permissions control bucket, asset, media, and key management. An S3 access key is a separate data-plane credential. Create one key per workload, give it read or readwrite permission, and use bucketScope to limit it to one bucket when possible. The secret is shown only at creation. Revoke an unused or exposed key in the project workspace or with the CLI:
hubfly storage keys create reports-reader --read-only --bucket reports --to reporting-app
hubfly storage keys
hubfly storage keys revoke <accessKey>--to writes the key into a Cell project's environment as secret variables, so the secret never appears in your terminal.
Keep S3 keys on trusted servers. A browser should use a short-lived upload or download URL that your server requests through the Dashboard API. Browsers can PUT to an upload session's upload_url from any origin; the S3 endpoint itself rejects cross-origin preflight requests, so presigned S3 PUTs do not work from a browser. Protected asset share and playback URLs are also temporary bearer capabilities.
Quota and size limits
| Limit | Current behavior |
|---|---|
| Project quota | A new tenant uses the region’s configured default, currently 100,000,000,000 bytes unless provisioned differently. The project usage response is authoritative. |
| Object listing | At most 1,000 objects per S3 page; follow continuation tokens for more. |
| Media session upload | 20 GB maximum source with a declared content length. |
| Image transforms | At most 100 distinct variants for one image per UTC day; output at most 16 million pixels. |
Current object bytes, staged multipart parts, and generated image or media objects use storage capacity. Read project usage, or run hubfly storage usage, before large uploads. Clean up incomplete multipart uploads and unneeded generated variants.
Protect sensitive data
Encrypt sensitive object bodies before upload
Public assets can be read by anyone with their URL. Choose protected access for private content and use short-lived shares. Deleting an asset also deletes its source object, renditions and image variants, and breaks every link to it. Rotating an asset's access key may invalidate links already embedded in an application.
Troubleshoot requests
| Symptom | Check |
|---|---|
| Signature or access error | Endpoint, signing region, system clock, SigV4 payload, key status, permission, and bucket scope. |
| Object not found | Project region, exact bucket and case-sensitive key, and versioning/delete markers. |
| Quota exceeded | Project usage, generated variants, old versions, and staged multipart parts. |
| Unsupported S3 call | Compare the request to the supported S3 operations; unsupported calls return an XML NotImplemented error. |
| Video playback fails | Source upload complete, job ready, playback token unexpired, and manifest URL from the latest response. |