An independent home for application files.
Photos, documents and generated files should live independently of application containers.
What matters for your application
Profile photos and application media
Validate file sizes and types on the backend.
Private document uploads
Separate public and private objects; an unpredictable key is not authorization.
Reports and export files generated by workers
Plan retention, deletion and transfer costs.
Where it fits
Photos, documents and generated files should live independently of application containers. Object storage manages files by object keys as a separate service.
- Profile photos and application media
- Private document uploads
- Reports and export files generated by workers
Its place in your application
The backend authorizes uploads and records ownership. Clients never receive permanent bucket access keys. Downloads of private objects are authorized per request or through time-limited access.
Before you begin
Choose services around the actual needs of your application. Include these points in your development and release plan.
- Validate file sizes and types on the backend.
- Separate public and private objects; an unpredictable key is not authorization.
- Plan retention, deletion and transfer costs.
Common questions
Can I create an S3-compatible bucket now?
Not yet. No object storage provider is connected and bucket / credential creation is disabled. This page describes the planned usage model.
Can I provision a live resource now?
Not yet. New registration and customer allocation are closed on the live site. Product guides are published; local development simulation does not create real services.