Fill the Server: 80% off your first 4 monthly invoices, monthly billing. Ends Nov 30, 2026. 25 spots in this batch.FILL25
Fill the Server, annual: about 29.63% off your first annual invoice. Ends Nov 30, 2026.FILL25Y
Fill the Server, 2 year term: about 15.69% off your first biennial invoice. Ends Nov 30, 2026.FILL25B
Fill the Server, 3 year term: about 11.11% off your first triennial invoice. Ends Nov 30, 2026.FILL25T
80% off your first 3 months, monthly billing. Ends Dec 25, 2027.3MONTHS80
50% off your first annual Shared term. Ends Dec 31, 2027.50SHARED
Shared Starter, 3 year term: C$105.84 total.MOOSE294
20% off your first 3 monthly VPS invoices. Ends Dec 31, 2027.20VPS3
25% off your first annual base VPS term.25VPS

← All guides

Object storage

What is S3-compatible object storage?

Published August 2026 · 8 min read

S3-compatible object storage stores data as named objects inside buckets and exposes those objects through an HTTP API. The familiar S3 request model makes many tools portable between providers, but compatibility should be treated as a tested protocol surface. It does not promise that every AWS service exists elsewhere.

Start with buckets, objects and keys

A bucket is a top-level namespace. An object combines bytes with a key and metadata. The key can contain slash characters, so software often presents keys as folders even though the backend is not maintaining a traditional directory tree.

That difference matters when an application expects file locking, random in-place writes or POSIX permissions. Object storage normally replaces an object with a new version of its bytes. It does not behave like a mounted disk.

The endpoint is part of the configuration

An S3 client needs an HTTPS endpoint, a region or signing scope, and credentials. A non-AWS provider usually requires the endpoint to be entered explicitly; leaving the AWS default in place can send requests to the wrong service.

Path-style and virtual-hosted-style requests also affect DNS and TLS. A compatibility test should cover the addressing style the intended client actually uses. One command-line example is not enough proof.

Authentication usually means Signature Version 4

Modern S3 clients sign requests with an access key and secret key. The signature covers request details and prevents a client from simply sending the secret across the network as a password.

The secret still needs the same care as any production credential. Put it in a secret store or protected application configuration, scope its permissions narrowly, and make rotation part of the operating plan.

Compatibility has boundaries

Core bucket and object operations, multipart uploads and presigned URLs are common compatibility targets. AWS-specific services around S3—such as unrelated IAM products, event integrations or proprietary management features—should not be assumed to exist just because basic object operations work.

Before production use, test the exact SDK, backup application or workflow that will depend on the service. Record unsupported operations so later users do not turn an untested assumption into a recovery problem.

Choose object storage for object-shaped workloads

Backups, immutable-style archives, media, application uploads, generated artifacts and static assets often map naturally to objects. A database data directory or a workload that needs block-level updates usually does not.

The protocol can be extremely useful without being universal. Start by describing how the application reads, writes, lists and deletes data, then choose the storage model that matches those operations.

Next step

Understand S3-compatible object storage through buckets, object keys, endpoints, credentials, HTTP operations and the compatibility limits that matter before choosing a service.

Explore DotMoose Object Storage

Keep reading

Related guides.

boto3 S3-compatible storage: custom endpoint, put_object and connection tests

Connect boto3 to S3-compatible storage with endpoint_url. Start with a read-only list, then optionally verify put_object with one isolated write/read/delete round trip.

Read the guide

S3 multipart upload explained: part size, retries, checksums and cleanup

Learn how S3 multipart upload works: numbered parts, AWS part-size limits, parallel retries, completion, checksums and cleanup of abandoned uploads.

Read the guide

S3 presigned URLs explained: temporary access without sharing keys

Learn how S3 presigned URLs authorize a specific operation for a limited time, where they help, what they expose and how to use them safely.

Read the guide

More object storage guides

We will handle the move. You check it first.

Your current site stays online until your new one is ready. You approve the copy first, and if anything is not right we switch you back right away. The price you pick is the price you renew at.

Start my free moveSee plans and prices
See pricesFree move