Search the docs

About This Documentation

Hammerspace is a sophisticated, highly flexible software-defined data platform. It has many capabilities that can be configured to meet a wide range of use-case requirements. These include the ability to act as an object storage target for clients using the S3 protocol.

This S3 support is native, meaning S3 is truly an equal peer with the other client protocols, NFS and SMB. No gateway, shim, cache, or translation layer is required. S3 services are also architected to support multitenancy, meaning that a single Hammerspace implementation can provide object storage services to multiple user populations that are separate from - and unaware of - each other.

This solution guide focuses on the multitenant capabilities of Hammerspace’s S3 object storage services. After reviewing the architecture and various tenant isolation techniques, several step-by-step configuration examples are provided.

Although the screenshots shown represent the v5.2 GUI, this guide applies to Hammerspace versions 5.1 and later.

For support resources, see the Hammerspace Support Hub and the Hammerspace Licensing and Delivery Portal.

Do not install additional or third-party software, agents, or packages directly on Hammerspace Anvil (metadata) or DSX (data) nodes. These nodes run a managed appliance software stack; anything installed outside that stack is unsupported and is removed during a software upgrade. Such software can also interfere with node operation. If you need monitoring or integration with an external tool, contact Hammerspace Support for a supported approach.