vania-janet/multiturn-rag-retrieval-data huggingface dataset:
[Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/6f3c07c34058f637b1c86044ca4f9b24214330a7/activity-tracker/images/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/6f3c07c34058f637b1c86044ca4f9b24214330a7/activity-tracker/images/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/6f3c07c34058f637b1c86044ca4f9b24214330a7/activity-tracker/images/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/6f3c07c34058f637b1c86044ca4f9b24214330a7/activity-tracker/images/checkmark-icon.svg) 
 Long-term retention policy NO NO NO NO 



[15]: Currently, you cannot use your own key with a bucket that has a retention policy configured.

Use the customer-managed encryption model to manage and control the key that is used to encrypt data at-rest.

[After you designate a root key in Key Protect](https://cloud.ibm.com/docs/key-protect?topic=key-protect-create-root-keys) and [grant access between your services](https://cloud.ibm.com/docs/key-protect?topic=key-protect-integrate-servicesgrant-access), you can enable envelope encryption for a specified storage bucket by using the IBM Cloud Object Storage GUI.
Auditing 

You can monitor data access in your IBM® Db2® Warehouse on Cloud instance with the built-in Db2 audit facility. Use the Db2 audit facility to generate and maintain an audit trail for a series of predefined database events, including attempts to access or manipulate database objects, user authentication, SQL statement execution, and even access to the audit log. Use the audit log to reveal usage patterns that would identify system misuse, and in turn, take action to eliminate such misuse.

Before initial configuration, you must collect the following information:



 Cloud Object Storage credentials 

[IBM Cloud Object Storage ](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-uhc-hmac-credentials-main)

Example,

cos_hmac_keys:
access_key_id: 7exampledonotusea6440da12685eee02
secret_access_key: 8not8ed850cddbece407exampledonotuse43r2d2586

[Amazon Simple Storage Service (S3) ](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_access-keys.htmlUsing_CreateAccessKey)

Example,

access key ID: AKIAIOSFODNN7EXAMPLE
secret access key: wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY





 Cloud Object Storage bucket name 

You must create a bucket that will store the audit records. You will need to save the bucket name during initial configuration. It is recommended that you do not use this bucket for other purposes. Consider securely configuring the bucket with appropriate encryption, access management, and data retention.

For cost control measures, you should set a quota to the [relevant bucket](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-quota) and set an [expiration rule](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-expiry).
cloud-object-storage.bucket-acl.read Get the bucket<br><br>ACL 
 cloud-object-storage.bucket-acl.create Create the bucket<br><br>ACL 
 cloud-object-storage.bucket-crn.read Get the bucket CRN 
 cloud-object-storage.bucket-location.read Get the bucket location 
 cloud-object-storage.bucket-retention.read Get the bucket retention 
 cloud-object-storage.bucket-retention.create Create the bucket retention 
 cloud-object-storage.bucket-key-state.update Updating a Key Protect root encryption key 
 cloud-object-storage.bucket-public-access-block.create Add a public ACL block configuration 
 cloud-object-storage.bucket-public-access-block.read Read a public ACL block configuration 
 cloud-object-storage.bucket-public-access-block.delete Delete a public ACL block configuration 



For cloud-object-storage.bucket-key-state.update events, the following fields include extra information:



 Field Description 

 requestData.eventType The type of lifecyle event that occured, such as deletion, rotation, etc. 
 requestData.requestedKeyState The the requested state of the key (enabled or disabled). 
 requestData.requestKeyVersion The requested version of the key. 
 requestData.bucketLocation The location of the bucket that uses the key. 
 responseData.eventID The unique identifier associated with the key lifecycle event. 
 responseData.adopterKeyState The current state the key (enabled or disabled). 
 responseData.adopterKeyVersion The current version of the key. 
 {: caption="Table 3a. Additional fields for bucket-key-state.update events"} 







 Object events 

The following table lists the COS object events:



Table 4. Object events

 Action Description 

 cloud-object-storage.object-cors.read Get the CORS configuration 
 cloud-object-storage.object-acl.read Get the object ACL 
 cloud-object-storage.object-acl.create Create the object ACL
This table has row and column headers. The row headers provide the service role name and the column headers identify the specific information available about each role.

 Role Description 

 Manager As a manager, you have permissions beyond the writer role to complete privileged actions as defined by the service. In addition, you can create and edit service-specific resources. 
 Reader As a reader, you can perform read-only actions within a service such as viewing service-specific resources. 
 Writer As a writer, you have permissions beyond the reader role, including creating and editing service-specific resources. 







 Cloud Foundry Enterprise Environment 

Review the available platform and service roles and the actions mapped to each to help you assign access. If you're using the CLI or API to assign access, use cfaas for the service name.

No supported roles.





 Cloud Object Storage 

Review the available platform and service roles and the actions mapped to each to help you assign access. If you're using the CLI or API to assign access, use cloud-object-storage for the service name.

Service roles

Actions



Table 17. Service roles - Cloud Object Storage
Use the tab buttons to change the context of the table. This table has row and column headers. The row headers provide the service role name and the column headers identify the specific information available about each role.

 Role Description 

 Content Reader As a Content Reader, one can read and list objects in the bucket. 
 Manager As a Manager, one can create/modify/delete buckets including managing retention policy, configuring IP addresses. In addition, one can upload and download the objects in the bucket. 
 Notifications Manager As a Notifications Manager, the service can manage (view/modify/delete) configuration for notifications on a Cloud Object Storage bucket. 
 Object Reader As an Object Reader, one can read objects in the bucket. 
 Object Writer As an Object Writer, one can only write objects to a bucket. 
 Reader As a Reader, one can view bucket configuration and download the objects in the bucket. 
 Writer As a Writer, one can create/modify/delete buckets. In addition, one can upload and download the objects in the bucket. 







 Cloudant
Amsterdamams03-standard / ams03-vault / ams03-cold / ams03-smart
   Chennaiche01-standard / che01-vault / che01-cold / che01-smart
   Mexicomex01-standard / mex01-vault / mex01-cold / mex01-smart
   Milanmil01-standard / mil01-vault / mil01-cold / mil01-smart
   Montréalmon01-standard / mon01-vault / mon01-cold / mon01-smart
   Parispar01-standard / par01-vault / par01-cold / par01-smart
   San Josesjc04-standard / sjc04-vault / sjc04-cold / sjc04-smart
   São Paulosao01-standard / sao01-vault / sao01-cold / sao01-smart
   Singaporesng01-standard / sng01-vault / sng01-cold / sng01-smart

For more information about endpoints, see [Endpoints and storage locations](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-endpointsendpoints).





 Using the REST API, Libraries, and SDKs 

Several new APIs have been introduced to the IBM COS SDKs to provide support for applications working with retention policies. Select a language (curl, Java, JavaScript, Go, or Python) at the beginning of this page to view examples that use the appropriate COS SDK.

All code examples assume the existence of a client object that is called cos that can call the different methods. For details on creating clients, see the specific SDK guides.



 Create a bucket with a storage class 



* Java
* Python
* Go
* Node



public static void createBucket(String bucketName) {
System.out.printf("Creating new bucket: %sn", bucketName);
_cos.createBucket(bucketName, "us-vault");
System.out.printf("Bucket: %s created!n", bucketName);
}
cloud-object-storage.object.copy_part Copy (write) an object part. 
 cloud-object-storage.object.copy_part_get Copy (read) an object part. 
 cloud-object-storage.object.post_complete_upload Complete a multipart upload. 
 cloud-object-storage.object.copy Copy (write) an object from one bucket to another. 
 cloud-object-storage.object.copy_get Copy (read) an object from one bucket to another. 
 cloud-object-storage.object.get_acl Read object ACL [deprecated]. 
 cloud-object-storage.object.put_acl Write object ACL [deprecated]. 
 cloud-object-storage.object.put_acl_version Unsupported operation - used for S3 API compatibility only. 
 cloud-object-storage.object.delete Delete an object. 
 cloud-object-storage.object.delete_version Delete a specific version of an object. 
 cloud-object-storage.object.get_uploads List parts of an object. 
 cloud-object-storage.object.delete_upload Abort a multipart upload. 
 cloud-object-storage.object.restore Temporarily restore an archived object. 
 cloud-object-storage.object.post_multi_delete Delete multiple objects. 
 cloud-object-storage.object.post_legal_hold Add a legal hold to an object. 
 cloud-object-storage.object.get_legal_hold View any legal holds on an object. 
 cloud-object-storage.object.post_extend_retention Extend a retention policy. 
 cloud-object-storage.provide_ibm_client_originating_ip_address Internal use only - unsupported for users. 
 cloud-object-storage.bucket.put_public_access_block Add a public ACL block configuration 
 cloud-object-storage.bucket.get_public_access_block Read a public ACL block configuration 
 cloud-object-storage.bucket.delete_public_access_block Delete a public ACL block configuration
Add or remove a legal hold to or from a protected object 

The object can support 100 legal holds:



* A legal hold identifier is a string of maximum length 64 characters and a minimum length of 1 character. Valid characters are letters, numbers, !, _, ., , (, ), - and \.
* If the addition of the given legal hold exceeds 100 total legal holds on the object, the new legal hold will not be added, a 400 error is returned.
* If an identifier is too long, it will not be added to the object and a 400 error is returned.
* If an identifier contains invalid characters, it will not be added to the object and a 400 error is returned.
* If an identifier is already in use on an object, the existing legal hold is not modified and the response indicates that the identifier was already in use with a 409 error.
* If an object does not have retention period metadata, a 400 error is returned and adding or removing a legal hold is not allowed.



The user making adding or removing a legal hold must have Manager permissions for this bucket.

def add_legal_hold_to_object(bucket_name, object_name, legal_hold_id):
print("Adding legal hold {0} to object {1} in bucket {2}n".format(legal_hold_id, object_name, bucket_name))

cos.add_legal_hold(
Bucket=bucket_name,
Key=object_name,
RetentionLegalHoldId=legal_hold_id
)

print("Legal hold {0} added to object {1} in bucket {2}!n".format(legal_hold_id, object_name, bucket_name))

def delete_legal_hold_from_object(bucket_name, object_name, legal_hold_id):
print("Deleting legal hold {0} from object {1} in bucket {2}n".format(legal_hold_id, object_name, bucket_name))

cos.delete_legal_hold(
Bucket=bucket_name,
Key=object_name,
Compliance 

IBM Cloud® Object Storage actively participates in several industry compliance programs.

This feature is not currently supported in Object Storage for Satellite. [Learn more.](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-about-cos-satellite)

An updated list of our compliance certifications can always be obtained by referencing the [Data Processing and Protection Datasheet](https://www.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProduct?deliverableId=89904B80AE1911E7A9EB066095601ABB) available from [IBM Software Product Compatibility Reports](https://www.ibm.com/software/reports/compatibility/clarity/softwareReqsForProduct.html).

Clients are responsible for ensuring their own compliance with any applicable laws and regulations and are solely responsible for obtaining advice of competent legal counsel as to the identification and interpretation of any relevant laws and regulations that may affect the clients’ business as well as any actions the clients may need to take to comply with such laws and regulations. IBM does not provide legal, accounting, or auditing advice or represent or warrant that its services or products will ensure that clients are in compliance with any law or regulation.

For a listing of available certificates and instructions on obtaining pertinent reports please visit [IBM Cloud Compliance](https://www.ibm.com/cloud/compliance) page or contact an [IBM Sales representative](https://www.ibm.com/account/reg/us-en/signup?formid=MAIL-wcp).



 International Organization for Standardization (ISO) 

IBM Cloud Object Storage is certified for ISO 27001, ISO 27017, and ISO 27018.

For available certificates, please refer to listings titled “IBM Cloud Services (PaaS and SaaS) certificates” on the IBM Cloud Compliance page.





 System and Organization Controls (SOC) 

IBM Cloud Object Storage is certified for SOC 1 Type 2, SOC 2 Type 2, and SOC 3.





 Payment Card Industry (PCI) data security standards 

IBM Cloud Object Storage is compliant with the PCI data security standards.





 HIPAA readiness
Provisioning Object Storage for Satellite 

You can provision Object Storage for Satellite using the IBM Cloud console.



 Before you begin 

Before deploying Object Storage in a Satellite location, you must first deploy [a Satellite location](https://cloud.ibm.com/docs/satellite?topic=satellite-locations) with sufficient computing hosts and raw block storage allocated for provisioning Object Storage.

Object Storage for Satellite requires OpenShift 4.7.



 Object Storage capacity Raw storage required Minimum host requirements 

 Small (12 TB) 18 TB 9 nodes of 4 vCPU and 16 GiB memory 
 Medium (24 TB) 36 TB 9 nodes of 4 vCPU and 16 GiB memory 
 Large (48 TB) 72 TB 9 nodes of 4 vCPU and 16 GiB memory 
 Extra Large (96 TB) 144 TB 18 nodes of 4 vCPU and 16 GiB memory 



For more information on configuring hosts for storage, [see the Satellite documentation](https://cloud.ibm.com/docs/satellite?topic=satellite-host-reqsreqs-host-storage).

Unlike cloud storage which scales elastically, there may be negative performance impacts when an instance gets near capacity. Workloads that demand higher performance may benefit from the additional computing power provided by the Extra Large plan, regardless of total storage required.

When provisioning block storage, is recommended to use a ["Silver" storage class at a minimum](https://cloud.ibm.com/docs/satellite?topic=satellite-config-storage-ebssat-ebs-sc-reference) to ensure adequate performance.





 Configure a satellite location 



1. Follow the documentation to [create a new Satellite location](https://cloud.ibm.com/docs/satellite?topic=satellite-locations) with [the necessary hosts](https://cloud.ibm.com/docs/satellite?topic=satellite-attach-hosts) and [storage resources](https://cloud.ibm.com/docs/satellite?topic=satellite-sat-storage-template-ov).
2. Grant the necessary service authorizations.



1. Configure your IAM Authorizations under the Manage tab.
"time_created": "2018-03-26T16:23:36.980Z",
"time_updated": "2018-10-17T19:29:10.117Z",
"object_count": 764265234,
"bytes_used": 28198745752445144
}





 Get resource information from an API 

The resource controller is the next-generation IBM Cloud Platform provisioning layer that manages the lifecycle of Object Storage resources in a customer account. The API can provide actual billable metrics, such as types of requests and charges for storage, to get you started. More information can be found at the [documentation](https://cloud.ibm.com/apidocs/resource-controller)

curl -X GET https://resource-controller.cloud.ibm.com/v2/resource_instances -H 'Authorization: Bearer <IAM_TOKEN>'

An appropriate response should list metadata for your resources as shown in the example.

{
"rows_count": 1,
"next_url": "/v2/resource_instances?next_docid=g1AAAACkeJzLYWBgYMpgTmFQSklKzi9KdUhJMtTLTMrVTSouNjAw1EvOyS9NScwr0ctLLckBqc1jAZIMC4DU____92eBxdycyiQ6O2sOMCQxMLHnZKEaZ0qEcQ8gxv2HG-fo9M_-Asg4-TVZWQCZcDI1&limit=2&account_id=d86af7367f70fba4f306d3c19c7344b2",
"resources": [
{
"id": "crn:v1:bluemix:public:cloud-object-storage:global:a/4329073d16d2f3663f74bfa955259139:8d7af921-b136-4078-9666-081bd8470d94::",
Now you know that your Object Storage subscription was created successfully and that the Object Storage subscription is ready to serve events, you can update the Object Storage subscription with the [ibmcloud ce sub cos update](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-subscription-cos-update) command. For example, you can change your subscription to run only when specific operations happen on a subset of objects in the bucket.



1. Update the Object Storage subscription to forward events only when delete operations happen on files with a name prefix of test.

ibmcloud ce sub cos update --name cos-sub --event-type delete --prefix test
2. Run the [ibmcloud ce sub cos get](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-subscription-cos-get) command to find information about your subscription.

ibmcloud ce sub cos get --name cos-sub

Example output

In this output, you can see that the updated values for Prefix and EventType are displayed.

Getting COS event subscription 'cos-sub'...
OK
Name: cos-sub
ID: abcdefgh-abcd-abcd-abcd-1a2b3c4d5e6f
Project Name: myproject
Project ID: 01234567-abcd-abcd-abcd-abcdabcd1111
Age: 4m16s
Created: 2021-02-01T13:11:31-05:00
Destination: App:cos-app
Bucket: mybucket
EventType: delete
Prefix: test
Ready: true

Conditions:
Type OK Age Reason
CosConfigured true 24m
Ready true 24m
ReadyForEvents true 24m
SinkProvided true 24m

Events:
Type Reason Age Source Messages
Normal CosSourceReady 9s (x2 over 24m) cossource-controller CosSource is ready
3.
Why can't the IBM Cloud Object Storage bucket be found? 

A flow log collector requires a IBM Cloud Object Storage bucket to be created and accessible. If you see the error log with message ID is.flow-log-collector.00003E, the bucket does not exist, or is no longer accessible. The flow log collector cannot publish data to the IBM Cloud Object Storage bucket.

To avoid lost data, create an IBM Cloud Object Storage bucket within the next 24 hours to correct this problem.

  What’s happening 

The flow log collector lost connection to an IBM Cloud Object Storage bucket: is.flow-log-collector.00003E: Cloud Object Storage bucket <BucketName> was not found

  Why it’s happening 

A bucket that is associated with a flow log collector was deleted, or is not accessible by a flow log collector.

  How to fix it 

Follow these steps to resolve this issue:



1.  Create an IBM Cloud Object Storage bucket with the same <BucketName> specified in the error message. To create a IBM Cloud Object Storage bucket, see the [IBM Cloud Object Storage](https://cloud.ibm.com/catalog/services/cloud-object-storage) ordering page.

The IBM Cloud Object Storage bucket must be a single-region bucket in the same region as the target resource. Additionally, it is recommended that you secure the bucket through IAM access groups and audit logging.
2.  Check to make sure that you defined an authorization between the flow log collector and the IBM Cloud Object Storage bucket so that the flow log collector can publish data. To define an authorization, use the following steps:



*  In the IBM Cloud console, click Manage > Access (IAM).
*  Select Authorizations from the navigation pane.
*  Click Create.
*  For Source service:



*  Select VPC Infrastructure Services. Then, select Services based on attributes.
*  Select Resource type. Then, select Flow Logs for VPC.
*  Select Source resource instance and choose an option.



*  For Target service:



*  Select Cloud Object Storage. Then, select Services based on attributes.
*  Select Service instance and choose an option.



*  For Service access, select the Writer role.
*  Click Authorize.





For more information, see [Creating a flow log collector](https://cloud.ibm.com/docs/vpc?topic=vpc-ordering-flow-log-collector).
Enter your IBM Cloud Object Storage credentials in the username field. The format of the username must be object_storage_username:IBM_Cloud_username. For example, ABC-DE123456-7:user. You can find your Object Storage username under Storage > Object Storage.
8. Enter a Bucket Name to store the data. The bucket name is the container name where you want to store the data in IBM Cloud Object Storage.



* Don't modify the default port unless otherwise directed to by your network administrator. The Enable Archiving field defaults to No and click Next.



9. Enter the License Request Token, if necessary, and click Next.
10. Enter an Encryption Key. You can allow AltaVault to generate a new encryption key or enter an existing key that you want to use to encrypt and decrypt the data. Click Next.
11. Verify that all your settings are correct and then click Finish and Apply. AltaVault now attempts to contact the IBM Cloud Object Storage service by using the inputs and settings that are in the Cloud Settings Wizard. If the connection fails, review your settings and make sure that you have the appropriate access to the service.
12. Click Exit after a connection is established to return to the Wizard Dashboard and click Exit Wizard to return to the AltaVault appliance status page.
13. Verify that the Storage Optimization Service is running and that the status is ready. Note: It might take few minutes for the status to change to Ready.



The AltaVault appliance is configured to communicate with the IBM Cloud Object Storage service.





 Configuring the CIFS/SMB mount point in AltaVault 

You need to configure the e0b interface to create a CIFS/SMB mount point. Use the following steps to configure the e0b interfave.



1. Go to Settings > Data Interfaces and expand the e0b interface. Select Enable Data Interface, and enter the IP address, Subnet Mask, and Gateway that you use to mount the CIFS/SMB share.
2. Leave the default MTU value of 1500 bytes.