vania-janet/multiturn-rag-retrieval-data huggingface dataset:
EU-GB ingest.private.eu-gb.security-compliance-secure.cloud.ibm.com 166.9.34.56 <br>166.9.36.71 TCP 6443 
 JP-OSA ingest.private.jp-osa.security-compliance-secure.cloud.ibm.com 166.9.72.14 <br>166.9.71.15 <br>166.9.70.14 TCP 6443 
 JP-TOK ingest.private.jp-tok.security-compliance-secure.cloud.ibm.com 166.9.44.38 <br>166.9.40.35 <br>166.9.42.48 TCP 6443 
 US-EAST ingest.private.us-east.security-compliance-secure.cloud.ibm.com 166.9.22.50 <br>166.9.24.43 <br>166.9.20.53 TCP 6443 
 AU-SYD ingest.private.au-syd.security-compliance-secure.cloud.ibm.com 166.9.56.32 <br>166.9.52.27 <br>166.9.54.27 TCP 6443 
 CA-TOR ingest.private.ca-tor.security-compliance-secure.cloud.ibm.com 166.9.77.20 <br>166.9.76.23 <br>166.9.78.21 TCP 6443 
 BR-SAO ingest.private.br-sao.security-compliance-secure.cloud.ibm.com 166.9.84.19 <br>166.9.83.18 <br>166.9.82.19 TCP 6443 







 Public Collector endpoints 

The following table lists the Public Collector endpoints that are available for each region:



Table 5. List of ingestion endpoints and public IP addresses to send data to the IBM Cloud Security and Compliance Center Workload Protection

 Region Public ingestion endpoint Public IP addresses IBM Cloud Security and Compliance Center Workload Protection agent ports
Toronto (ca-tor) api.ca-tor.logging.cloud.ibm.com 169.53.161.75 <br>163.74.65.133 <br>163.75.73.42 TCP 443 <br>TCP 80 
 Washington (us-east) api.us-east.logging.cloud.ibm.com 169.47.134.86 <br>169.60.72.62 <br>169.61.107.10 TCP 443 <br>TCP 80 







 Private API endpoints 

The following table shows the private API endpoints:



Table 2. Lists of private API endpoints for interacting with IBM Log Analysis

 Region Private API endpoint Private IP addresses Ports 

 Chennai (in-che) api.private.in-che.logging.cloud.ibm.com 166.9.60.6<br><br>166.9.60.11 () TCP 443 <br>TCP 80 
 Dallas (us-south) api.private.us-south.logging.cloud.ibm.com 166.9.16.11 <br>166.9.12.12 <br>166.9.14.2<br><br>166.9.90.41 () <br>166.9.85.89 () <br>166.9.61.79 () TCP 443 <br>TCP 80 
 Frankfurt (eu-de) api.private.eu-de.logging.cloud.ibm.com 166.9.32.7 <br>166.9.28.2 <br>166.9.30.231<br><br>166.9.30.45 () <br>166.9.28.159 () <br>166.9.32.117 () TCP 443 <br>TCP 80
* [Security Bulletin: IBM Watson Speech Services Cartridge for IBM Cloud Pak for Data is vulnerable to spoofing attacks in GnuPG (CVE-2022-34903)](https://www.ibm.com/support/pages/node/6967657)
* [Security Bulletin: IBM Watson Speech Services Cartridge for IBM Cloud Pak for Data is vulnerable to a denial of service in SQLite (CVE-2022-35737)](https://www.ibm.com/support/pages/node/6967659)
* [Security Bulletin: IBM Watson Speech Services Cartridge for IBM Cloud Pak for Data is vulnerable to a heap-based buffer overflow in zlib (CVE-2022-37434)](https://www.ibm.com/support/pages/node/6967661)
* [Security Bulletin: IBM Watson Speech Services Cartridge for IBM Cloud Pak for Data is vulnerable to a denial of service in systemd (CVE-2022-3821)](https://www.ibm.com/support/pages/node/6967663)
* [Security Bulletin: IBM Watson Speech Services Cartridge for IBM Cloud Pak for Data is vulnerable to an arbitrary code execution in Gnome libxml2 (CVE-2022-40303)](https://www.ibm.com/support/pages/node/6967667)
* [Security Bulletin: IBM Watson Speech Services Cartridge for IBM Cloud Pak for Data is vulnerable to an arbitrary code execution in Gnome libxml2 (CVE-2022-40304)](https://www.ibm.com/support/pages/node/6967669)
* [Security Bulletin: IBM Watson Speech Services Cartridge for IBM Cloud Pak for Data is vulnerable to a denial of service in Python Charmers Future (CVE-2022-40899)](https://www.ibm.com/support/pages/node/6967679)
curl -X GET "https://{instance_id}.{region}.secrets-manager.appdomain.cloud/v1/ibmcloud/username_password/secrets/{secret_id}/groups/{group_id}" -H 'Accept: application/json' -H 'X-Vault-Token: {Vault-Token}'

Get an imported certificate.

curl -X GET "https://{instance_id}.{region}.secrets-manager.appdomain.cloud/v1/ibmcloud/imported_cert/secrets/{secret_id}" -H 'Accept: application/json' -H 'X-Vault-Token: {Vault-Token}'

Get an imported certificate in an existing secret group.

curl -X GET "https://{instance_id}.{region}.secrets-manager.appdomain.cloud/v1/ibmcloud/imported_cert/secrets/{secret_id}/groups/{group_id}" -H 'Accept: application/json' -H 'X-Vault-Token: {Vault-Token}'





 Example responses 

A request to retrieve an arbitrary secret returns the following response:

{
"request_id": "463e84e8-3a0c-1061-1a6e-6ce1434c7ba2",
"lease_id": "",
"renewable": false,
"lease_duration": 0,
"data": {
"created_by": "iam-ServiceId-c0c7cfa4-b24e-4917-ad74-278f2fee5ba0",
"creation_date": "2020-12-16T20:54:52Z",
"renewable": false,
"lease_duration": 0,
"data": {
"creation_date": "2020-12-15T22:08:46Z",
"description": "Extended description for my secret group.",
"id": "2bcaa289-5d38-aa57-910d-970e418ab1b3",
"last_update_date": "2020-12-15T22:08:46Z",
"name": "test-secret-group",
"type": "application/vnd.ibm.secrets-manager.secret.group+json"
},
"wrap_info": null,
"warnings": null,
"auth": null
}







 List secret groups 

Lists the secret groups that are available in your Secrets Manager service instance.



 Example request 

curl -X GET "https://{instance_id}.{region}.secrets-manager.appdomain.cloud/v1/auth/ibmcloud/manage/groups" -H 'Accept: application/json' -H 'X-Vault-Token: {Vault-Token}'





 Example response 

{
"request_id": "7ecc32f2-b78b-9290-015c-24803a1e87c9",
"lease_id": "",
"renewable": false,
"lease_duration": 0,
"data": {
"groups": [
{
"creation_date": "2020-12-14T14:48:55Z",
"description": "Read and write to Cloud Object storage buckets.",
"id": "714e070d-8122-6270-198c-fef9166729e3",
"last_update_date": "2020-12-14T14:48:55Z",
"name": "cloud-object-storage-writers",
The BAA can be digitally accepted as described in [Enabling the HIPAA Supported setting](https://cloud.ibm.com/docs/account?topic=account-enabling-hipaa).





 Legal contact information 

For subpoenas or for reporting abuse on IBM Cloud, contact the following:

IBM Cloud c/o SoftLayer Inc.
14001 North Dallas Parkway, Suite M100
Dallas, TX 75240
214.442.0600 Main
214.442.0605 Abuse
214.442.0612 Fax
Subpoenas subpoenas@softlayer.com
Abuse abuse@softlayer.com

* SoftLayer Inc. is an IBM Company
f7:25:20:96:96:47:46:ec:b7:b5:a1:ff:53:62:68:dd:cb:21:6d:9c PrivateKey /Users/hexiaohu/.hpnet-cfg/hpnet-test1-a5-d8-9a-25.priv 
 04:03:60:c8:52:5f:dc:b4:93:1b:fc:7f:62:d1:a9:54:a5:d8:9a:25 PublicKey /Users/hexiaohu/.hpnet-cfg/hpnet-test1-a5-d8-9a-25.pub 
+-------------------------------------------------------------+------------+---------------------------------------------------------+

An automatically generated keypair is stored locally and configured to node remotely.
The keypair is required to keep carefully!!!

OK
Show more

ibmcloud hpnet adminkey delete --instance "$HPVS_A" --admin-priv-key "$ADMIN_PRIV_KEY_A"

Enter passphrase to use the private key '--admin-priv-key'>
OK

Starting to decrypt key '/Users/hexiaohu/.hpnet-cfg/hpnet-test1-a5-d8-9a-25.priv'....

Connecting to the server hpnet-test1 [52.117.54.147] ...

The connecting server's certificate is valid and already confirmed in the previous command
Osaka jp-osa osa22 163.69.65.55/29 163.69.65.49 
 Osaka jp-osa osa22 163.69.65.63/29 163.69.65.57 
 Osaka jp-osa osa23 163.73.65.175/28 163.73.65.161 
 Osaka jp-osa osa23 163.73.68.95/27 163.73.68.65 
 Osaka jp-osa osa23 163.73.71.63/26 163.73.71.1 
 Osaka jp-osa osa23 163.73.67.191/29 163.73.67.185 
 Osaka jp-osa osa23 163.73.67.231/29 163.73.67.225 







 Private Subnets 



Table 14. jp-osa Private Subnets

 Location Region Data center Subnet First IP 

 Osaka jp-osa osa21 10.8.22.255/26 10.8.22.193 
 Osaka jp-osa osa21 10.8.66.127/25 10.8.66.1 
 Osaka jp-osa osa21 10.8.16.159/29 10.8.16.153 
 Osaka jp-osa osa21 10.8.16.167/29 10.8.16.161 
 Osaka jp-osa osa22 10.9.12.127/26 10.9.12.65 
 Osaka jp-osa osa22 10.9.32.255/25 10.9.32.129 
 Osaka jp-osa osa22 10.9.6.207/29 10.9.6.201 
 Osaka jp-osa osa22 10.9.6.215/29 10.9.6.209 
 Osaka jp-osa osa23 10.10.12.255/26 10.10.12.193 
 Osaka jp-osa osa23 10.10.28.255/25 10.10.28.129 
 Osaka jp-osa osa23 10.10.8.7/29 10.10.8.1
* [Implementation guidance](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-ac-6.9implementation-guidance)
* [IBM Cloud for Financial Services profile](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-ac-6.9scc-fs-cloud-profile)
* [NIST supplemental guidance](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-ac-6.9nist-supplemental-guidance)



[AC-6 (10) - Prohibit Non-privileged Users from Executing Privileged Functions](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-ac-6.10ac-6.10)



* [Control requirements](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-ac-6.10control-requirements)
* [NIST supplemental guidance](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-ac-6.10nist-supplemental-guidance)



[AC-7 - Unsuccessful Logon Attempts](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-ac-7ac-7)



* [Control requirements](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-ac-7control-requirements)
* [Additional IBM Cloud for Financial Services specifications](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-ac-7additional-ibm-cloud-for-financial-services-specifications)
curl -s -H "Authorization: Bearer $IAM_TOKEN" -X GET "https://us-east.iaas.cloud.ibm.com/v1/load_balancers/r014-020f4f34-bb49-4699-98a7-a53384cd649d?version=2021-07-30&generation=2" | jq

Sample output:

{
"id": "r014-020f4f34-bb49-4699-98a7-a53384cd649d",
"name": "nlb-vnf",
"href": "https://us-east.iaas.cloud.ibm.com/v1/load_balancers/r014-020f4f34-bb49-4699-98a7-a53384cd649d",
"crn": "crn:v1:bluemix:public:is:us-east-2:a/be636a7a6e4d4b6296bedf669ce8f757::load-balancer:r014-020f4f34-bb49-4699-98a7-a53384cd649d",
"is_public": false,
"created_at": "2021-09-14T21:45:06.377863Z",
"hostname": "020f4f34-us-east.lb.appdomain.cloud",
"listeners": [],
"operating_status": "online",
"pools": [],
"private_ips": [
{
"address": "10.241.64.13"
},
{
"address": "10.241.64.14"
}
],
"provisioning_status": "active",
"public_ips": [],
"subnets": [
{
Descriptions of the parameters that need to be provided in the export request

 Parameters Description 

 encryptionSecret A custom string that is used to encrypt and decrypt a user's hashed password. 
 tenantID The service tenant ID can be found in your service credentials. You can find your service credentials in the App ID dashboard. 



Only your Cloud Directory users and their profiles are returned. Users from other identity providers are not.







 Importing all users 

Now that you have a list of exported Cloud Directory users, you can import them into the new instance. You can use the import-all API endpoint to import a large number of users (16,000 or more) with a single request.



1. Import the list of exported users that you downloaded.

curl -X POST 'https://<region>.appid.cloud.ibm.com/management/v4/<tenantID>/import/all' 
--header 'Content-Type: application/json' 
--header 'Authorization: Bearer <IAMToken>' 
--form 'file=@"<User/desktop/myfolder/user_list.json>"' 
--form 'encryption_secret="mySecret"' 
--form 'emailAddress="jdoe@example.com"'
2. Get the status of your request, as needed.

curl -X GET 'https://<region>.appid.cloud.ibm.com/management/v4/<tenantID>/import/status?id=<id>' 
--header 'Accept: application/json' 
--header 'Content-Type: application/json' 
--header 'Authorization: Bearer <IAMToken>'



Table 4. Descriptions of the parameters that need to be provided in the import/all request

 Parameters Description 

 encryptionSecret A custom string that is used to encrypt and decrypt a user's hashed password.
Toronto (ca-tor) api.private.ca-tor.logging.cloud.ibm.com 166.9.77.23 <br>166.9.76.26 <br>166.9.78.24<br><br>166.9.78.10 () <br>166.9.76.10 () <br>166.9.77.10 () TCP 443 <br>TCP 80 
 Washington (us-east) api.private.us-east.logging.cloud.ibm.com 166.9.22.35 <br>166.9.20.72 <br>166.9.24.247<br><br>166.9.24.171 () <br>166.9.22.194 () <br>166.9.68.157 () TCP 443 <br>TCP 80 



() Indicates endpoints that are in plan to be supported. See [Service IP changes](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-service-ip-changes) for planned changes. These endpoints should be added to an allowlist in advance to avoid service interruptions.







 Ingestion endpoints 



 Public ingestion endpoints 

The following table shows the ingestion endpoints:



Table 3. Lists of public ingestion endpoints for interacting with IBM Log Analysis

 Region Public Ingestion endpoint Public IP addresses Ports 

 Chennai (in-che) logs.in-che.logging.cloud.ibm.com 169.38.75.46<br><br>169.38.94.141 () TCP 443 <br>TCP 80 
 Dallas (us-south) logs.us-south.logging.cloud.ibm.com 169.61.197.84 <br>50.22.153.155 <br>67.228.211.6<br><br>52.117.134.204 () <br>50.22.151.6 () <br>67.228.208.253 () TCP 443 <br>TCP 80
* [Security Bulletin: IBM Watson Discovery for IBM Cloud Pak for Data affected by vulnerability in Google Protocol Buffers](https://www.ibm.com/support/pages/node/6570937)
* [Security Bulletin: IBM Watson Discovery for IBM Cloud Pak for Data affected by vulnerability in Node.js](https://www.ibm.com/support/pages/node/6570939)
* [Security Bulletin: IBM Watson Discovery for IBM Cloud Pak for Data affected by vulnerability in Java](https://www.ibm.com/support/pages/node/6570941)
* [Security Bulletin: IBM Watson Discovery for IBM Cloud Pak for Data affected by vulnerability in PostgreSQL](https://www.ibm.com/support/pages/node/6570943)
* [Security Bulletin: IBM Watson Discovery for IBM Cloud Pak for Data affected by vulnerability in Kotlin](https://www.ibm.com/support/pages/node/6570945)
* [Security Bulletin: IBM Watson Discovery for IBM Cloud Pak for Data affected by vulnerability in Apache POI](https://www.ibm.com/support/pages/node/6570947)
* [Security Bulletin: IBM Watson Discovery for IBM Cloud Pak for Data is affected by a remote code execution in Spring Framework (CVE-2022-22965)](https://www.ibm.com/support/pages/node/6570949)







 IBM Watson® Discovery for IBM Cloud Private (ICP) for Data 2.2.x End Of Support 

Effective 30 April 2022, IBM will withdraw support for the following programs:



* IBM Watson Discovery for ICP for Data 2.2.x
* IBM Watson Discovery for ICP for Data Add-on 2.2.x



For more information, see announcement [ENUS921-134.PDF](https://www.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/4/897/ENUS921-134/index.html&request_locale=en).





 4.0.7 release, 30 March 2022
Osaka jp-osa osa22 163.69.68.31/27 163.69.68.1 
 Osaka jp-osa osa22 163.69.71.255/26 163.69.71.193 
 Osaka jp-osa osa22 163.69.65.55/29 163.69.65.49 
 Osaka jp-osa osa22 163.69.65.63/29 163.69.65.57 
 Osaka jp-osa osa23 163.73.65.175/28 163.73.65.161 
 Osaka jp-osa osa23 163.73.68.95/27 163.73.68.65 
 Osaka jp-osa osa23 163.73.71.63/26 163.73.71.1 
 Osaka jp-osa osa23 163.73.67.191/29 163.73.67.185 
 Osaka jp-osa osa23 163.73.67.231/29 163.73.67.225 







 Private Subnets 



Table 14. jp-osa Private Subnets

 Location Region Data center Subnet First IP 

 Osaka jp-osa osa21 10.8.22.255/26 10.8.22.193 
 Osaka jp-osa osa21 10.8.66.127/25 10.8.66.1 
 Osaka jp-osa osa21 10.8.16.159/29 10.8.16.153 
 Osaka jp-osa osa21 10.8.16.167/29 10.8.16.161 
 Osaka jp-osa osa22 10.9.12.127/26 10.9.12.65 
 Osaka jp-osa osa22 10.9.32.255/25 10.9.32.129 
 Osaka jp-osa osa22 10.9.6.207/29 10.9.6.201 
 Osaka jp-osa osa22 10.9.6.215/29 10.9.6.209 
 Osaka jp-osa osa23 10.10.12.255/26 10.10.12.193
ibmcloud secrets-manager secret-versions 

List the versions of a secret.

A successful request returns the list of versions of a secret, along with the metadata of each version.

ibmcloud secrets-manager secret-versions --secret-id SECRET-ID



 Command options 

--secret-id (string)
: The ID of the secret. Required.

The maximum length is 36 characters. The minimum length is 36 characters. The value must match regular expression /[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}/.





 Example 

ibmcloud secrets-manager secret-versions --secret-id=0b5571f7-21e6-42b7-91c5-3f5ac9793a46





 Example output 

Example secret version metadata collection response

{
"versions" : [ {
"created_at" : "2022-06-27T11:58:15Z",
"created_by" : "iam-ServiceId-e4a2f0a4-3c76-4bef-b1f2-fbeae11c0f21",
"expiration_date" : "2023-10-05T11:49:42Z",
"id" : "bc656587-8fda-4d05-9ad8-b1de1ec7e712",
"payload_available" : true,
"secret_group_id" : "67d025e1-0248-418f-83ba-deb0ebfb9b4a",
"secret_id" : "67d025e1-0248-418f-83ba-deb0ebfb9b4a",
"secret_name" : "example-imported-certificate",
"secret_type" : "imported_cert",
--- -----
token s.6yFk0Z1IRi0Yc5DtwIKuENDJ
token_accessor BnEHQuAxTiHJGhP1x0hNqagV
token_duration 57m58s
token_renewable true
token_policies ["default" "instance-manager"]
identity_policies []
policies ["default" "instance-manager"]
token_meta_grant_type urn:ibm:params:oauth:grant-type:apikey
token_meta_name test-ibm-cloud-api-key
token_meta_resource crn:v1:bluemix:public:secrets-manager:us-south:a/791f5fb10986423e97aa8512f18b7e65:e415e570-f073-423a-abdc-55de9b58f54e::
token_meta_user iam-ServiceId-222b47ab-b08e-4619-b68f-8014a2c3acb8
token_meta_bss_acc 791f5fb10986423e97aa8512f18b7e65

Now you can use Vault CLI commands to interact with your Secrets Manager instance. To find out more, check out the [CLI reference](https://cloud.ibm.com/docs/secrets-manager?topic=secrets-manager-vault-cli).
"secret_id" : "cb7a2502-8ede-47d6-b5b6-1b7af6b6f563",
"secret_group_id" : "bc656587-8fda-4d05-9ad8-b1de1ec7e712",
"last_update_date" : "2022-04-24T16:50:09.692573+03:00",
"secret_version_alias" : "current"
}, {
"name" : "lock-2",
"description" : "lock for consumer-2",
"creation_date" : "2020-08-27T14:29:01Z",
"created_by" : "IBM-id-1",
"attributes" : {
"key" : "value"
},
"secret_version_id" : "5bf89b0c-df55-c8d5-7ad6-8816951c6784",
"secret_id" : "cb7a2502-8ede-47d6-b5b6-1b7af6b6f563",
"secret_group_id" : "bc656587-8fda-4d05-9ad8-b1de1ec7e712",
"last_update_date" : "2022-04-24T16:50:09.692573+03:00",
"secret_version_alias" : "current"
} ]
}







 ibmcloud secrets-manager secret-version-lock 

Create a lock on the specified version of a secret.

A lock can be used to prevent a secret from being deleted or modified while it's in use by your applications. A successful request attaches a new lock to the specified version, or replaces a lock of the same name if it already exists. Additionally, you can use this method to clear any matching locks on a secret version by using one of the following optional lock modes:
For more information about the command options, see [ibmcloud secrets-manager secret](https://cloud.ibm.com/docs/secrets-manager?topic=secrets-manager-cli-plugin-secrets-manager-clisecrets-manager-cli-secret-command).



 Downloading certificates 

When you're working with certificates, you might need the ability to download the payload of a certificate into a pem file by using the CLI. To do so, you can use the Secrets Manager CLI plug-in and jq.

To store the certificate into a pem file, run the [ibmcloud secrets-manager secret](https://cloud.ibm.com/docs/secrets-manager?topic=secrets-manager-cli-plugin-secrets-manager-clisecrets-manager-cli-secret-command) command.

ibmcloud secrets-manager secret --id=SECRET_ID | jq -r '.certificate' | sed 's/\n/n/g' > my-cert-file.pem

The command outputs the value of the certificate and stores it to my-cert-file.pem. For more information about the command options, see [ibmcloud secrets-manager secret](https://cloud.ibm.com/docs/secrets-manager?topic=secrets-manager-cli-plugin-secrets-manager-clisecrets-manager-cli-secret-command).







 Retrieving a secret with the API 

After you store a secret in your instance, you might need to retrieve its value so that you can connect to an external app or get access to a protected service. You can retrieve the value of a secret by using the Secrets Manager API.

The following example request retrieves a secret and its contents. When you call the API, replace the ID variables and IAM token with the values that are specific to your Secrets Manager instance.

curl -X GET
-H "Authorization: Bearer {iam_token}" -H "Accept: application/json" 
"https://{instance_ID}.
curl -X GET "https://{instance_id}.{region}.secrets-manager.appdomain.cloud/v1/ibmcloud/username_password/locks/groups/{group_id}/{secret_id}?limit={limit}&offset={offset}" -H 'Accept: application/json' -H 'X-Vault-Token: {Vault-Token}'

Filter for locks that contain book in their names.

curl -X GET "https://{instance_id}.{region}.secrets-manager.appdomain.cloud/v1/ibmcloud/username_password/locks/groups/{group_id}/{secret_id}?search=book" -H 'Accept: application/json' -H 'X-Vault-Token: {Vault-Token}'





 Example response 

{
"request_id": "ba51140d-31a8-0a51-dd5b-1ca59838e881",
"lease_id": "",
"renewable": false,
"lease_duration": 0,
"data": {
"locks": [
{
"attributes": {
"key": "value"
},
"created_by": "iam-ServiceId-222b47ab-b08e-4619-b68f-8014a2c3acb8",
"creation_date": "2022-06-30T21:41:36.616174Z",
"description": "Test lock for secret in the default secret group.",
"last_update_date": "2022-06-30T21:41:36.616174Z",
"name": "lock-for-app-2",
"secret_group_id": "default",
"secret_id": "184408d6-8264-5ff3-c308-6922ed04ad88",
"secret_type": "arbitrary",
"state": 1,
"state_description": "Active",
"versions": [
{
"created_by": "iam-ServiceId-c0c7cfa4-b24e-4917-ad74-278f2fee5ba0",
"creation_date": "2020-12-16T20:54:52Z",
"id": "03d9ddb3-aa1d-d929-40c8-04027213ef08"
}
]
},
"wrap_info": null,
"warnings": null,
"auth": null
}

A request to retrieve an arbitrary secret in an existing secret group returns the following response:

{
"request_id": "791340bd-5664-c1e3-e779-d1391494f55d",
"lease_id": "",
"renewable": false,
"lease_duration": 0,
"data": {
"created_by": "iam-ServiceId-c0c7cfa4-b24e-4917-ad74-278f2fee5ba0",
"creation_date": "2020-12-15T22:34:53Z",
"crn": "crn:v1:bluemix:public:secrets-manager:us-south:a/a5ebf2570dcaedf18d7ed78e216c263a:0f4c764e-dc3d-44d1-bd60-a2f7cd91e0c0:secret:a6972127-35ad-b36f-aac8-0223f0475cb6",
"description": "Extended description for my secret.",
"expiration_date": "2030-04-01T09:30:00Z",
curl -X GET "https://s3.us-south.cloud-object-storage.appdomain.cloud" -H "Authorization: Bearer $IAM_TOKEN" -H "ibm-service-instance-id: $COS_INSTANCE_ID" -H "Accept: application/json"

The following XML snippet shows an example response.

<ListAllMyBucketsResult xmlns="http://s3.amazonaws.com/doc/2006-03-01/">
<Owner>
<ID>cccbd89c-6eb0-4aed-8ffb-899d39bc022e</ID>
<DisplayName>cccbd89c-6eb0-4aed-8ffb-899d39bc022e</DisplayName>
</Owner>
<Buckets>
<Bucket>
<Name>test-secrets-tutorial</Name>
<CreationDate>2020-12-14T21:40:55.739Z</CreationDate>
</Bucket>
</Buckets>
</ListAllMyBucketsResult>

To see the contents of your test-secrets-tutorial bucket, you can run the following command.

curl -X GET "https://s3.us-south.cloud-object-storage.appdomain.cloud/test-secrets-tutorial" -H "Authorization: Bearer $IAM_TOKEN" -H "ibm-service-instance-id: $COS_INSTANCE_ID" -H "Accept: application/json"

The following XML snippet shows an example response.

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<ListBucketResult xmlns="http://s3.amazonaws.com/doc/2006-03-01/">
<Name>test-secrets-tutorial</Name>
<Prefix></Prefix>
<Marker></Marker>
<MaxKeys>1000</MaxKeys>