The Provider Bridge keeps provider ownership intact. It handles approved control actions and provider-side integration while customer object traffic continues to flow directly to provider RGW.
The bridge initiates outbound connectivity. ScaleStore does not need broad inbound administrative exposure into provider infrastructure.
The bridge is part of the control plane. It applies approved operations and reports health. It is not the customer object-data path.
Each provider runs its own bridge against its own infrastructure, domains, and RGW environment. There is no shared cross-provider bridge.
The bridge lets ScaleStore coordinate provider workflows without taking over the provider's storage path or requiring ScaleStore Cloud to become the direct operator of provider infrastructure.
Defines provider state, product configuration, approved actions, and support workflows.
Receives approved operations, integrates with provider-side systems, and reports health and diagnostics.
Customers keep talking to provider-owned S3 endpoints. Their object traffic does not get proxied through ScaleStore Cloud.
The Provider Bridge is a controlled provider-side component. It sits between ScaleStore Cloud and provider-owned systems so the platform can coordinate provider workflows without centralizing storage traffic.
In practical terms, the bridge is the architectural answer to a simple requirement: providers should stay providers.
The Bridge executes a defined set of provider-side actions. It is scoped to one provider, connects outbound, records what it does and does not become a general administrative tunnel into the environment.
