IBM Storage Protect - S3

Edit online

Follow the instructions below:

Before you begin

The IBM Storage Protect Object client (S3) must be installed and configured before setting up IBM® Storage Protect for Cloud. Refer to, Sending data from other object clients to IBM Storage Protect.

Procedure

  1. Storage type – Select IBM Storage Protect - S3 from the drop-down list.
  2. Bucket name – Enter the bucket name you wish to access.
    Note: The entered name must match an existing bucket. For details on creating a bucket, see How to create an S3 bucket in IBM Storage Protect.
  3. Access key ID – Enter the corresponding access key ID to access the specified bucket.
  4. Secret access key – Enter the corresponding secret key ID to access the specified bucket.
  5. Endpoint – Enter the URL used to connect to the place where you want to store the data.
    Note: The URL must begin with http:// or https://.
  6. Advanced – If you want to configure extended parameters, select the Advanced option. Refer to the instructions below to configure Extended parameters, and note that if you have multiple parameters to enter, use the semicolon (;) to separate the parameters.
    • Use_PathStyle=true – This parameter is required to ensure the IBM Storage Protect for Cloud Google Workspace can work with your storage properly.
    • RetryCount – Customize the reconnection times after the network connection is interrupted. Enter any positive integer from 0 to 2147483646. For example, RetryCount=6 represents when the network connection is interrupted, and it can reconnect at most 6 times.

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

    • RetryMode – Customize the retry mode for the requests not being completed successfully. If this parameter is not configured or configured incorrectly, the Legacy will be applied as the default value. You can also set the value to Standard or Adaptive. Standard represents the standardized request retry strategy which is consistent across all SDKs; Adaptive represents an experimental request retry strategy that builds on the Standard strategy and introduces congestion control through client-side rate limiting.
    • 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.
    • Cert_thumbprint – If you use a self-signed certificate on the storage server side and you want to pass the certificate validation with a specific thumbprint, set the value to the thumbprint string.

      By default, the Cert_thumbprint parameter is not configured.

  7. Click Save to save the custom storage location.