---
name: containers-ts-app-svc-key
title: Why does binding a service to a cluster results in service does not support service keys error?
description: '[Virtual Private Cloud] [Classic infrastructure]'
last-updated: 2025-02-03
---

> ## Documentation Index
> The table of contents for this documentation set is at https://cloud.ibm.com/docs/containers?format=markdown
> The index for all IBM Cloud docs is at: https://cloud.ibm.com/docs/llms.txt
> Use these files to discover more information as needed.

# Why does binding a service to a cluster results in service does not support service keys error?
{: #ts-app-svc-key}
{: support}

[Virtual Private Cloud]{: tag-vpc} [Classic infrastructure]{: tag-classic-inf}


When you run `ibmcloud ks cluster service bind --cluster <cluster_name> --namespace <namespace> --service <service_instance_name>`, you see the following message.
{: tsSymptoms}

```sh
This service doesn't support creation of keys
```
{: screen}



Some services in IBM Cloud, such as IBM&reg; Key Protect don't support the creation of service credentials, also referred to as service keys. Without the support of service keys, the service can't be bound to a cluster. To learn how to connect services, see [Connecting services to apps](https://cloud.ibm.com/docs/account?topic=account-service_credentials&format=markdown).
{: tsCauses}



To integrate services that don't support service keys, check if the service provides an API that you can use to access the service directly from your app. For example, if you want to use IBM&reg; Key Protect, see the [API reference](https://cloud.ibm.com/apidocs/key-protect){: external}.
{: tsResolve}