Provisioning object storage space

Object storage space is provisioned via S3 buckets created in the S3 cluster.

Limitations

  • Only one S3 cluster can be created on top of the storage cluster.
  • All components of the S3 cluster should run on multiple nodes for high availability. Name server and object server components in the S3 cluster are automatically balanced and migrated between S3 nodes. S3 gateways are not automatically migrated; their high availability is based on load balancing.

    We recommend using an external load balancer to balance traffic between S3 nodes with gateways. The external load balancer must support session persistence (also called sticky sessions) based on the source IP address and SSL certificate management.

    DNS load balancing can be used for test purposes only. For production, use an external load balancer.

Prerequisites

Provisioning overview

  1. Create the S3 cluster.
  2. To manage S3 resources in the self-service panel, enable S3 access for the self service, log in there at http://<admin_panel_IP_address>:8800 as a self-service user, and then proceed to create S3 buckets, as described in Managing S3 resources in the Self-Service Guide.
  3. To manage S3 resources in the legacy user panel or by using a third-party application (such as Cyberduck and Mountain Duck), add S3 users, and then proceed to create S3 buckets, as described in Accessing S3 buckets in the Storage User’s Guide.