Block storage
Block StorageCloud disks separate from the server: your data stays in place when the server is replaced or deleted
Object Storage in Dorsa Cloud stores photos, videos, documents, large files and backups. Your application can access it directly.
| files | Size |
|---|---|
| images/hero.webp | 480 KB |
| videos/intro.mp4 | 24.6 MB |
| docs/catalog.pdf | 3.1 MB |
| images/logo.svg | 12 KB |
DC7K••••Q2MFA separate key for every applicationObject Storage does not depend on a server. Applications use access keys to write and read files.
Your application, script or S3-compatible tool uploads a file using an access key.
The file is retained in your project's storage, and the panel shows used capacity.
Your server, website or application reads the file with the same key. Files remain in place if you replace the server.
Both keep data separate from servers, but they serve different purposes.
| Object storageObject Storage | Block storageBlock Storage | |
|---|---|---|
| What it stores | Complete files such as photos, videos, documents, backups and logs | Data accessed directly by a server's operating system, such as database files |
| How you use it | Access keys and S3-compatible tools or libraries | Attaches to a server like a disk and appears within the operating system |
| Who can access it | Any application with a key; create separate keys for separate applications | Only the server currently attached to the disk |
| Server dependency | Not attached to a server; files remain when the server is replaced | Created separately but must be attached to a server for use |
| Who it is for | Numerous large files, archives and backups | Databases, application files and data continuously read and written by a server |
Choose Cloud Disk when a server needs an additional data disk. About Cloud Disk
Store server and application backups separately from the server. Managed database backups can also be kept in your project's Object Storage.
Store product photos, user uploads and videos without filling your server disk.
Keep images, fonts and built website assets together for your application or deployment workflow to read.
Send web server and application logs to storage, keeping server disks clear and logs available when needed.
Files are not uploaded through the panel; your application or tool accesses storage directly using access keys.
Choose a storage name. Review service status and usage in the panel later.
The panel shows your access key, secret key and service endpoint. The secret is visible only once; keep it safe.
Enter these three values into an S3-compatible tool or library. The first command lists your storage.
With separate application keys, delete an unneeded key without affecting the others.
export AWS_ACCESS_KEY_ID=<ACCESS_KEY>
export AWS_SECRET_ACCESS_KEY=<SECRET_KEY>
# list your bucket
aws s3 ls --endpoint-url <ENDPOINT>
# upload a file
aws s3 cp ./backup.tar.gz s3://<BUCKET>/backups/ \
--endpoint-url <ENDPOINT>The main capabilities of Object storage at a glance.
Create a separate, named space for each application or department.
Specify which access key each application uses to reach your files.
Review service status and used capacity in your project.
Services commonly used alongside Object storage.
Cloud disks separate from the server: your data stays in place when the server is replaced or deleted
Back up your data so you can restore it after an error
Manage domains, DNS records, traffic routing and HTTPS settings in one place
Large files quickly fill server disks and tie business growth to one server's capacity.
Object storage supports use cases such as Application and website files, Document and data archives, Photos and videos. The right choice depends on your project's technical and operational requirements.
Read the product guide and estimate costs in the calculator, then create the service in your chosen project in the client panel.
Register, estimate costs before provisioning and pay hourly for the time you use the service.