Deployment and client configuration
When an object vault is deployed to an Accesser node, it is automatically made available through each of the other supported REST APIs (Swift, SOH).
Clients can always access the CSO API via the following URL scheme:
[source,http] ---- http://{accesser-ip}/s3/{vault-name}/{object-name} ---- | Parameter | Explanation |
|---|---|
| accesser-ip | The IP address or hostname of the Accesser node. The actual address might differ for client applications if a proxy or load balancer is being used. |
| s3 | The literal that indicates the CSO API. |
| vault-name | The vault name that is being accessed. A vault is synonymous with a bucket in the S3 API. |
| object-name | The full object name that is being accessed. It is omitted for bucket operations such as listing. |
If the CSO API is configured as the default API for an Accesser node, clients can also access the
API via the following URL scheme:
[source,http] ---- http://{accesser-ip}/{vault-name}/{object-name} ---- Access through HTTPS is recommended, as some operations are supported only through HTTPS.
Note: See the Vaults section of the Manager Administration Guide for more information
on deploying an object vault and about SSL and PKI access through an Accesser node.
If an S3 Virtual Host Suffix is configured
for an Accesser node, clients can also access the API via the following URL
scheme:
[source,http] ---- http://{bucket-name}.{s3-virtual-host-suffix}/{object-name} ---- Note: See the 'Create Access Pool' section and the 'Edit Access Pool' section of the Manager
Administration Guide for more information on configuring virtual host-style access through an
Accesser node.