/// CONNECT A PROVIDER / HITACHI CONTENT PLATFORM
Hitachi Content Platform
Hitachi Content Platform (HCP) exposes an S3-compatible API — HS3 — over your tenant. Point storafleet at your tenant's HS3 data domain with credentials an admin issues for you.
What you need
- An Access Key and Secret Key derived from your HCP user (see below).
- Your tenant HS3 / data domain URL, e.g.
https://<tenant>.hcp.<domain>— not the admin console. - The region — HCP ignores it, so use
us-east-1.
Get your credentials
- In the tenant console, go to Security → Users and Generate Authorization Token for your user.
- The console gives you the two values to use as your access key and secret key.
- (HCP for Cloud Scale instead issues a normal random access/secret pair.)
With classic HCP auth the credentials are derived, not random: your Access Key = Base64(username) and your Secret Key = MD5(password). Generate them under Security → Users → Generate Authorization Token in the tenant console.
Endpoint & region
Your endpoint is your tenant's HS3 data domain, e.g. https://<tenant>.hcp.<domain> — use the data domain, not the admin console. In HCP, namespaces are buckets and each is a subdomain, so it needs wildcard DNS. The region is ignored, so use us-east-1.
Connect the Fleet
- From the Fleet page, click Create Fleet and pick Access Keys.
- Paste the Access Key and Secret Key for your HCP user.
- Set your endpoint to your tenant HS3 data domain (e.g.
https://<tenant>.hcp.<domain>) and set the region tous-east-1. - HCP uses virtual-hosted-style addressing (each namespace is a subdomain), so it needs wildcard DNS. If your tenant uses a private-CA or self-signed HTTPS certificate, provide a CA bundle so storafleet can verify the connection.
Supported features
HCP supports versioning and Object Lock — WORM/retention in Compliance mode, with SEC/FINRA/Cohasset-validated compliance — over HS3.
Lifecycle, tiering, and access are governed by HCP service plans and data-access ACLs, not S3 bucket config.