STORE
Object Storage
S3-compatible object storage for data, media, logs, and application assets.
Use buckets as an origin in Applications, automate uploads with Functions, and keep your data strategy portable across tools and providers.
_
egress fees between Azion services
_
availability with distributed architecture
_
S3-compatible—use your existing tools
Usage-based pricing with predictable costs
Pay per GB stored per month and scale with actual usage—no fixed infrastructure commitments.
Keep storage costs predictable as your datasets, media libraries, and backups grow.
High availability on a distributed architecture
Build resilience for applications and data with a distributed architecture designed to reduce downtime and keep object access fast and reliable.
No lock-in with an S3-compatible API
Integrate with existing tools, SDKs, and pipelines using an S3-compatible API.
Maintain control and portability without being tied to a single provider.
S3-compatible object storage, unified on a single platform.
Migrate from S3 providers using the tools you already run
Move objects from existing S3 providers without rewriting your application. Object Storage exposes an S3-compatible API so your current clients and scripts can keep working.
Create a bucket, generate credentials, and point your S3 tooling to Azion's endpoint.
After migration, simplify delivery and processing on one platform
Once your data is in Object Storage, connect it directly to Applications and Functions and avoid egress fees between Azion services.
Use a bucket as an origin for static websites, downloads, and asset libraries, while Functions handle ingest steps like validation, metadata enrichment, and file transformations.
This reduces glue code and external pipelines: storage, delivery, and request-time logic work together on a distributed infrastructure, with one data repository shared across teams.
Object Storage use cases
Frequently Asked Questions
What is Object Storage?
Object Storage is a scalable storage service for unstructured data that integrates with Azion using the S3 standard. It stores data in buckets and lets you upload, download, list, and delete objects.
What is a bucket in Object Storage?
A bucket is a top-level container used to organize objects. Buckets can also be used as an origin for Applications, including static site delivery.
What is an object key and can it be changed?
An object key is the unique identifier used to retrieve an object inside a bucket. The key can’t be changed; uploading a new object using the same key replaces the existing object.
How do prefixes work if buckets don’t have folders?
Prefixes simulate folder hierarchy by using slashes in object keys. This helps you organize content (for example, src/assets/images/...) and control how content is served when using a bucket as an origin.
How can I access Object Storage using the S3 protocol?
Create an S3 credential for a bucket to obtain an access key and secret key, then configure your S3-compatible tools to use Azion’s Object Storage endpoint. Permissions are controlled by the capabilities set on the credential.
Which operations are supported via API and via S3 compatibility?
Object Storage supports core operations for buckets and objects such as create, list, update permissions, upload, download, copy, and delete. For large objects and transfers, S3-compatible multipart upload operations are also supported.
What are the default limits for Object Storage?
Default limits include up to 100 buckets per account and a default ListObjects limit of up to 1,000 objects per request. Limits can be increased depending on your plan.
Can I use Object Storage as an origin for Applications?
Yes. You can configure a bucket as an origin for Applications and choose whether to serve content from the bucket root or a specific prefix, which is useful for static sites and asset hosting.
Can I access Object Storage from Functions?
Yes. Functions can interact with Object Storage through the Storage API, allowing you to read, write, delete, and list objects programmatically.
How do I safely manage read-write access?
Buckets can be configured with different access permissions. If you enable read-write access, ensure you control who can write objects—often by mediating writes through Functions where you can enforce authentication and validation.