IBM Cloud Object Storage

Edit online

You can configure IBM Cloud® Object Storage.

Before you begin

Ensure that you have HMAC credentials that are created in the IBM Cloud Object Storage. To create a set of HMAC credentials by using the console mode or CLI mode, follow the instructions in HMAC credentials section of the IBM Cloud documentation.
Tip: The HMAC credentials can be found in the cos_hmac_keys field, which consist of an access key and a secret key paired.

Procedure

Follow the instructions below:
  1. Storage Type – Select IBM Cloud Object Storage from the drop-down list.
  2. Bucket name – Enter the bucket name that you wish to access.
    Note: The entered name must match an existing bucket. If no bucket is available, refer to Creating a bucket to create one.
  3. Access key ID – Enter the corresponding access key ID to access the specified bucket. You can get the access key ID from your IBM® Cloud Object Storage account.
  4. Secret access key – Enter the corresponding secret key ID to access the specified bucket. You can get the secret access key from your IBM Cloud Object Storage account.
  5. Endpoint – Enter the URL used to connect to the place where you want to store the data. For more details about endpoint, refer to Endpoints and storage locations.
    Note: The URL must begin with “http://” or “https://”.
  6. Extended parameters – Enter the following extended parameters in Extended parameters settings if necessary. If you have multiple parameters to enter, press Enter on your keyboard to separate the parameters. Refer to the instructions below to add parameters.
    • Allow_Insecure_SSL – By default, the storage client expects an SSL certificate issued by a public trusted certificate authority over HTTPS transport to ensure integrity. A self-signed certificate on the storage server side will fail the certificate validation. If you choose to use a self-signed certificate, you can set the Allow_Insecure_SSL to true in the Extended parameters to bypass the certificate validation.
    • SignatureVersion – By default, IBM Storage Protect for Cloud Microsoft™ 365 uses V2 authentication to access your storage. If you want to use V4 authentication, add SignatureVersion=V4 into the extended parameters.
      Note: IBM Cloud Object Storage can be accessed by using both V2 and V4 authentication. For more details, refer to Configure authentication against a system.
    • RetryInterval – Customize the retry interval when the network connection is interrupted. Enter any positive integer between 0 and 2147483646 (the unit is millisecond). For example, RetryInterval=30000 means that it will try to reconnect every 30000 milliseconds.

      If you do not configure this parameter, the value is 30000 milliseconds by default.

    • RetryCount – Customize the reconnection times after the network connection is interrupted. Enter any positive integer between 0 and 9. For example, RetryCount=9 represents when the network connection is interrupted, it can reconnect at most 9 times.

      If you do not configure this parameter, the value is 6 by default.

    • CustomizedMetadata – Configure if customized metadata or user-added metadata is supported. By default, customized metadata and user-added metadata are all supported.
    • CustomizedMode=Close – This physical device will not support customized metadata or user-added metadata.
    • CustomizedMode=SupportAll – This physical device will support all customized metadata and user-added metadata.
    • CustomizedMode=CustomizedOnly – This physical device will only support user-added metadata.
    • Cert_thumbprint - If you have a self-signed certificate for S3 server and only want to pass the certificate validation with a specific thumbprint, enter your thumbprint as the value of the parameter.
    • Cert_thumbprint – If you have a self-signed certificate for S3 server and only want to pass the certificate validation with a specific thumbprint, enter your thumbprint as the value of the parameter.
    • Virtualhosting – By default, it is set to false. If your bucket does not support using path-style domain names, you need to configure virtualhosting = true to use virtual-hosted-style domain names.