Skip to content

Users

Object Storage Client Setup

See API Access — Object Storage for details on setting up your S3-compatible client.

Understanding Object Storage Users

Object Storage Users are distinct from IAM users and serve as the primary identity for accessing the Object Storage service. The following hierarchy shows how they fit in:

Hierarchy Overview

  • IAM Project: The top-level entity that contains resources, including Object Storage Users.
  • Object Storage User: A unique identity for accessing Object Storage, associated with a specific IAM project. Each user owns one or more buckets.
  • Bucket: A container for objects, owned by a single Object Storage User. See the Buckets documentation for details.
  • Credentials: Each Object Storage User can have one or more sets of access and secret keys for authentication. Each credential acts as the user, allowing flexible access management.

Managing Access and Bucket Policies

Create separate Object Storage Users within a project to isolate access between buckets. Bucket policies become relevant when you grant access between Object Storage Users. This approach provides fine-grained control over access to buckets and objects within the Object Storage service.

Key Concepts

  • Object Storage User: A unique identity for accessing Object Storage, associated with a specific IAM project.
  • Credentials: Each Object Storage User can have one or more sets of access and secret keys for authentication.
  • Regions: we offer two regions for Object Storage:
  • HAM1 (Hamburg): https://objectstorage-replicated.ham1.cloud.syseleven.net
  • DUS2 (Düsseldorf): https://objectstorage-replicated.dus2.cloud.syseleven.net

Security & Multi-tenancy

Keep your Object Storage credentials secure and never share them publicly. Using separate Object Storage Users lets you partition buckets — either within a single IAM project or across projects — to maintain strong security and multi-tenancy.