vania-janet/multiturn-rag-retrieval-data huggingface dataset:
curl -X GET "$vpc_api_endpoint/v1/instances/r006-44905aa4-119d-5622-00ce-face32b78999?version=2022-09-06&generation=2" -H "Authorization: Bearer $iam_token" | jq -r '(.image)'

When you run this command, you see the following output.

{
"crn": "crn:v1:bluemix:public:is:us-south:a/123456::image:r006-6cab2dbd-4e57-4dc5-810b-b7366cb78999",
"href": "https://us-south.iaas.cloud.ibm.com/v1/images/r006-6cab2dbd-4e57-4dc5-810b-b7366cb78999",
"id": "r006-6cab2dbd-4e57-4dc5-810b-b7366cb78999",
"name": "test-image"
}

If you try to retrieve information about this image by using its id,

curl -X GET "$vpc_api_endpoint/v1/images/r006-6cab2dbd-4e57-4dc5-810b-b7366cb78999?version=2022-09-06&generation=2" -H "Authorization: Bearer $iam_token"

then this attempt fails with HTTP status code 404 (not found). This status code means that the image doesn't exist in your account. If the instance was provisioned by using a shared catalog image in another account, this response is the response that you always get even if the image still exists in the owning account.

Additionally, it is possible that the referenced image might have the same name as a custom image in your account. But these image names are for two different images in two different accounts.
<binary DER-encoded certificate >





 Read CA certificate chain 

You can retrieve with this endpoint the CA certificate chain, which includes the CA in PEM format. This endpoint is bare. It doesn't return a standard Vault data structure and the Vault CLI can't read it.

GET v1/ibmcloud/private_cert/config/certificate_authorities/:ca-name/ca_chain

Response 200 OK
<PEM-encoded certificate chain>

To verify that the CA chain is from the context of a leaf certificate, you can configure your CAs in Secrets Manager with the property "issuing_certificates_urls_encoded": true. In each leaf or intermediate CA certificate, this configuration encodes the URL that is used for downloading the issuing CA certificate in the property Authority Information Access/CA Issuers. Then, your CA validator can validate each CA certificate.







 Next steps 

Now you're ready to create certificate authorities for your instance.



* [Create a root certificate authority](https://cloud.ibm.com/docs/secrets-manager?topic=secrets-manager-root-certificate-authorities)
* [Create an intermediate certificate authority](https://cloud.ibm.com/docs/secrets-manager?topic=secrets-manager-intermediate-certificate-authorities)
* [Add a certificate template](https://cloud.ibm.com/docs/secrets-manager?topic=secrets-manager-certificate-templates)
7. Run the following command to display the client certificate and CA, server certificate and KEY in base64-encoding: 

./build.py instance-env --env sbs-config.json

The following snippet shows example output, including the encrypted base64-encoded values for CLIENT_CRT,CLIENT_CA, SERVER_CRT, and SERVER_KEY, which you need in the next step

INFO:root:client_certificate: using supplied pem files client_crt_key=.SBContainer-3576faac-1a48-47dc-9702-6b46068cddf1 capath=./.SBContainer-3576faac-1a48-47dc-9702-6b46068cddf1.d/client-ca.pem cakeypath=./.SBContainer-3576faac-1a48-47dc-9702-6b46068cddf1.d/client-ca-key.pem
INFO:__main__:

 Copy below environment variables and use in instance-create command. 

-e CLIENT_CRT=... -e CLIENT_CA=... -e SERVER_CRT=... -e SERVER_KEY=...





 8. Provision the Secure Build Server instance 

First, copy the encrypted registration definition for the Secure Build image into a new file named secure_build.asc. The content of the encrypted registration definition is located [here](https://cloud.ibm.com/docs/hp-virtual-servers?topic=hp-virtual-servers-imagebuilddeploysecurebuild).

Then, use the following command line to provision a new instance of the Secure Build Server. Insert the values for the environment variables CLIENT_CRT and CLIENT_CA, SERVER_CRT and SERVER_KEY taken from the output of the preceding command.
For this example, you see a response that is similar to the following output.

Name vCPU Manufacturer Architecture Family vCPUs Memory(GiB) Bandwidth(Mbps) Volume bandwidth(Mbps) GPUs Storage(GB) Min NIC Count Max NIC Count
bx2-2x8 intel amd64 balanced 2 8 4000 1000 - - 1 5
bx2a-2x8 amd amd64 balanced 2 8 2000 500 - - 1 5
bx2d-2x8 intel amd64 balanced 2 8 4000 1000 - 1x75 1 5
bx2-4x16 intel amd64 balanced 4 16 8000 2000 - - 1 5
bx2a-4x16 amd amd64 balanced 4 16 4000 1000 - - 1 5
bx2d-4x16 intel amd64 balanced 4 16 8000 2000 - 1x150 1 5

For more information about available profiles, see [x86 instance profiles](https://cloud.ibm.com/docs/vpc?topic=vpc-profiles) and [s390x instance profiles](https://cloud.ibm.com/docs/vpc?topic=vpc-vs-profiles).

Secure execution-enabled profiles are now available and are identified by the fourth character of the profile name that is an "e", such as bz2e. For more information, see [Confidential computing with LinuxONE](https://cloud.ibm.com/docs/vpc?topic=vpc-about-se).

The secure execution-enabled profiles are available for Balanced, Compute, and Memory families. Make sure that you use secure-enabled profiles when you use the IBM Hyper Protect Container Runtime image. Profile validation for the IBM-provided stock images and the IBM Hyper Protect Container Runtime occurs in the RIAS layer. Any profile mismatch results in an error message that is similar to the following example.

FAILED
Response HTTP Status Code: 400
Error code: bad_field
Error message: Image OS IBM Hyper Protect is not supported by the instance profile <profile_name>
Error target name: profile, type: field
6.
* [RootFS field details](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_cli_listregistry_cli_list_imageinspect_rootfs)





[Container Registry CLI change log](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_cli_change_logregistry_cli_change_log)



* [Version 1.1.0](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_cli_change_logcli-change-logv1-110)
* [Version 1.0.11](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_cli_change_logcli-change-logv1-1011)
* [Version 1.0.8](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_cli_change_logcli-change-logv1-108)
* [Version 0.1.587](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_cli_change_logcli-change-log-01587)
* [Version 1.0.6](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_cli_change_logcli-change-logv1-106)
* [Version 1.0.5](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_cli_change_logcli-change-logv1-105)
* [Version 0.1.585](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_cli_change_logcli-change-log-01585)
* [Version 1.0.2](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_cli_change_logcli-change-logv1-102)
[Formatting and filtering the CLI output](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_cli_listregistry_cli_list)



* [Go template options for ibmcloud cr image-digests](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_cli_listregistry_cli_list_imagedigests)
* [Go template options for ibmcloud cr image-list](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_cli_listregistry_cli_list_imagelist)
* [Go template options for ibmcloud cr image-inspect](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_cli_listregistry_cli_list_imageinspect)



* [Config field details](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_cli_listregistry_cli_list_imageinspect_config)
* [Healthcheck field details](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_cli_listregistry_cli_list_imageinspect_healthcheck)
* [RootFS field details](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_cli_listregistry_cli_list_imageinspect_rootfs)





[Container Registry CLI change log](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_cli_change_logregistry_cli_change_log)



* [Version 1.1.0](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_cli_change_logcli-change-logv1-110)
container_nlb_dns](https://registry.terraform.io/providers/IBM-Cloud/ibm/1.37.0/docs/resources/container_nlb_dns)<br> * [ibm_container_storage_attachment](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/container_storage_attachment)<br> * [ibm_container_vpc_alb](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/container_vpc_alb)<br> * [ibm_container_vpc_alb_create](https://registry.terraform.io/providers/IBM-Cloud/ibm/1.37.0/docs/resources/container_vpc_alb_create)<br> * [ibm_container_vpc_cluster](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/container_vpc_cluster)<br> * [ibm_container_vpc_worker](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/container_vpc_worker)<br> * [ibm_container_vpc_worker_pool](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/container_vpc_worker_pool)<br> * [ibm_container_worker_pool](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/container_worker_pool)<br> * [ibm_container_worker_pool_zone_attachment](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/container_worker_pool_zone_attachment)<br> * [ibm_ob_logging](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/ob_logging)<br> * [ibm_ob_
For more information, see [Creating a cluster by using an IBM Cloud Schematics template](https://cloud.ibm.com/docs/openshift?topic=openshift-templates&interface=ui).

IBM Cloud Object Storage plug-in
: Version 2.1.3 is [released](https://cloud.ibm.com/docs/openshift?topic=openshift-cos_plugin_changelog). Master fix pack update change log documentation
: Master fix pack update change log documentation is available for version [4.7.23_1529_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_474723_1529), [4.6.42_1553_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_464642_1553), [4.5.41_1549_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-changelog_archive4541_1549), and [3.11.487_1601_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_311311487_1601).





 23 August 2021 

Registry token update
: Registry tokens are no longer accepted for authentication in IBM Cloud Container Registry. Update your clusters to use IBM Cloud IAM authentication. For more information, see [Accessing IBM Cloud Container Registry](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_access). For more information about Registry token deprecation, see [IBM Cloud Container Registry Deprecates Registry Tokens for Authentication](https://www.ibm.com/cloud/blog/announcements/ibm-cloud-container-registry-deprecates-registry-tokens-for-authentication).

Ingress change logs
[Available](https://cloud.ibm.com/docs-content/v1/content/11f96f96f8f4b60cf6f3fa4d904856a2c4528bc2/icons/checkmark-icon.svg) ![Available](https://cloud.ibm.com/docs-content/v1/content/11f96f96f8f4b60cf6f3fa4d904856a2c4528bc2/icons/checkmark-icon.svg) 
 Catalog: View Published Catalogs ![Available](https://cloud.ibm.com/docs-content/v1/content/11f96f96f8f4b60cf6f3fa4d904856a2c4528bc2/icons/checkmark-icon.svg) ![Available](https://cloud.ibm.com/docs-content/v1/content/11f96f96f8f4b60cf6f3fa4d904856a2c4528bc2/icons/checkmark-icon.svg) ![Available](https://cloud.ibm.com/docs-content/v1/content/11f96f96f8f4b60cf6f3fa4d904856a2c4528bc2/icons/checkmark-icon.svg) ![Available](https://cloud.ibm.com/docs-content/v1/content/11f96f96f8f4b60cf6f3fa4d904856a2c4528bc2/icons/checkmark-icon.svg) 
 Certificate Library: Manage ![Available](https://cloud.ibm.com/docs-content/v1/content/11f96f96f8f4b60cf6f3fa4d904856a2c4528bc2/icons/checkmark-icon.svg) !
* [3 June 2019](https://cloud.ibm.com/docs/containers?topic=containers-containers-relnotescontainers-june0319)



* Bringing your own Ingress controller
* IBM Cloud Object Storage
* Ingress ALB change log
* Kustomize
* Razee





* [May 2019](https://cloud.ibm.com/docs/containers?topic=containers-containers-relnotescontainers-may19)



* [30 May 2019](https://cloud.ibm.com/docs/containers?topic=containers-containers-relnotescontainers-may3019)



* CLI reference
* Troubleshooting storage



* [28 May 2019](https://cloud.ibm.com/docs/containers?topic=containers-containers-relnotescontainers-may2819)



* Cluster add-ons change log
* Troubleshooting registry
* Troubleshooting storage



* [23 May 2019](https://cloud.ibm.com/docs/containers?topic=containers-containers-relnotescontainers-may2319)



* CLI reference
* Cluster add-ons change log
* Cluster and worker states
* Cluster planning and creation
* Cluster version updates
* Istio
* Popular topics



* [20 May 2019](https://cloud.ibm.com/docs/containers?topic=containers-containers-relnotescontainers-may2019)



* Version change logs



* [16 May 2019](https://cloud.ibm.com/docs/containers?topic=containers-containers-relnotescontainers-may1619)



* CLI reference
* Unsupported: Kubernetes version 1.10



* [15 May 2019](https://cloud.ibm.com/docs/containers?topic=containers-containers-relnotescontainers-may1519)



* Default Kubernetes version
* Service limits
* [Setting up the internal container image registry](https://cloud.ibm.com/docs/openshift?topic=openshift-satellite-clusterssatcluster-internal-registry)



* [Setting up the internal container image registry with IBM Cloud Object Storage](https://cloud.ibm.com/docs/openshift?topic=openshift-satellite-clusterssatcluster-internal-registry-cos)



* [Exposing apps](https://cloud.ibm.com/docs/openshift?topic=openshift-satellite-clusterssatcluster-expose-apps)
* [Storing application data in persistent storage](https://cloud.ibm.com/docs/openshift?topic=openshift-satellite-clusterssatcluster-storage)
* [Removing Satellite worker nodes or clusters](https://cloud.ibm.com/docs/openshift?topic=openshift-satellite-clusterssatcluster-rm)
* [Limitations for Red Hat OpenShift clusters in IBM Cloud Satellite](https://cloud.ibm.com/docs/openshift?topic=openshift-satellite-clusterssatcluster-limitations)
* [Pricing for clusters in Satellite](https://cloud.ibm.com/docs/openshift?topic=openshift-satellite-clusterssatcluster-pricing)
* [Bringing your own OCP license](https://cloud.ibm.com/docs/openshift?topic=openshift-satellite-clustersbyo-ocp-satellite)



[Creating a private-only cluster in VPC by using a Schematics template](https://cloud.ibm.com/docs/openshift?topic=openshift-templatestemplates)



* [Resources that are created from the template](https://cloud.ibm.com/docs/openshift?topic=openshift-templatessch-tf-resources-created)
* [Log in to your container registries](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift-storage-odf-privateodf-storage-login-registry)
* [Create a namespace in IBM Cloud Container Registry](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift-storage-odf-privateodf-private-registry-namespace-create)
* [Mirror the Operator index to IBM Cloud Container Registry](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift-storage-odf-privateodf-storage-mirror-catalog)
* [Create a secret to pull images from IBM Cloud Container Registry](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift-storage-odf-privateodf-storage-create-secret)
* [Update the catalog source in your cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift-storage-odf-privateodf-storage-create-catalog)
* [Update your image pull secret](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift-storage-odf-privateodf-private-update-dockerconf)
* [Replace each worker node to pick up configuration changes](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift-storage-odf-privateodf-private-reload-workers)
* [Update the registries.conf file on each node](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift-storage-odf-privateodf-private)
* [Reboot each worker node](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift-storage-odf-privateodf-private-reboot-workers)
[Retrieve your authentication credentials to work with the API](https://cloud.ibm.com/docs/key-protect?topic=key-protect-set-up-api).
2. View the registrations that match a CRN query that you specify by running the following curl command.

$ curl -X GET "https://<region>.kms.cloud.ibm.com/api/v2/keys/registrations" -H "authorization: Bearer <IAM_token>" -H "bluemix-instance: <instance_ID>"

Replace the variables in the example request according to the following table.





Table 6. Describes the variables that are needed to list registrations for any key in your Key Protect instance.

 Variable Description 

 region Required. 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). 





 Filter registrations for any root key 

You can filter for a set of registrations that are associated with any root key managed in your provisioned instance of Key Protect by specifying the preventKeyDeletion and urlEncodedResourceCRNQuery parameters at query time.
* [Version 1.0.430](https://cloud.ibm.com/docs/containers?topic=containers-cs_cli_changelogcli-10430)
* [Version 1.0.426](https://cloud.ibm.com/docs/containers?topic=containers-cs_cli_changelogcli-10426)
* [Version 1.0.419](https://cloud.ibm.com/docs/containers?topic=containers-cs_cli_changelogcli-10419)
* [Version 1.0.415](https://cloud.ibm.com/docs/containers?topic=containers-cs_cli_changelogcli-10415)
* [Version 1.0.408](https://cloud.ibm.com/docs/containers?topic=containers-cs_cli_changelogcli-10408)
* [Version 1.0.404](https://cloud.ibm.com/docs/containers?topic=containers-cs_cli_changelogcli-10404)
* [Version 1.0.403](https://cloud.ibm.com/docs/containers?topic=containers-cs_cli_changelogcli-10403)
* [Version 1.0.394](https://cloud.ibm.com/docs/containers?topic=containers-cs_cli_changelogcli-10394)
* [Version 1.0.384](https://cloud.ibm.com/docs/containers?topic=containers-cs_cli_changelogcli-10384)
* [Version 1.0.374](https://cloud.ibm.com/docs/containers?topic=containers-cs_cli_changelogcli-10374)
* [Version 1.0.372](https://cloud.ibm.com/docs/containers?topic=containers-cs_cli_changelogcli-10372)
IBM Cloud File Storage for Classic plug-in 347 348 Image updated for [CVE-2019-14697](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14697). 
 IBM Cloud Provider v1.13.8-188 v1.13.9-209 Updated to support the Kubernetes 1.13.9 release. 
 Kubernetes v1.13.8 v1.13.9 See the [Kubernetes release notes](https://github.com/kubernetes/kubernetes/releases/tag/v1.13.9). Updates resolves [CVE-2019-11247](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-11247) (see [IBM security bulletin](https://www.ibm.com/support/pages/node/967115)) and [CVE-2019-11249](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-11249) (see [IBM security bulletin](https://www.ibm.com/support/pages/node/967123)). 
 Kubernetes DNS 1.14.13 1.15.4 See the [Kubernetes DNS release notes](https://github.com/kubernetes/dns/releases/tag/1.15.4). Image update resolves [CVE-2019-14697](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14697). 
 Load balancer and load balancer monitor for IBM Cloud Provider 146 147 Image updated for [CVE-2019-14697](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14697).
* [ibmcloud ks ingress domain rm](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-cliingress-domain-rm)
* [ibmcloud ks ingress domain secret regenerate](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-cliingress-domain-secret-regenerate)
* [ibmcloud ks ingress domain secret rm](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-cliingress-domain-secret-rm)
* [ibmcloud ks ingress domain update](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-cliingress-domain-update)
* [ibmcloud ks ingress instance default set](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_ingress_instance_default_set)
* [ibmcloud ks ingress instance default unset](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_ingress_instance_default_unset)
* [ibmcloud ks ingress instance get](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_ingress_instance_get)
* [ibmcloud ks ingress instance ls](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_ingress_instance_ls)
* [ibmcloud ks ingress instance register](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_ingress_instance_register)
For more information, about the description of ibm_container_cluster argument reference such as public_vlan_id, private_vlan_id, kube_version values, refer to [registry documentation of ibm_container_cluster](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/container_clusterargument-reference).

Example for an Red Hat OpenShift on IBM Cloud cluster

data "ibm_resource_group" "resource_group" {
name = "default"
}

resource "ibm_container_cluster" "tfcluster" {
name = "tfcluster"
datacenter = "dal10"
machine_type = "b3c.4x16"
hardware = "shared"
public_vlan_id = "<public_vlan_ID_dal10>"
private_vlan_id = "<private_vlan_ID_dal10>"

kube_version = "3.11_openshift"

default_pool_size = 3

public_service_endpoint = "true"
private_service_endpoint = "true"

resource_group_id = data.ibm_resource_group.resource_group.id
}
Show more

For more information, about the description of ibm_container_cluster argument reference such as public_vlan_id, private_vlan_id, kube_version values, refer to [registry documentation of ibm_container_cluster](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/container_clusterargument-reference).
2. Initialize the Terraform on IBM Cloud CLI.

terraform init
3. Create an Terraform on IBM Cloud execution plan. When you execute this command, Terraform on IBM Cloud validates the syntax of your configuration file and resource definitions against the specifications of the IBM Cloud Provider plug-in.

terraform plan

Example output:

Refreshing Terraform on IBM Cloud state in-memory prior to plan...
<br> <br>For more information, see [Retrieving an instance ID](https://cloud.ibm.com/docs/key-protect?topic=key-protect-retrieve-instance-ID). 



A successful GET api/v2/keys/<keyID_or_alias>/registrations request returns a collection of registrations that are mapped to the specified key ID.

{
"metadata": {
"collectionType": "application/vnd.ibm.kms.registration+json",
"collectionTotal": 2
},
"resources": [
{
"keyId": "12e8c9c2-a162-472d-b7d6-8b9a86b815a6",
"resourceCrn": "crn:v1:bluemix:public:cloud-object-storage:global:a/<account-id>:<service-instance>:bucket:<bucket-name>",
"createdBy": "IBMid-25555555",
"creationDate": "2010-01-12T05:23:19+0000",
"updatedBy": "IBMid-25555555",
"lastUpdated": "2010-01-12T05:23:19+0000",
"description": "A description of the registration",
"preventKeyDeletion": true,
"keyVersion": {
"id": "12e8c9c2-a162-472d-b7d6-8b9a86b815a6",
"creationDate": "2010-01-12T05:23:19+0000"
}
},
{
"keyId": "2291e4ae-a14c-4af9-88f0-27c0cb2739e2",