What Is S3-Compatible Backup Storage?

By Mark Austen, Solutions Architect

Learn what S3-compatible backup storage is, how it works, and why teams use it for scalable, flexible cloud backup.

In summary

S3-compatible backup storage is object storage that works with the same API structure as Amazon S3, allowing backup tools and applications to store data in a familiar format outside AWS. It gives organizations more flexibility over where backup data lives, how it is accessed, and how costs are managed. S3-compatible storage is commonly used for scalable, offsite, and cloud-ready backup strategies.

A backup is only useful if the data is still there when something goes wrong — and if it can be restored quickly enough to matter. As backup volumes grow, teams need more capacity without losing control of recovery performance or cost.

S3-compatible backup storage gives teams another way to handle that pressure. It uses the familiar Amazon Simple Storage Service (Amazon S3) API model without requiring backup data to live in Amazon S3 itself.

What is S3-compatible backup storage?

S3-compatible backup storage is object storage that supports the API conventions used by Amazon S3. Backup applications can write data to it using familiar S3 operations and bucket structures, along with the same authentication model.

Object storage keeps data as objects rather than arranging it in a conventional file hierarchy or dividing it into fixed blocks. Each object contains the data and descriptive metadata, with a unique key used to retrieve it from a bucket. This approach makes object storage well suited to large, expanding backup repositories. For more background, see our Guide to Cloud Storage.

The important word is compatible. An S3-compatible service follows enough of the Amazon S3 API for supported applications to communicate with it. That does not mean every provider implements every Amazon S3 feature in exactly the same way.

How does S3-compatible storage work?

S3-compatible storage gives a backup application a standard way to create, find, write, and retrieve objects. In a typical backup workflow:

1. The backup platform authenticates using an access key and secret key.
2. It connects to the storage provider’s S3 endpoint and selects a bucket.
3. It writes backup data as objects, often using multipart uploads for large files.
4. When recovery is needed, the platform requests the relevant objects and reconstructs the backup set.

The provider supplies the storage infrastructure, while the S3 API acts as the common language between that infrastructure and the backup tool. Moving to another S3-compatible target may involve changing the endpoint and credentials rather than redesigning the entire backup workflow.

Some services also support S3 features such as versioning, lifecycle policies, replication, and object lock. Support varies, so teams should check the exact operations their backup software requires before selecting a provider.

Is S3-compatible storage the same as Amazon S3?

No. Amazon S3 is an AWS storage service, while S3-compatible storage is a broader category of object storage that implements the S3 API, either fully or in part.

The distinction matters because API familiarity does not make the services identical. Providers can differ in storage location and the path traffic takes to reach it. Feature support and commercial terms can also vary considerably.

Basic actions such as creating buckets or uploading objects may behave consistently across providers. More specialized capabilities, including retention controls or identity integrations, may not. Before committing to a service, confirm that the provider supports the specific API calls and settings used by the backup platform.

Why use S3-compatible cloud backup?

Organizations use S3-compatible cloud backup to gain more choice without giving up the tooling built around the S3 ecosystem. The main benefits include:

• Wider provider choice: Teams can compare service models across storage locations, including the commercial terms, instead of treating one cloud as the default destination.
• Existing tool support: Many enterprise backup platforms already work with S3-compatible targets, reducing the need for custom integrations.
• Capacity that can grow: Object storage can expand as backup volumes increase without requiring teams to purchase and manage another storage array.
• More control over costs: Alternative providers may use different models for capacity, data retrieval, API operations, or egress, giving teams room to match spending to the way backups are used.

S3 compatibility can reduce technical friction, but it does not make every migration automatic. Teams still need to consider data transfer time and application certification. Provider-specific settings may also need to change.

What are common use cases for S3-compatible backup storage?

S3-compatible backup storage fits workloads that need large amounts of durable, offsite capacity. Common use cases include:

• Secondary backup copies: Keeping a copy away from the primary environment reduces dependence on the same infrastructure during an outage.
• Immutable backup repositories: When the service supports object lock, backup data can be protected from modification or deletion for a defined retention period.
• Long-term retention: Object storage can hold older backup sets or compliance records without consuming primary storage capacity.
• Hybrid and multicloud recovery: A shared API model can help backup tools protect workloads across data centers and cloud environments.

It can also serve Managed Service Providers that operate backup services for several customers. A common API simplifies integration, while separate buckets and access policies can help keep customer data logically isolated.

What should you look for in S3-compatible backup storage?

Start with recoverability, not capacity alone. A low storage price has limited value if the service does not support the backup platform or cannot return data within the required recovery window.

Evaluate the following areas:

• API and application compatibility: Confirm which S3 operations are supported and whether the backup vendor has certified the target.
• Recovery performance: Check expected throughput and latency against the organization’s recovery time objective. Look for any restore throttling that could slow a large recovery.
• Availability and durability: Review how the provider protects data across hardware failures and what its service-level commitments cover.
• Retention controls: Look for versioning and object lock, then confirm that policies prevent unauthorized early deletion. These features must also be configured correctly.
• Access protection: Assess encryption, identity controls, credential management, and audit logging. Cloud storage security still depends on how the service is configured and operated.
• Cost predictability: Model capacity charges alongside retrieval, egress, API request, and early deletion fees.
• Data location: Make sure available regions support latency needs and applicable data sovereignty or compliance requirements.
• Connectivity: Consider how backup and restore traffic will reach the storage, particularly when large recovery jobs could saturate an internet connection.

Finally, test a real restore. Compatibility tables and performance estimates are useful, but a recovery exercise shows whether the complete path works under the conditions that matter.

How does S3-compatible storage support backup and disaster recovery?

S3-compatible storage provides an offsite destination for backup data and a consistent interface for retrieving it during recovery. Its elastic capacity can accommodate changing backup volumes, while features such as versioning and object lock can limit the damage caused by accidental deletion or ransomware.

That makes it a useful component of a disaster recovery plan, but not the entire plan. Recovery point objectives determine how much data the organization can afford to lose. Recovery time objectives define how quickly systems need to return. Backup frequency and retention settings should be designed around those targets. The available restore bandwidth must support them, too.

The network path matters more during recovery than it may during routine backups. Incremental backup jobs can trickle data into storage over time; a major restore may need to pull terabytes back at once. Dedicated connectivity can provide more predictable throughput than the public internet, helping teams estimate whether a recovery window is realistic.

How Megaport Storage provides S3-compatible backup storage

Megaport Standard Object Storage is S3-compatible object storage designed for enterprise backup and disaster recovery, including large-volume data retention. It works with existing S3-compatible backup tools, so teams can add a storage target without rebuilding their surrounding workflow.

Connected directly to the Megaport Network, Megaport Storage supports throughput up to 100 Gbps and includes object lock for immutable backups, as well as no egress fees and no storage capacity limits — helping teams plan for growing repositories and large restores without treating data retrieval as an exception.

Review our Megaport Object Storage documentation for info on the connection model and supported Megaport services.

Backup storage should make recovery easier without making the wider infrastructure harder to change. S3 compatibility preserves tool choice. From there, capacity and retention can be designed around actual recovery needs, with a network path fast enough to bring the data back.

Need an S3-compatible backup target that works with the tools you already use?