> CDS > Hedvig S3 Protocol-Compatible Object Storage User Guide > Hedvig Object Storage Configuration > Hedvig Configuration File (config.xml)

S3 <s3> Element

Here is a list of the properties in the <s3> element in the Hedvig Configuration File (config.xml):

  • <metaclients> – the number of S3 Service threads that process requests other than IO (all other lightweight requests) within each S3 Service.

    Note

    Contact Commvault for help with setting this value.

  • <readclients> – the number of S3 Service threads that process Read IO requests (read/download object) within each S3 Service.

    Note

    Contact Commvault for help with setting this value.

  • <writeclients> – the number of S3 Service threads that process Write IO requests (create object) within each S3 Service.

    Note

    Contact Commvault for help with setting this value.

  • <port> [default: 16000] – the port on which a Hedvig S3 Storage Proxy listens for incoming S3 Service client requests.

  • <certfile> and <keyfile> – the paths to the certification and key files, which are necessary only if <https> is set to true. Otherwise, these elements are not required.

  • <rsakeyfile> – the path to the RSA private key file for decryption on the Hedvig Storage Proxy, which must be the same file that is present on the Hedvig Storage Cluster Nodes under /usr/local/hedvig/pages/privateKey.

    Important

    To start an S3 Service on a Hedvig Storage Proxy, you must copy the RSA private key file to /var/log/hedvig/privateKey and set the restrictions.

  • <https> [values: true, false] – enables or disables an HTTPS-supported S3 Service.

  • <virtualhostingenabled> [values: true, false] – By default, the S3 proxy recognizes all requests only as path-style access. To use S3 with virtual-hosted style access, enable this by adding the tag and setting it to true

  • <hostendpoints> – If <virtualhostingenabled> is set to true, and if the Hedvig Storage Cluster setup uses a load balancer with the Hedvig Storage Proxies, then the load balancer hostname endpoints must be included in the storage proxy configuration file. This information identifies path-style versus virtual-hosted style requests made through the load balancer and extracts the bucket name from the host header for virtual-hosted style requests. Use comma-separated load balancer fully qualified hostnames, such as nginxvm1.hedviginc.com,nginxvm2.hedviginc.com

Loading...