vania-janet/multiturn-rag-retrieval-data huggingface dataset:
: The name of the storage class.

ibm.io/parallel-count
: The maximum number of parallel requests that can be sent to the IBM Cloud Object Storage service instance for a single read or write operation. Storage classes with perf in their name are set up with a maximum of 20 parallel requests. Storage classes without perf are set up with two parallel requests by default.

ibm.io/s3fs-fuse-retry-count
: The maximum number of retries for a read or write operation before the operation is considered unsuccessful. All storage classes are set up with a maximum of five retries.

ibm.io/stat-cache-size
: The maximum number of records that are kept in the IBM Cloud Object Storage metadata cache. Every record can take up to 0.5 kilobytes. All storage classes set the maximum number of records to 100000 by default.

ibm.io/tls-cipher-suite
: The TLS cipher suite that must be used when a connection to IBM Cloud Object Storage is established via the HTTPS endpoint. The value for the cipher suite must follow the [OpenSSL format](https://www.openssl.org/docs/man1.1.1/man1/ciphers.html). If your worker nodes run an Ubuntu operating system, your storage classes are set up to use the AESGCMcipher suite by default. For worker nodes that run a Red Hat operating system, the ecdhe_rsa_aes_128_gcm_sha_256 cipher suite is used by default.

For more information about each storage class, see the [storage class reference](https://cloud.ibm.com/docs/openshift?topic=openshift-storage_cos_reference). If you want to change any of the pre-set values, create your own customized storage class.
5. Decide on a name for your bucket. The name of a bucket must be unique in IBM Cloud Object Storage. You can also choose to automatically create a name for your bucket by the IBM Cloud Object Storage plug-in. To organize data in a bucket, you can create subdirectories.
</AbortIncompleteMultipartUpload>
</Rule>
</LifecycleConfiguration>
Show more





 Using the API and SDKs 

You can programmatically manage lifecycle rules by using the REST API or the IBM COS SDKs.

REST API reference

This implementation of the PUT operation uses the lifecycle query parameter to set lifecycle settings for the bucket. This operation allows for a single lifecycle policy definition for a bucket. The policy is defined as a set of rules consisting of the following parameters: ID, Status, Filter, and Expiration.

Cloud IAM users must have the Writer role to add a lifecycle policy from a bucket.

Classic Infrastructure Users must have Owner permissions on the bucket to add a lifecycle policy from a bucket.



 Header Type Description 

 Content-MD5 String Required: The base64 encoded 128-bit MD5 hash of the payload, which is used as an integrity check to ensure that the payload wasn't altered in transit. 



The body of the request must contain an XML block with the following schema:



 Element Type Children Ancestor Constraint 

 LifecycleConfiguration Container Rule None Limit 1. 
 Rule Container ID, Status, Filter, AbortIncompleteMultipartUpload LifecycleConfiguration Limit 1000. 
 ID String None Rule Must consist of (a-z,A-Z0-9) and the following symbols:!_.*'()- 
 Filter String Prefix Rule Must contain a Prefix element or be self-closed (<Filter />). 
 Prefix String None Filter The rule applies to any objects with keys that match this prefix. 
 AbortIncompleteMultipartUpload Container DaysAfterInitiation Rule Limit 1. 
 DaysAfterInitiation Non-negative integer None AbortIncompleteMultipartUpload Must be a value greater than 0. 



The body of the request must contain an XML block with the schema that is addressed in the table (see Example 1).

<LifecycleConfiguration>
<Rule>
<ID>delete-after-3-days</ID>
<Filter />
<Status>Enabled</Status>
// PUT BUCKET PROTECTION CONFIGURATION
pInput := &s3.PutBucketProtectionConfigurationInput{
Bucket: aws.String("<BUCKET_NAME>"),
ProtectionConfiguration: &s3.ProtectionConfiguration{
DefaultRetention: &s3.BucketProtectionDefaultRetention{
Days: aws.Int64(100),
},
MaximumRetention: &s3.BucketProtectionMaximumRetention{
Days: aws.Int64(1000),
},
MinimumRetention: &s3.BucketProtectionMinimumRetention{
Days: aws.Int64(10),
},
Status: aws.String("Retention"),
},
}
p, e := client.PutBucketProtectionConfiguration(pInput)
fmt.Println(p)
fmt.Println(e) // see response for results

// GET BUCKET PROTECTION CONFIGURATION
gInput := &s3.GetBucketProtectionConfigurationInput{
Bucket: aws.String("<BUCKET_NAME>"),
}
g, e := client.GetBucketProtectionConfiguration(gInput)
fmt.Println(g)
fmt.Println(e)
}

Show more

The typical response is exemplified here.

{
ProtectionConfiguration: {
DefaultRetention: {
Days: 100
},
MaximumRetention: {
Days: 1000
},
MinimumRetention: {
Days: 10
},
Status: "COMPLIANCE"
}
}





 Create a hosted static website 

This operation requires permissions, as only the bucket owner is typically permitted to configure a bucket to host a static website. The parameters determine the default suffix for visitors to the site as well as an optional error document included here to complete the example.

func main() {
Inactive session timeout N/A N/A Set the inactive session timeout to 5 minutes for compliance reasons. 







 Change log for 1.9.10_1527, released 2 October 2018 

The following table shows the changes that are in patch 1.9.10_1527.



Table 1. Changes since version 1.9.10_1523

 Component Previous Current Description 

 IBM Cloud Provider v1.9.10-192 v1.9.10-219 Updated the documentation link in load balancer error messages. 
 IBM Cloud file storage classes N/A N/A Removed mountOptions in the IBM file storage classes to use the default that is provided by the worker node. Removed duplicate reclaimPolicy parameter in the IBM file storage classes. <br>Also, now when you update the cluster master, the default IBM file storage class remains unchanged. 







 Change log for worker node fix pack 1.9.10_1524, released 20 September 2018 

The following table shows the changes that are in the worker node fix pack 1.9.10_1524.



Table 1. Changes since version 1.9.10_1523

 Component Previous Current Description 

 Log rotate N/A N/A Switched to use systemd timers instead of cronjobs to prevent logrotate from failing on worker nodes that are not reloaded or updated within 90 days. Note: In all earlier versions for this minor release, the primary disk fills up after the cron job fails because the logs are not rotated. The cron job fails after the worker node is active for 90 days without being updated or reloaded. If the logs fill up the entire primary disk, the worker node enters a failed state. The worker node can be fixed by using the ibmcloud ks worker reload[command](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_worker_reload) or the ibmcloud ks worker update[command](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_worker_update).
Bronze 2 IOPS/GB 20-12000 Gi 
 Silver 4 IOPS/GB 20-12000 Gi 
 Gold 10 IOPS/GB 20-4000 Gi 



Custom storage class
: When you choose this storage class, you have more control over the size and IOPS that you want. For the size, you can select any whole number of gigabyte within the allowed size range. The size that you choose determines the IOPS range that is available to you. You can choose an IOPS that is a multiple of 100 that is in the specified range. The IOPS that you choose is static and does not scale with the size of the storage. For example, if you choose 40Gi with 100 IOPS, your total IOPS remains 100.
: The IOPS to gigabyte ratio also determines the type of hard disk that is provisioned for you. For example, if you have 500Gi at 100 IOPS, your IOPS to gigabyte ratio is 0.2. Storage with a ratio of less than or equal to 0.3 is provisioned on SATA hard disks. If your ratio is greater than 0.3, then your storage is provisioned on SSD hard disks.



Table of custom storage class size ranges and IOPS

 Size range in gigabytes IOPS range in multiples of 100 

 20-39 Gi 100-1000 IOPS 
 40-79 Gi 100-2000 IOPS 
 80-99 Gi 100-4000 IOPS 
 100-499 Gi 100-6000 IOPS 
 500-999 Gi 100-10000 IOPS 
 1000-1999 Gi 100-20000 IOPS 
 2000-2999 Gi 200-40000 IOPS 
 3000-3999 Gi 200-48000 IOPS 
 4000-7999 Gi 300-48000 IOPS 
 8000-9999 Gi 500-48000 IOPS 
 10000-12000 Gi 1000-48000 IOPS 







 Reclaim policy 

Choose if you want to keep your data after the cluster or the persistent volume claim (PVC) is deleted.



* If you want to keep your data, then choose a retain storage class. When you delete the PVC, only the PVC is deleted.
echo -n (XML block) | openssl dgst -md5 -binary | openssl enc -base64



Example request

PUT /apiary?lifecycle HTTP/1.1
Content-Type: text/plain
Host: s3.us.cloud-object-storage.appdomain.cloud
Authorization: {authorization-string}
Content-Type: text/plain
Content-MD5: M625BaNwd/OytcM7O5gIaQ==
Content-Length: 305

Example request

PUT /apiary?lifecycle HTTP/1.1
Authorization: 'AWS4-HMAC-SHA256 Credential={access-key}/{date}/{region}/s3/aws4_request,SignedHeaders=host;x-amz-date;,Signature={signature}'
x-amz-date: {timestamp}
Content-Type: text/plain
Content-MD5: M625BaNwd/OytcM7O5gIaQ==
Content-Length: 305
Host: s3.us.cloud-object-storage.appdomain.cloud

<LifecycleConfiguration>
<Rule>
<ID>my-archive-policy</ID>
<Filter>
<Prefix/>
</Filter>
<Status>Enabled</Status>
<Transition>
<Days>20</Days>
<StorageClass>GLACIER</StorageClass>
</Transition>
</Rule>
</LifecycleConfiguration>

The server responds with 200 OK.

--------------------

<LifecycleConfiguration>
<Rule>
<ID>{string}</ID>
<Status>Enabled</Status>
<Filter>
<Prefix/>
</Filter>
<Expiration>
<Days>{integer}</Days>
</Expiration>
</Rule>
</LifecycleConfiguration>
[Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) 
 [SSE-C](https://cloud.ibm.com/docs/cloud-object-storage/basics?topic=cloud-object-storage-sdk-aboutsdk-about-sse-c) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) 
 [Archive rules](https://cloud.ibm.com/docs/cloud-object-storage/basics?topic=cloud-object-storage-sdk-aboutsdk-about-archive) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) !
[Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) 
 [SSE-C](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-sdk-aboutsdk-about-sse-c) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) 
 [Archive rules](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-sdk-aboutsdk-about-archive) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) !
[Version 2 object listing](https://cloud.ibm.com/docs/cloud-object-storage/basics?topic=cloud-object-storage-sdk-aboutsdk-about-v2-list) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) 
 [Key Protect](https://cloud.ibm.com/docs/cloud-object-storage/basics?topic=cloud-object-storage-sdk-aboutsdk-about-kp) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) 
 [SSE-C](https://cloud.ibm.com/docs/cloud-object-storage/basics?topic=cloud-object-storage-sdk-aboutsdk-about-sse-c) !
[Version 2 object listing](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-sdk-aboutsdk-about-v2-list) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) 
 [Key Protect](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-sdk-aboutsdk-about-kp) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) 
 [SSE-C](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-sdk-aboutsdk-about-sse-c) !
After provisioning your instance of Object Storage, you will want to learn how to control access using [Identity and Access Management](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-iam). Other options for controlling access are available, and your needs will determine how best to proceed.

While there are many tools for working with IBM Cloud Object Storage developers using one of the supported languages will want to check the [libraries and SDKs](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-sdk-gs) that are available.



 Next Steps 

For more information on how to begin, check out how to [get started](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-getting-started-cloud-object-storage) with IBM Cloud Object Storage.
Access key ID ibm-cos-access-key Secret Your IBM COS HMAC access key ID . false N/A 
 Secret access key ibm-cos-secret-key Secret Your IBM COS HMAC secret access key. false N/A 
 Encryption enabled cluster-encryption Config Set to true if you want to enable cluster-wide encryption. true false 
 IAM API key iam-api-key Secret Your IAM API key. true N/A 
 Perform Cleanup perform-cleanup Config Set to true if you want to perform complete cleanup of ODF on assignment deletion. true false 
 KMS encryption kms-encryption Config Set to true if you want to enable storage class encryption. true false 
 KMS instance name kms-instance-name Config Your KMS instance name. The instance name must only include alphanumeric characters, -, _ or . and start and end with an alphanumeric character. false N/A 
 KMS instance id kms-instance-id Config Your KMS instance id. false N/A 
 KMS instance Base URL kms-base-url Config Your KMS instance public URL to connect to the instance. false N/A 
 KMS instance API key token URL kms-token-url Config API key token URL to generate token for KMS instance. false N/A 
 KMS root key kms-root-key Secret KMS root key of your instance. false N/A 
 KMS IAM API key kms-api-key Secret IAM API key to access the KMS instance. The API key that you provide must have at least Viewer access to the KMS instance. false N/A 
 Ignore Noobaa ignore-noobaa Config Set to true if you do not want to deploy MultiCloud Object Gateway (Noobaa) true false 







 4.11 parameter reference 



Table 3. 4.11 parameter reference

 Display name CLI option Type Description Required? Default value 

 Automatic storage volume discovery auto-discover-devices Config Automatically discover and use the storage volumes on your worker nodes.
In this guide, we will use [HMAC credentials](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-uhc-hmac-credentials-main) similar to the format of AWS credentials.
4. Managing [encryption](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-encryption) provides insights into security. Refer to product documentation on [IBM® Key Protect for IBM Cloud®](https://cloud.ibm.com/docs/key-protect?topic=key-protect-about) and [Hyper Protect Crypto Services](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-overview) for more information.







 Determine your solution 

It is true that a massively complex [migration](https://www.ibm.com/cloud/mass-data-migration) requires a complete service to plan and implement migrating your data to IBM Cloud Object Storage. But whatever the size of your data, your goals and timetable take precedence. Once you have provisioned and set your target, it is time to choose a process to achieve your goals on your time.

There are many ways to achieve the goal of migrating your AWS data. Integrated solutions provide comprehensive guides to migration, as shown in the [IBM Cloud Pak for Integration](https://www.ibm.com/cloud/cloud-pak-for-integration/high-speed-data-transfer). In addition to full-featured migration services, you may also want to investigate third party migration tools as part of your investigation. But don't forget that there are many CLI and GUI tools readily available for use as part of your migration.



* [COS CLI](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-cli-plugin-ic-cos-cli) can be used for many operations. For example, you may wish to use the CLI to configure your IBM Cloud Object Storage instances, and to create and configure buckets.
Access key ID ibm-cos-access-key Secret Your IBM COS HMAC access key ID . false N/A 
 Secret access key ibm-cos-secret-key Secret Your IBM COS HMAC secret access key. false N/A 
 Encryption enabled cluster-encryption Config Set to true if you want to enable cluster-wide encryption. true false 
 IAM API key iam-api-key Secret Your IAM API key. true N/A 
 Perform Cleanup perform-cleanup Config Set to true if you want to perform complete cleanup of ODF on assignment deletion. true false 
 KMS encryption kms-encryption Config Set to true if you want to enable storage class encryption. true false 
 KMS instance name kms-instance-name Config Your KMS instance name. The instance name must only include alphanumeric characters, -, _ or . and start and end with an alphanumeric character. false N/A 
 KMS instance id kms-instance-id Config Your KMS instance id. false N/A 
 KMS instance Base URL kms-base-url Config Your KMS instance public URL to connect to the instance. false N/A 
 KMS instance API key token URL kms-token-url Config API key token URL to generate token for KMS instance. false N/A 
 KMS root key kms-root-key Secret KMS root key of your instance. false N/A 
 KMS IAM API key kms-api-key Secret IAM API key to access the KMS instance. The API key that you provide must have at least Viewer access to the KMS instance. false N/A 
 Ignore Noobaa ignore-noobaa Config Set to true if you do not want to deploy MultiCloud Object Gateway (Noobaa) true false 









 Storage class reference for OpenShift Data Foundation for remote devices 

Review the Satellite storage classes for OpenShift Data Foundation. You can describe storage classes in the command line with the oc describe sc <storage-class-name> command.



Table 4.
IBM COS endpoint ibm-cos-endpoint Config The IBM COS regional public endpoint. false N/A 
 IBM COS location constraint ibm-cos-location Config The location constraint that you want to use when creating your COS bucket. For example: us-east-standard. false N/A 
 Access key ID ibm-cos-access-key Secret Your IBM COS HMAC access key ID . false N/A 
 Secret access key ibm-cos-secret-key Secret Your IBM COS HMAC secret access key. false N/A 
 Encryption enabled cluster-encryption Config Set to true if you want to enable cluster-wide encryption. true false 
 IAM API key iam-api-key Secret Your IAM API key. true N/A 
 Perform Cleanup perform-cleanup Config Set to true if you want to perform complete cleanup of ODF on assignment deletion. true false 
 KMS encryption kms-encryption Config Set to true if you want to enable storage class encryption. true false 
 KMS instance name kms-instance-name Config Your KMS instance name. The instance name must only include alphanumeric characters, -, _ or . and start and end with an alphanumeric character. false N/A 
 KMS instance id kms-instance-id Config Your KMS instance id. false N/A 
 KMS instance Base URL kms-base-url Config Your KMS instance public URL to connect to the instance. false N/A 
 KMS instance API key token URL kms-token-url Config API key token URL to generate token for KMS instance. false N/A 
 KMS root key kms-root-key Secret KMS root key of your instance. false N/A 
 KMS IAM API key kms-api-key Secret IAM API key to access the KMS instance. The API key that you provide must have at least Viewer access to the KMS instance. false N/A
But as stated before the control planes might suffer an outage and the Compute instances continue to function, if they do not require the associated service control plane (that is, increasing volume storage size, and so on)

Internal services
: All client facing internal or external services depend on the identity and platform data plane for authentication and authorization. Control planes for monitoring, logging, and IBM Cloud CLI and data plane services for security services depend on the identity platform data plane. (Specific configurations might vary.)

Storage
: The Object Storage data plane does not depend on Block Volumes or File Storage. Services that support backup and restore depend on Object Storage to operate. Therefore, those services require that the Block Volumes data and control planes exist in every deployment unit.







 Related documents 



Table 2. Related documents

 Document and Link Description 

 [SLA](https://www-03.ibm.com/software/sla/sladb.nsf/latest/bm-6605) IBM Cloud SLA 
 [Shared Responsibility Matrix](https://cloud.ibm.com/docs/overview?topic=overview-shared-responsibilities) IBM's customer shared responsibility matrix 
 [Availability of services](https://cloud.ibm.com/docs/overview?topic=overview-services_region) Listing of services available by location 
 [SLO](https://cloud.ibm.com/docs/overview?topic=overview-slo) IBM Cloud SLO