'%20transform='translate(102%20102)%20scale(.8)'/%3e%3c/svg%3e){kind=small}
VOS Object Storage
Choose how files are accessed
Distinguish file management, temporary sharing, access domains and S3 permissions, then verify each access path.
Uploaded does not mean publicly accessible
Open the target bucket under Object storage VOS → Buckets. Files visible in management use your sign-in permissions; they are not necessarily public. Share through file-sharing links or configured access domains. Never give visitors an S3 Secret.
Choose the right entry point
| Use case | Entry point | What matters |
|---|---|---|
| Administrator download check | File list → Download | Verify the current file and downloaded content |
| Time-limited external sharing | File list → Temporary share | Set an expiry and generate a new link when it expires |
| Long-term references in an application | Bucket → Access domains | DNS, HTTPS, permissions and complete resource paths |
| Manage files with tools or code | Object storage VOS → S3 access | Use bucket-scoped credentials; never put secrets in public links |
Create a share link or configure a domain
- Locate the file in the target bucket and confirm its folder and name. For temporary sharing, open the file's sharing action, set an expiry and generate a link.
- For a business domain, open Access domains in the bucket and select the appropriate configuration. Custom domains require DNS management permissions.
- Complete ownership verification and DNS records listed in the domain task, then check CDN and HTTPS task status. Receiving a CNAME alone does not prove file availability.
- Use the complete generated temporary-share URL. For private domains, obtain an address through the appropriate authorization flow and preserve its signature and expiry parameters; do not simply append a file path to the domain. For public files, use the verified full resource URL.
- Test in a new window and compare content. For private files, also verify that access is denied without a session, signature or authorization.
Essential verification
Receiving a CNAME or creating a domain does not mean the whole access path is ready. Check ownership, DNS, certificates and actual file responses, and compare downloaded content.
After a temporary link expires, generate a new one with the required permissions. Do not use expiring share links as permanent resource URLs.
Where to check failed access
| Issue | Check |
|---|---|
| 403 | File permissions, signatures or temporary-link expiry |
| 404 | File location in the bucket, URL path and case |
| Certificate warning | Access-domain HTTPS status, certificate coverage and validity |
| Domain does not resolve | Current DNS records, authoritative nameservers and domain-task requirements |
| Configuration shown as incomplete | Open the existing domain task and review the failure; do not replace troubleshooting with duplicate creation |
Access and costs
Domain creation, DNS, certificate deployment and file permissions are separate steps that each need verification. When using CDN, review its usage charges too. Storage capacity is listed separately in Billing center.