Skip to content
Product Tour

A workflow-level tour of ScaleStore.

ScaleStore adds provider, customer, and operator workflows around Ceph RGW without becoming the object-data path.

The flow

From provider onboarding to day-two operations.

Connect the provider, define the service, onboard customers, manage access and usage, then operate the service.

1

Connect infrastructure

Install and enroll the Provider Bridge, verify readiness, and establish the provider-side control boundary.

2

Define the service

Configure the object-storage service, plans, boundaries, product settings, and operating model.

3

Onboard customers

Expose the customer-facing workflows needed to create and manage storage access.

4

Manage access

Work with access keys, temporary credentials, revocation, and support around storage access.

5

Support and prove

Use diagnostics, monitoring and recovery checks to operate and troubleshoot the service.

Step 1 — Connect your infrastructure

Provider onboarding installs and enrolls the Provider Bridge, verifies connectivity and establishes the provider-side control boundary.

Step 2 — Define your storage service

Once connected, the provider configures the object-storage service they want to expose: service presentation, commercial boundaries, enabled workflows, and operating assumptions.

Step 3 — Onboard customers

Customers need a clear path to storage access, buckets, credentials and usage. Providers need the same workflows to be supportable without dropping into Ceph administration for routine tasks.

Step 4 — Manage credentials

Access keys, temporary credentials, rotation and revocation are handled as normal service workflows, with enough context for support when access fails.

Step 5 — Work with buckets and usage

Customers keep using normal S3 clients against RGW. ScaleStore handles the surrounding bucket workflows, quota state and usage visibility needed by customers and providers.

Step 6 — Operate and prove

Day-two operations cover provider and Bridge health, troubleshooting, governance, release checks and recovery. These are available to operators without turning routine support into a manual cluster investigation.