Considerations for the HS3 API

These considerations apply to the HS3 API:

You can enable the HS3 protocol for a namespace only while ACLs are enabled for the namespace. For information on enabling ACLs, see Enabling the use of ACLs.

For users and applications to be able to perform any operations with the HS3 API, the HCP management API must be enabled for the tenant. For information on enabling the management API, see Controlling access to HCP through the management API.

For a user or application to be able to create and manage namespaces with the HS3 API, the applicable user or group account must have the allow namespace management property enabled. For information on the allow namespace management property, see Managing accounts.

This additional consideration applies when you enable the HS3 API for a namespace that was created in an HCP release earlier than 6.0.

After being upgraded from a release earlier than 6.0, HCP generates ETags for objects that were stored before the upgrade. HCP generally does this over time. However, in response to an HS3 request to retrieve an object that does not yet have an ETag, HCP immediately generates the ETag before returning the object. This can be time consuming for large objects, with the result that HCP may be slow to respond to the first GET request for such an object. If you are concerned about this issue, please contact your HCP system administrator before enabling HS3 for the namespace.

Note: An ETag is an identifier for the content of the object. As of release 6.0, HCP generates ETags for objects at the time they are stored.

Trademark and LegalDisclaimer

© 2015 Hitachi Data Systems Corporation. All rights reserved.