HS3 is an HTTP-based API. This means that you use URLs to identify tenants, buckets, and objects. Every HS3 request for access to HCP must include the URL for the service point, bucket, or object that’s the target of the request.
With every HS3 request, you also need to either provide credentials for the user account you’re using or request anonymous access. If HCP determines that credentials you provide correspond to a valid user account and that the user account has the applicable permissions for the requested operation, you become an authenticated user.
HCP supports two methods of user authentication for HS3: Amazon Web Services™ (AWS™) and HCP. With AWS authentication, HCP follows the Amazon S3 method of authenticating users. With HCP authentication, HCP uses its own standard method. If you’re using HS3 to develop S3-compatible applications, you should use AWS authentication.
This chapter describes the URLs you can use in HS3 requests when using AWS authentication. It also explains how to provide credentials or request anonymous access with that authentication method.
For information on HCP authentication and the URLs you can use with that authentication method, see Alternative authentication method.
![]() |
Note: •All the examples of HS3 requests in this book assume AWS authentication. •To use a recognized Active Directory user account for access to HCP through the HS3 API, applications must use the SPNEGO protocol or the AD authentication header to negotiate the AD user authentication themselves. For more information on SPNEGO, see http://tools.ietf.org/html/rfc4559. For more information on the AD authentication header, see .Active Directory authentication header |
© 2016 Hitachi Data Systems Corporation. All rights reserved.