IBM COS Binary Storage
Cloud CMS supports IBM Cloud Object Storage (COS) by allowing it to serve as a backend provider for the storage of binary files within Cloud CMS.
When files are uploaded to Cloud CMS, they are parsed and worked with and then eventually sent over to IBM COS for persistence. When users seek to download those binary files, they are streamed back from IBM COS.
Depending on how you elect to configure your binary storage providers, Cloud CMS may employ an TTL cache in between to avoid going back to the binary storage provider on repeated invocations.
Adjusting the Binary Storage Provider used by Cloud CMS is a system-wide change and will therefore require that you run Cloud CMS on-premise. SaaS subscribers do not have the ability to adjust the Binary Storage provider.
For information on how to adjust the Binary Storage Provider within an On-Premise or Docker installation, please see our documentation on Configuring the IBM Cloud Object Storage Provider.