--- title: "IBM Cloud Satellite With Wasabi" slug: "how-do-i-use-ibm-cloud-satellite-with-wasabi" updated: 2026-05-29T23:58:08Z published: 2026-05-29T23:58:08Z --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.wasabi.com/llms.txt > Use this file to discover all available pages before exploring further. # IBM Cloud Satellite With Wasabi Wasabi has been validated for use with[IBM Cloud Satellite](https://www.ibm.com/cloud/satellite?utm_content=SRCWW&p1=Search&p4=43700056326614888&p5=e&gclid=CjwKCAjw_MqgBhAGEiwAnYOAejsFbaB8mYteobXXW6LxNVLsvZGIN9qDp1dT33MoTML4sGZfZmUuqhoCkkkQAvD_BwE&gclsrc=aw.ds). The IBM Cloud Satellite-managed distributed cloud solution delivers cloud services, APIs, access policies, security controls, and compliance. To use Wasabi Object Storage with workload running in IBM Cloud Satellite Locations, follow the instructions below. ## Reference Architecture ![Screenshot_2023-03-29_at_1.21.45_PM.png](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/14082417053339.png) #### Prerequisites - **On the IBM Cloud side**: An IBM Cloud account and a Satellite location [created](https://cloud.ibm.com/docs/satellite?topic=satellite-locations) and [configured](https://cloud.ibm.com/docs/satellite?topic=satellite-setup-clusters-satconfig). - **On the Wasabi side**: An active Wasabi account, at least one bucket, and an Access Key/Secret Key pair. ## Integration Scenarios There are multiple use cases for the IBM Cloud Satellite with Wasabi integration. This article outlines a few use cases. To learn more about Satellite use cases in general, refer to [Satellite Use Cases](https://cloud.ibm.com/docs/satellite?topic=satellite-use-case&interface=cli). ## Base Integration Satellite Locations are mini cloud regions and, in most cases, do not need a direct integration to Wasabi cloud object storage. You can run any application workload that uses object storage and leverages the S3 API function unchanged as long as their API usage does not hardcode AWS (or IBM, MinIO, and so on.) endpoints. Wasabi provides an S3-compatible object storage solution with defined API endpoints. Existing applications that utilize 'boto3', or any of the other S3-compatible API libraries, can supply the Wasabi endpoint and user credentials. Below are examples of some products within IBM’s data portfolio that work OOTB (out of the box) with Wasabi. ### Running IBM Cloud Pak for Data and Watson Studio with Wasabi ![Screenshot_2023-03-22_at_9.28.55_AM.png](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/13884124619675.png) ![Screenshot_2023-03-22_at_9.30.44_AM.png](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/13884100341403.png) ### Running Red Hat Open Data Service on Satellite with a Wasabi data connection ![Screenshot_2023-03-22_at_9.25.40_AM.png](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/13883948056859.png) ![Screenshot_2023-03-22_at_9.27.07_AM.png](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/13883995057819.png) ## Satellite Storage Templates For workloads that depend on mounted filesystems that utilize object storage in the backend, you can use the IBM Object Storage plugin to define the Wasabi endpoints and bucket(s) to be mounted. Within the context of Satellite, there is a Satellite Storage Template to ease the use of the IBM Object Storage plugin. With Satellite storage templates, you can create a storage configuration that can be deployed across your clusters without the need to re-create the configuration for each cluster. To learn more about the Satellite Storage Templates, review [How do templates work?](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-template-ov&interface=cli#storage-template-flow) To create a Satellite Storage Template: 1. Log in to your IBM Cloud account and click the **Dashboard** icon. ![Screenshot_2023-03-20_at_9.01.43_PM.png](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/13840729506971.png) 2. Click **Satellite**, then click **Overview**. ![Screenshot_2023-03-20_at_9.03.46_PM.png](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/13840772284315.png) 3. On the Satellite Overview page, click **Locations**. ![Screenshot_2023-03-20_at_9.05.12_PM.png](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/13840818988571.png) 4. On the Locations page, select the desired location. ![Screenshot](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/16666398400923.png) 5. On the Location Configuration page, click **Storage**. Click **Create storage configuration**. ![Screenshot_2023-03-20_at_9.12.54_PM.png](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/13840929474715.png) 6. In the Basics section, provide a name for the configuration. Select **IBM Object Storage Plugin** as the Storage type in the drop-down. Click **Next**. ![Screenshot_2023-03-20_at_9.15.26_PM.png](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/13840977239195.png) 7. In the Parameters section, change the COS plugin license field to "true" to accept the Apache open-source license terms. Select Wasabi as the Object Storage Provider. ![Screenshot](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/16666519758619.png) 8. Provide the desired region in the Object Storage region and click **Next**. ![Screenshot](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/16666559068571.png) ** This configuration example discusses the use of Wasabi's us-east-2 storage region. Provide the appropriate region for your configuration. 9. Click through to the Assignment tab and assign the storage template to the desired clusters. 10. The result will be the creation of storage classes within the assigned OpenShift clusters (which are running in our location in this example). 11. In the cluster(s), you also need to create a Kubernetes Secret with the associated Wasabi access credentials. We need to create a secret with two key-value pairs: `access-key` and `secret-key`, which contain the respective Wasabi credentials for the account to use. 12. Log into the OpenShift cluster running on the location by clicking on **Services**. ![Screenshot_2023-03-20_at_9.30.38_PM.png](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/13841159812507.png) 13. To log into the OpenShift web UI, click **OpenShift web console**. ![Screenshot_2023-03-20_at_9.31.58_PM.png](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/13841197535643.png) 14. In the OpenShift console, navigate to **Storage**, then to **StorageClasses** on the left-hand pane. ** These storageclassses are created by Satellite. We created a storage template for this location. ![Screenshot_2023-03-20_at_9.37.47_PM.png](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/13841258845595.png) 15. Navigate to **Workloads,** then to **Secrets**. Expand the Create drop-down and select **Key/value secret**. ![Screenshot_2023-03-21_at_10.25.42_AM.png](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/13852658563355.png) 16. On the Create key/value secret page, provide a name for the secret in the Secret name field. 17. In the Key field, enter the term "access-key". In the Value field, enter the access key of your Wasabi account. 18. Click **Add key/value** to add the secret key. ![Screenshot_2023-03-21_at_10.52.38_AM.png](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/13853557108891.png) 19. In the Key field, enter the term "secret-key". In the Value field, enter the secret key of your Wasabi account. Click **Create**. ![Screenshot_2023-03-21_at_10.55.03_AM.png](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/13853637534107.png) We now have a secret created for our OpenShift cluster. Below is a prototypical PVC for a workload that wants to mount an S3 bucket into the filesystem: ```plaintext kind: PersistentVolumeClaim apiVersion: v1 metadata:   name: s3fs-test-pvc   namespace: wasabi-test   annotations:     volume.beta.kubernetes.io/storage-class: "ibmc-s3fs-cos"     ibm.io/auto-create-bucket: "true"     ibm.io/auto-delete-bucket: "false"     ibm.io/bucket: "davet-test-011"     ibm.io/object-path: ""    # Bucket's sub-directory to be mounted (OPTIONAL)     ibm.io/endpoint: https://s3.wasabisys.com     ibm.io/region: "us-east-1"     ibm.io/secret-name: "wasabi-cos"     ibm.io/stat-cache-expire-seconds: ""   # stat-cache-expire time in seconds; default is no expire spec:   accessModes:     - ReadWriteOnce   resources:     requests:       storage: 1Gi # fictitious value ``` Below is an example pod specification that would use that PVC: ```plaintext apiVersion: v1 kind: Pod metadata:   name: s3fs-test-pod   namespace: wasabi-test spec:   containers:   - name: s3fs-test-container     image: anaudiyal/infinite-loop     volumeMounts:     - mountPath: "/mnt/s3fs"       name: s3fs-test-volume   volumes:   - name: s3fs-test-volume     persistentVolumeClaim:       claimName: s3fs-test-pvc ``` In this example, the bucket `davet-test-011` in Wasabi is mapped to `/mnt/s3fs` (or, whatever path is specified). You can verify the filesystem mounting by inspecting the pod. ```plaintext $ kubectl exec -it s3fs-test-pod -n  bash root@s3fs-test-pod:/# root@s3fs-test-pod:/# df -Th | grep s3 s3fs fuse.s3fs 256T 0 256T 0% /mnt/s3fs root@s3fs-test-pod:/# cd /mnt/s3fs/ root@s3fs-test-pod:/mnt/s3fs# ls root@s3fs-test-pod:/mnt/s3fs# root@s3fs-test-pod:/mnt/s3fs# echo "Sateliite and Wasabi integration" > sample.txt root@s3fs-test-pod:/mnt/s3fs# ls sample.txt root@s3fs-test-pod:/mnt/s3fs# cat sample.txt Sateliite and Wasabi integration root@s3fs-test-pod:/mnt/s3fs# ```