Skip to content
BloberThe Safest, Easiest Way to Move Cloud Files
Articles
On this page

Enterprise and On-Premises S3-Compatible Storage Systems

· 5 min read · Updated

Add as preferred source
Copy page
View as MarkdownOpen in ChatGPTOpen in Claude
Enterprise and on-premises S3-compatible storage systems

Many enterprise storage platforms expose an S3-compatible endpoint inside the data center. Media companies, banks, research labs, and government keep petabytes on them, and because they all speak S3, standard tools can read and write to them.

Enterprise systems are one section of our complete list of S3-compatible storage providers. Every one of them connects to Blober through the generic S3-Compatible provider: point it at the system's S3 endpoint (often a data VIP or load-balanced address inside your network) and enter your keys. Most on-premises systems prefer path-style addressing, and the endpoint setup notes explain how it differs from virtual-hosted. The endpoint notes follow each vendor's documentation, checked against rclone's S3 docs[1].

NetApp StorageGRID

NetApp StorageGRID is a widely deployed enterprise object store with a mature S3 implementation, used for backup targets, archives, and data lakes. It supports S3 features like versioning, object lock, and lifecycle, which makes it a strong compliance and ransomware-recovery target[2].

  • Endpoint format: your StorageGRID gateway or load-balancer address (your own deployment).
  • Addressing: both styles are supported; path-style is common on-prem.

NetApp ONTAP S3

NetApp ONTAP, the operating system behind FAS and AFF arrays and Cloud Volumes ONTAP, includes an S3 object server. Since ONTAP 9.8 you can enable an ONTAP S3 object storage server in an ONTAP cluster and manage it with System Manager or the ONTAP CLI[3].

  • Endpoint format: the S3 server address you configure on the ONTAP system.
  • Addressing: path-style is the safe default.

Dell ECS and ObjectScale

Dell ECS (Elastic Cloud Storage) and its containerized successor ObjectScale are enterprise object platforms with a full S3 API. They are designed for multi-site, geo-distributed deployments with active-active access[4].

  • Endpoint format: your ECS or ObjectScale data node or load-balancer address.
  • Addressing: both styles; path-style is common on-prem.

Cloudian HyperStore

Cloudian HyperStore is an S3-native enterprise object store sold as software or as an appliance. Cloudian markets very high S3 API compatibility, including object lock for immutability[5].

  • Endpoint format: your HyperStore S3 endpoint (data VIP or load balancer).
  • Addressing: both styles supported.

Pure Storage FlashBlade

Pure Storage FlashBlade is a high-performance, all-flash platform with an S3-compatible object store. Recent Purity releases support ListObjectsV2, multipart with AWS-compatible ETags, versioning, and advanced checksums[6].

  • Endpoint format: https://<s3-data-vip> (the FlashBlade S3 data VIP).
  • Addressing: path-style works everywhere; virtual-hosted needs DNS so that bucket.<endpoint> resolves to the data VIP.

Hitachi Content Platform (HCP)

Hitachi Content Platform is an enterprise object store for long-term retention and compliance, with an S3-compatible API. HCP supports namespace access through REST, the Hitachi API for Amazon S3, WebDAV, CIFS, and NFS, and its S3-compatible API calls namespaces buckets[7].

  • Endpoint format: https://<your-hcp-host>.
  • Addressing: path-style is the safe default.

Spectra Logic BlackPearl

Spectra Logic BlackPearl is an on-premises S3-compatible gateway that tiers data to disk, tape, and public clouds under one namespace. It is popular for media archives and backup where tape economics matter[8].

  • Endpoint format: https://<your-blackpearl-host>.
  • Addressing: path-style.

Scality RING and ARTESCA

Scality RING is a petabyte-scale software-defined object store, and ARTESCA is its lighter, cloud-native sibling. Both expose S3. Scality also maintains the open-source Zenko CloudServer[9].

  • Endpoint format: your RING or ARTESCA S3 endpoint, usually a load balancer address.
  • Addressing: both styles supported.

Quantum ActiveScale

Quantum ActiveScale (formerly Western Digital ActiveScale) is an enterprise object system tuned for large-capacity archives and cold data. It is often paired with tape for very long-term retention[10].

  • Endpoint format: your ActiveScale S3 endpoint (load-balanced address).
  • Addressing: path-style is common.

DataCore Swarm (formerly Caringo Swarm)

DataCore Swarm is an object storage platform with an S3-compatible gateway. It is used for archives and content repositories and focuses on long-term data protection and large media libraries[11].

  • Endpoint format: your Swarm S3 gateway address.
  • Addressing: path-style is common.

Nutanix Objects

Nutanix Objects is the S3-compatible object service in the Nutanix hyperconverged platform, and it adds object storage to existing Nutanix clusters[12].

  • Endpoint format: the Objects store endpoint you configure in Prism.
  • Addressing: both styles supported.

VAST Data

VAST Data is an all-flash, scale-out platform that exposes S3 alongside file protocols, aimed at high-throughput analytics and AI pipelines[13].

  • Endpoint format: your VAST S3 endpoint (virtual IP or load balancer).
  • Addressing: path-style is the safe default.

WekaFS (Weka)

Weka is a high-performance data platform with an S3 protocol front end over its parallel file system, built for GPU and HPC workloads that also need object access[14].

  • Endpoint format: your Weka S3 endpoint (cluster address).
  • Addressing: path-style is common.

Zadara

Zadara is fully managed, enterprise-grade S3-compatible storage with on-prem, hybrid, and cloud deployment options. Get the endpoint and region from the Zadara Object Storage management interface[15].

  • Endpoint format: https://<vsa-id>.zadarazios.com (for example https://vsa-00000001-public-zadara-cloud-01.zadarazios.com).
  • Addressing: virtual-hosted, with us-east-1 as the default region.

IBM Cloud Object Storage and MinIO on premises

Two systems span cloud and on-premises use. IBM Cloud Object Storage (covered on the cloud providers page) is also sold as on-premises software descended from Cleversafe. MinIO (covered on the self-hosted page) runs in many enterprises as a production object tier. Blober connects to both the same way, with the generic S3-Compatible provider pointed at the endpoint.

Frequently asked questions

Can Blober connect to an on-premises storage array? Yes, if the array exposes an S3 endpoint your computer can reach. Enter the system's data VIP or load-balanced address with your keys, and if browsing fails, put the address in Path-style endpoint URL instead.

Do enterprise systems support S3 object lock and versioning? Many do, including StorageGRID, Cloudian, and Dell ECS, which is why they are used as immutable backup and compliance targets. Confirm the specific features with your vendor.

Why do these prefer path-style addressing? Virtual-hosted addressing needs DNS so that every bucket.<endpoint> name resolves to the storage. On-prem systems often skip that setup, so path-style (bucket in the URL path) is the reliable default.

Can I move data from an on-prem array to the cloud? Yes. Blober reads from your on-prem S3 endpoint and writes to a cloud S3 endpoint that supports the normal object operations it uses, or to a non-S3 target like Azure Blob. The files stream through your computer, so no full copy is staged on your disk.