Home > Storage > ObjectScale and ECS > Product Documentation > ECS Storage Broker Installation Guide > Binding an instance
For your application to be able access the ECS bucket created, you will need to tell sv-cat to bind (create object user/access key) the bucket to your application namespace in Kubernetes.
Issue the below command to bind your instance.
root@local:~/ecs-cf-service-broker# svcat bind demo-instance
Name: demo-instance
Namespace: default
Status:
Secret: demo-instance
Instance: demo-instance
Parameters:
No parameters defined
Note: As with the previous instance provisioning, it is important to remember whether a namespace was defined during provisioning, as this setting must match on the binding.
To validate the binding was successful issue the below command.
root@local:~# svcat get bindings
NAME NAMESPACE INSTANCE STATUS
+---------------+-----------+---------------+--------+
demo-instance default demo-instance Ready
To explore further what the binding has done with Kubernetes you the describe command. This will show the secret information which has been placed into your application namespace in Kubernetes.
root@local:~# svcat describe binding demo-instance
Name: demo-instance
Namespace: default
Status: Ready - Injected bind result @ 2020-07-10 14:43:02 +0000 UTC
Secret: demo-instance
Instance: demo-instance
Parameters:
No parameters defined
Secret Data:
accessKey 48 bytes
bucket 48 bytes
endpoint 25 bytes
path-style-access 4 bytes
s3Url 168 bytes
secretKey 40 bytes