< Previous | Contents | Next >

Using SSL security

When you create a bucket or list the buckets you own, HCP does not require the use of SSL security with the HS3 request; that is, you can start the URL in the request with either HTTP or HTTPS. Whether the use of SSL security with other HS3 requests is required, optional, or not supported depends on the configuration of the HS3 API for the target bucket.


By default, the use of SSL security is optional for requests for operations other than creating a bucket or listing the buckets you own. You cannot use HS3 to change this configuration. However, tenant administrators can use other HCP interfaces to reconfigure the HS3 API to require or not support the use of SSL security.


Using an IP address in a URL

Normally, you let HCP choose the node on which to process an HS3 API request. You can, however, use an IP address in the request URL to access the system on a specific node. To do this, you replace the fully qualified hostname in the URL with the IP address of an HCP node.


When you use an IP address in a URL, you also need to specify the fully qualified hostname in an HTTP Host request header.


Here’s an example of an s3curl command that uses a URL with an IP address and a Host header that identifies the finance bucket:


./s3curl --id=lgreen --put=Q4_2012.ppt -- -k

-H "Host:finance.europe.hcp.example.com" "https://192.168.210.16/quarterly_rpts/Q4_2012.ppt"


Chapter 3: Access and authentication 45

URLs for access to HCP


Here’s a command that does the same thing as the command above but uses the format in which the bucket name follows the URL:


./s3curl --id=lgreen --put=Q4_2012.ppt -- -k

-H "Host:europe.hcp.example.com" "https://192.168.210.16/finance/quarterly_rpts/Q4_2012.ppt"


For information on HCP nodes, see “HCP nodes” on page 3. For information on when to use an IP address instead of a hostname, see “Hostname and IP address considerations” on page 192.


For the IP addresses of the HCP nodes, contact your tenant administrator.