vania-janet/multiturn-rag-retrieval-data huggingface dataset:
The region abbreviation, such as us-south or eu-gb, that represents the geographic area where your Key Protect instance resides. <br> <br>For more information, see [Regional service endpoints](https://cloud.ibm.com/docs/key-protect?topic=key-protect-regionsservice-endpoints). 
 IAM_token Required. Your IBM Cloud access token. Include the full contents of the IAM token, including the Bearer value, in the curl request. <br> <br>For more information, see [Retrieving an access token](https://cloud.ibm.com/docs/key-protect?topic=key-protect-retrieve-access-token). 
 instance_ID Required. The unique identifier that is assigned to your Key Protect service instance. <br> <br>For more information, see [Retrieving an instance ID](https://cloud.ibm.com/docs/key-protect?topic=key-protect-retrieve-instance-ID). 
 key_ring_ID Optional. The unique identifier of the key ring that the key is a part of. <br>If unspecified, Key Protect will search for the key in every key ring associated with the specified instance. It is recommended to specify the key ring ID for a more optimized request. <br> <br>Note: The key ring ID of keys that are created without an x-kms-key-ring header is: default. <br> <br>For more information, see [Grouping keys](https://cloud.ibm.com/docs/key-protect?topic=key-protect-grouping-keys). 



A successful request returns an HTTP 204 No Content response, which indicates that your Key Protect instance is now enabled for dual authorization. Keys that you create or import to the service now require two authorizations before they can be deleted. For more information, see [Deleting keys](https://cloud.ibm.com/docs/key-protect?topic=key-protect-delete-keys).

This new policy does not affect existing keys in your instance.
Your IBM Cloud access token. Include the full contents of the IAM token, including the Bearer value, in the curl request. <br> <br>For more information, see [Retrieving an access token](https://cloud.ibm.com/docs/key-protect?topic=key-protect-retrieve-access-token). 
 instance_ID Required. The unique identifier that is assigned to your Key Protect service instance. <br> <br>For more information, see [Retrieving an instance ID](https://cloud.ibm.com/docs/key-protect?topic=key-protect-retrieve-instance-ID). 
 correlation_ID Optional.The unique identifier that is used to track and correlate transactions. 



A successful POST api/v2/key_rings request returns an HTTP 201 Created response, which indicates that the key ring was created and is now available for to hold standard and root keys.





 Transferring a key to a different key ring 

As requirements change and new team members are brought into an org, you might create new key rings to reflect these organizational changes. After creating the key rings, it might be necessary to move a key from an existing key ring to a new key ring that has different IAM permissions. For example, you might be onboarding a team that will need specific access to a key that is part of to a custom, non-default key ring that was previously made. You can create a new key ring that is dedicated to the onboarding team and, since keys can only be associated with one key ring at a time, you will need to move the key to the new key ring.

Because a key ring cannot be deleted as long as it contains keys in any state (including the destroyed state keys are moved to after they are deleted but before they are automatically purged 90 days after deletion), if you want to delete a key ring, you might need to transfer keys to a different ring first.

After transferring a key to a different key ring, it may take up to a maximum of ten minutes for the change to take effect.



 Transferring a key to a different key ring with the UI
ibmcloud iam service-id-delete ServiceId-cb258cb9-8de3-4ac0-9aec-b2b2d27ac976

For more information about managing API keys by using the CLI, see [Managing IAM access](https://cloud.ibm.com/docs/account?topic=cli-ibmcloud_commands_iam&interface=cliibmcloud_iam_service_id_delete).







 Deleting a service ID by using the API 

To delete a service ID, call the [IAM Identity Services API](https://cloud.ibm.com/apidocs/iam-identity-token-apidelete-service-id) as shown in the following example:



* Curl
* Java
* Python
* Go
* Node



curl -X DELETE 'https://iam.cloud.ibm.com/v1/serviceids/SERVICE_ID_UNIQUE_ID' -H 'Authorization: Bearer TOKEN' -H 'Content-Type: application/json'

DeleteServiceIdOptions deleteServiceIdOptions = new DeleteServiceIdOptions.Builder()
.id(svcId)
.build();

Response<Void> response = service.deleteServiceId(deleteServiceIdOptions).execute();

response = iam_identity_service.delete_service_id(id=svc_id)

deleteServiceIDOptions := iamIdentityService.NewDeleteServiceIDOptions(svcID)

response, err := iamIdentityService.DeleteServiceID(deleteServiceIDOptions)
if err != nil {
panic(err)
}

const params = {
id: svcId,
};

iamIdentityService.deleteServiceId(params)
.then(res => {
done();
})
For information about the exact actions mapped to each role, see [IAM roles and actions](https://cloud.ibm.com/docs/account?topic=account-iam-service-roles-actions) and [Db2 Warehouse](https://cloud.ibm.com/docs/account?topic=account-iam-service-roles-actionsdb2-warehouse).





 Prerequisites 



* Db2 Client V11.1 FP3 or later.
* Must use SSL connections through port 50001.
* [Configure your Db2 client](https://cloud.ibm.com/docs/Db2whc?topic=Db2whc-ssl_supportssl_cfg_client).
* Catalog your database. See [Connecting to your database: step 2](https://cloud.ibm.com/docs/Db2whc?topic=Db2whc-ssl_supportssl_conn_db).







 Client connections and user logins 

The following methods can be used for IAM authentication:



 Access token 

An access token can be obtained from the IAM service directly by the application through the REST API by using an API key. For more information, see: [Getting an IBM Cloud IAM token by using an API key](https://cloud.ibm.com/docs/account?topic=account-iamtoken_from_apikey). The access token has a default validity period of 60 minutes before it expires. If the token has expired, the Db2 server won't allow the connection to be established. The token isn’t checked for expiry after the connection is established. Just as it was before IAM integration, the connection stays connected until the application disconnects or the connection is terminated due to other reasons.

curl -k -X POST 
--header "Content-Type: application/x-www-form-urlencoded" 
--header "Accept: application/json" 
--data-urlencode "grant_type=urn:ibm:params:oauth:grant-type:apikey"
Also, for admins, the user_ctx property can be used to trigger a replication for another user. This user context is passed to local target database document validation functions.

The user_ctx property applies to local endpoints only.

In summary, for admins, the user_ctx property is optional. While for regular (nonadmin) users, it's mandatory. When the roles property of user_ctx is missing, it defaults to the empty list [ ].





 Performance-related options 

Several performance-related options can be set for a replication, by including them in the replication document.

use_bulk_get
: Set to true to improve replication job performance. A replication fetches documents in batches from the source. The increased replication rate can consume the source and target account capacity quicker, and result in concurrent nonreplication requests on those accounts to experience more 429 HTTP errors.

connection_timeout
: The maximum period of inactivity for a connection in milliseconds. If a connection is idle for this period, its current request is retried. Default value is 30000 milliseconds (30 seconds).

http_connections
: The maximum number of HTTP connections per replication. For push replications, the effective number of HTTP connections that are used is min(worker_processes + 1, http_connections). For pull replications, the effective number of connections that are used corresponds to this parameter's value. Default value is 20.

retries_per_request
: The maximum number of retries per request. Before a retry, the replicator waits for a short period before it repeats the request. This period doubles between each consecutive retry, and never goes beyond 5 minutes. The minimum value before the first retry is 0.25 seconds. The default value is 10 retries.

socket_options
: A list of options to pass to the connection sockets. The available options can be found in the [documentation for the Erlang function setopts of the inet module](https://www.erlang.org/doc/man/inet.htmlsetopts-2).
For information about the exact actions mapped to each role, see [IAM roles and actions](https://cloud.ibm.com/docs/account?topic=account-iam-service-roles-actions) and [Db2](https://cloud.ibm.com/docs/account?topic=account-iam-service-roles-actionsdb2).





 Prerequisites 



* Db2 Client V11.1 FP3 or later.
* Must use SSL connections through port 50001.
* [Configure your Db2 client](https://cloud.ibm.com/docs/Db2onCloud?topic=Db2onCloud-ssl_supportssl_cfg_client).
* Catalog your database. See [Connecting to your database: step 2](https://cloud.ibm.com/docs/Db2onCloud?topic=Db2onCloud-ssl_supportssl_conn_db).







 Client connections and user logins 

The following methods can be used for IAM authentication:



 Access token 

An access token can be obtained from the IAM service directly by the application through the REST API by using an API key. For more information, see: [Getting an IBM Cloud IAM token by using an API key](https://cloud.ibm.com/docs/account?topic=account-iamtoken_from_apikey). The access token has a default validity period of 60 minutes before it expires. If the token has expired, the Db2 server won't allow the connection to be established. The token isn’t checked for expiry after the connection is established. Just as it was before IAM integration, the connection stays connected until the application disconnects or the connection is terminated due to other reasons.

curl -k -X POST 
--header "Content-Type: application/x-www-form-urlencoded" 
--header "Accept: application/json" 
--data-urlencode "grant_type=urn:ibm:params:oauth:grant-type:apikey"
The current redemption fee, which is subject to change, can be found at [https://www.ibm.com/cloud/dns](https://www.ibm.com/cloud/dns). If You do not redeem Your domain name prior to the end of the redemption grace period IBM Cloud may, at its sole discretion, delete Your domain name or transfer it to another registrant on Your behalf.





 Term of Agreement; Modifications 

This Agreement continues in full force and effect as long as You have any domain name registered through IBM Cloud. You agree that You will not transfer any domain name registered through IBM Cloud to another domain name registrar during the first sixty (60) days from its initial registration date. You further agree that IBM Cloud may charge You a small fee if You cancel Your domain within the five-day grace period after registering Your domain with IBM Cloud and IBM Cloud refunds the price of Your domain. IBM Cloud will not charge You a fee if IBM Cloud cancels Your domain name during this period because of fraud.

You agree that IBM Cloud may modify this Agreement from time to time, and You agree to be bound by any such changes. IBM Cloud may also discontinue services it provides under this Agreement. Should You elect to cancel Your Agreement, You will not receive a refund for any fees You have paid to IBM Cloud.

You agree that IBM Cloud is not bound by any representations made by third parties who You may use to purchase services from IBM Cloud, and that any statements of a general nature which may be posted on IBM Cloud’s website or contained in IBM Cloud’s promotional materials will not bind IBM Cloud.





 Your Account Information 

It is Your responsibility to keep Your account information current. If You fail to do so, or fail to respond within five business days of IBM Cloud inquiring as to the validity of Your information, You will be in material breach of this Agreement.

You agree that for each domain name You register, the following information will be made publicly available in the Whois directory, and may be sold in bulk, as set forth by ICANN policy and the ICANN agreement:



* The domain name
* Your name and postal address
* The email address, postal address, voice and fax numbers for technical and administrative contacts
Action parameter Description 

 bucket The bucket parameter is the name of the IBM Cloud Object Storage bucket. 
 endpoint The endpoint parameter is the IBM Cloud Object Storage endpoint that is used to connect to your IBM Cloud Object Storage instance. You can locate your endpoint in the [IBM Cloud Object Storage documentation](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-endpoints). 
 expires The expires parameter is the number of seconds to expire the pre-signed URL operation. The default expires value is 15 minutes. 
 ibmAuthEndpoint The ibmAuthEndpoint parameter is the IBM Cloud authorization endpoint that is used to generate a token from the apikey. The default authorization endpoint works for all IBM Cloud Regions. 
 key The key parameter is the object name. 
 operation The operation parameter is the pre-signed URL's operation to call. 
 corsConfig The corsConfig parameter is a bucket's CORS configuration.
If a certificate expires in more than five years, the expiration date is not visible from the console.[↩](https://cloud.ibm.com/docs/blockchain?topic=blockchain-cert-mgmtfootnote-how-to-view1-ref)
2. If a certificate expires in more than five years, the expiration date is not visible from the console.[↩](https://cloud.ibm.com/docs/blockchain?topic=blockchain-cert-mgmtfootnote-how-to-view2-ref)
3. If a certificate expires in more than five years, the expiration date is not visible from the console.[↩](https://cloud.ibm.com/docs/blockchain?topic=blockchain-cert-mgmtfootnote-how-to-view3-ref)
4. If a certificate expires in more than five years, the expiration date is not visible from the console.[↩](https://cloud.ibm.com/docs/blockchain?topic=blockchain-cert-mgmtfootnote-how-to-view4-ref)
Watson IoT Platform organizations that were created by using IBM Cloud® use temporary user profiles by default.

You can resolve this problem by accessing your Watson IoT Platform organization by using IBM Cloud and changing the expiration setting for your user profile. To change your user expiration settings:



1. From your IBM Cloud dashboard, open your Watson IoT Platform service.
2. Click Members from the navigation bar.
3. Click the Edit icon.
4. Clear the Access expires check box and click Save.







 Problem connecting to the Watson IoT Platform 

Your connection to the Watson IoT Platform drops or disconnects unexpectedly.

When you attempt to connect to the Watson IoT Platform, your device or application receives an error.

You might have more than one device that is trying to connect with the same client ID and credentials. Only one unique connection is allowed per clientID. You cannot have multiple concurrent connections that use the same ID. Applications can share the same API key, but MQTT requires that the client ID is always unique.

You can rule out this reason by verifying that you don't have multiple devices that are trying to connect by using the same credentials.





 Device intermittently disconnects from Watson IoT Platform 

Your device connection to the Watson IoT Platform intermittently drops unexpectedly.

A device that is connected to the Watson IoT Platform service is disconnected intermittently. The device reconnects, but it is unexpectedly disconnected again after a while.

It might be that when you connect, you are using a value for an MQTT ping option that is too low, which makes it look like the connection timed out. For example, if the client MQTT is set incorrectly, pings are not received in a timely manner, and the connection is closed.

You can fix this problem by confirming that you have properly set the ping and KeepAlive parameters for your connection.





 Subscription to Device events fails using MQTT 

When you subscribe to events for a device, the connection always closes so the subscription does not take effect.

You see a message like the following on the dashboard: Closed connection. The topic is not valid: format_string. The topic does not match an authorized rule
Stopping a CDN 

After a mapping is stopped, the DNS lookup is switched to the origin. Traffic skips the CDN Edge servers and content is fetched directly from the origin. After a mapping is stopped, there might be a brief period of time where your content is not accessible. This is because the DNS cache might still be directing traffic to the Akamai Edge servers. However, during this time, the Akamai Edge server denies traffic for the domain. How long this period lasts depends on how often the DNS cache is refreshed, and varies depending on your DNS provider.

Important:



*  You can only stop a CDN when in Running state.
*  Stopping a CDN is NOT recommended for a CDN configured with an HTTPS SAN certificate because HTTPS traffic might not work when you move the CDN back to Running status.
*  Stop CDN functionality is intended for maintenance windows not exceeding seven days. After seven days, the CDN must be started, or it is disabled and traffic to the CDN CNAME is notredirected to the origin server.
*  Currently, stopping a Wildcard CDN with the CNAME suffix .cdnedge.bluemix.net is NOT allowed.



To stop a CDN, follow these steps:



1.  Click Stop CDN from the Overflow ![Overflow menu](https://cloud.ibm.com/docs-content/v1/content/006fd22ab2811b7d19804c763a00568b3da4c03a/CDN/images/overflow.png) menu.
2.  A window appears, asking you to confirm that you want to stop the service. Select Confirm to proceed.

After 5 to 15 seconds, the status changes to Stopped.
If https secure protocol is not enabled on your instance, you can use your instance IP address instead of the host name.

In the request, you specify an expiration time for the token. The default is 5 minutes, but you can specify that it expires sooner or later (5 seconds to 1 hour).

The response (a JSON payload) contains the instance identity access token. Use this token to access the metadata service.

You can also generate an IAM token from this token and use the RIAS API to call IAM-enabled services. For more information, see [Generate an IAM token from an instance identity access token](https://cloud.ibm.com/docs/vpc?topic=vpc-imd-configure-service&interface=cliimd-token-exchange).





 Acquire an instance identity access token 

Using the Metadata service API, make PUT "https://api.metadata.cloud.ibm.com/instance_identity/v1/token call to get an instance identity access token from the token service. The following example uses jq to parse the JSON API response and then extract the instance identity access token value. You can use your preferred JSON parser.

In the example, the return value of the cURL command is the instance identity access token, which is extracted by jq and placed in the instance_identity_token environment variable. You use specify this variable in a GET call to the metadata service to reach the metadata endpoint. For more information, see [Retrieve metadata from your running instances](https://cloud.ibm.com/docs/vpc?topic=vpc-imd-get-metadata&interface=apiimd-retrieve-instance-data).

The example uses jq as a parser, a third-party tool licensed under the [MIT license](https://stedolan.github.io/jq/download/). jq might not come preinstalled on all VPC images available when you create an instance. You might need to install jq before use or use any parser of your choice.
If https secure protocol is not enabled on your instance, you can use your instance IP address instead of the host name.

In the request, you specify an expiration time for the token. The default is 5 minutes, but you can specify that it expires sooner or later (5 seconds to 1 hour).

The response (a JSON payload) contains the instance identity access token. Use this token to access the metadata service.

You can also generate an IAM token from this token and use the RIAS API to call IAM-enabled services. For more information, see [Generate an IAM token from an instance identity access token](https://cloud.ibm.com/docs/vpc?topic=vpc-imd-configure-service&interface=apiimd-token-exchange).





 Acquire an instance identity access token 

Using the Metadata service API, make PUT "https://api.metadata.cloud.ibm.com/instance_identity/v1/token call to get an instance identity access token from the token service. The following example uses jq to parse the JSON API response and then extract the instance identity access token value. You can use your preferred JSON parser.

In the example, the return value of the cURL command is the instance identity access token, which is extracted by jq and placed in the instance_identity_token environment variable. You use specify this variable in a GET call to the metadata service to reach the metadata endpoint. For more information, see [Retrieve metadata from your running instances](https://cloud.ibm.com/docs/vpc?topic=vpc-imd-get-metadata&interface=apiimd-retrieve-instance-data).

The example uses jq as a parser, a third-party tool licensed under the [MIT license](https://stedolan.github.io/jq/download/). jq might not come preinstalled on all VPC images available when you create an instance. You might need to install jq before use or use any parser of your choice.
If https secure protocol is not enabled on your instance, you can use your instance IP address instead of the host name.

In the request, you specify an expiration time for the token. The default is 5 minutes, but you can specify that it expires sooner or later (5 seconds to 1 hour).

The response (a JSON payload) contains the instance identity access token. Use this token to access the metadata service.

You can also generate an IAM token from this token and use the RIAS API to call IAM-enabled services. For more information, see [Generate an IAM token from an instance identity access token](https://cloud.ibm.com/docs/vpc?topic=vpc-imd-configure-service&interface=uiimd-token-exchange).





 Acquire an instance identity access token 

Using the Metadata service API, make PUT "https://api.metadata.cloud.ibm.com/instance_identity/v1/token call to get an instance identity access token from the token service. The following example uses jq to parse the JSON API response and then extract the instance identity access token value. You can use your preferred JSON parser.

In the example, the return value of the cURL command is the instance identity access token, which is extracted by jq and placed in the instance_identity_token environment variable. You use specify this variable in a GET call to the metadata service to reach the metadata endpoint. For more information, see [Retrieve metadata from your running instances](https://cloud.ibm.com/docs/vpc?topic=vpc-imd-get-metadata&interface=apiimd-retrieve-instance-data).

The example uses jq as a parser, a third-party tool licensed under the [MIT license](https://stedolan.github.io/jq/download/). jq might not come preinstalled on all VPC images available when you create an instance. You might need to install jq before use or use any parser of your choice.