Deployment and Client Configuration
When an object vault is deployed to an IBM Cloud Object Storage Accesser®appliance, it is automatically made available through each of the REST APIs in the Dispersed Storage Object API Family.
See the Manager Administration Guide for more information on deploying an Object Vault.
Clients can always access the SOH API via the following URL scheme (new in version 2.5):
http://{accesser-ip}/soh/{vault-name}/{object-id}Where:
| URL Part | Description |
|---|---|
| {accesser-ip} | The IP address or host name of the Accesser appliance. The actual address can differ for client applications if a proxy or load balancer is being used. |
| soh | The literal that indicates the SOH API. |
| {vault-name} | The vault name that is being accessed. When omitted, a list of vaults is returned. |
| {object-id} | The identifier of the object that was written, and is specified for operations on existing objects. It is omitted when new objects are written. |
If the SOH API is configured as the Default API for an Accesser appliance, clients can also access the API via the following URL scheme:
http://{accesser-ip}/{vault-name}/{object-name}In ClevOS 2.8.0, the default API is initially set to SOH API. When ClevOS is upgraded, existing client applications that support the SOH API do not need to be modified unless an administrator changes the default API on a given Accesser appliance.
Access through HTTPS is also supported.