Buckets
Create buckets in the project, with the name, provider, location, and visibility you choose.
Object Storage
Object storage through familiar S3 APIs.
Create public or private buckets, manage access, and use familiar S3 APIs. With the S3 provider you choose.
Access
S3 stays S3.
You work with familiar S3 APIs and SDKs. You decide whether a bucket is public or private. You create access keys in Loopback, and with the S3 provider you choose the location of your data.
S3 APIs
Familiar APIs, SDKs, and tools work without changes.
Visibility
You decide for each bucket whether it is public or private.
Access keys
Create, view, and revoke access keys.
Provider
You choose the S3 provider and with it the location of your data.
From project to object.
You create buckets in the project, manage access, and work with familiar S3 APIs.
01
Project
Object Storage belongs to the project. You manage buckets, visibility, and keys in one place.
02
Bucket
You set name, provider, location, and visibility, public or private.
03
Access
Create, view, and revoke access keys.
04
Use
Objects through the file browser or familiar S3 APIs and SDKs.
What you can do
Buckets, files, and keys in the project.
File browser
Create folders, upload files, and delete objects.
Access keys
Create, view, and revoke access keys.
Buckets in the project.
Organization, project, and bucket build on each other. Your buckets live in the project, right next to your clusters.
Organization
Account, teams, and roles. The frame for every resource.
Project
Shared context for clusters, storage, and billing.
Bucket
Name, provider, location, visibility, file browser, and access keys.
The facts.
| API | S3-compatible |
|---|---|
| Visibility | Public or private, per bucket |
| Access keys | Create, view, and revoke |
| Location | At the location of the S3 provider you choose |
| Billing | Per GB and month, traffic separate |
| SLA | 99.5% availability |
Keep working in the same project.
You reach Object Storage from the cluster and store files in the same project.
Object Storage at a per-gigabyte price.
0.05€ per GB per month, billed hourly. You pay for what sits in the buckets.
Object Storage
0.05€ / GB
per GB per month, billed hourly Based on 720 hours
- S3-compatible
- Public and private buckets
- Access keys
- File browser
- Same project as the cluster
FAQ
Is Object Storage S3-compatible?
Yes. You can use familiar S3 APIs and SDKs.
Can buckets be public and private?
Yes. You decide for each bucket whether it is public or private.
Where is Object Storage stored?
At the location of the S3 provider you choose.
How are permissions managed?
Through the Loopback account and project. You can create, view, and revoke access keys.
Which SDKs and tools can I use?
Familiar S3 APIs and SDKs.
How is Object Storage billed?
You pay per stored GB. Traffic is billed separately by usage.
Is Object Storage the same as persistent cluster storage?
Object Storage is the S3 service in the project. Persistent volumes live in the Kubernetes workspace.