Using S3 compatible storage as repository

We have a requirement to put all case attachments in S3 compatible storage. OOTB pega supports Amazon S3 repository where there is no option to provide endpoint or region but S3 compatible storage are private clouds and have an endpoint URL where it is hoisted. Fundamentally both are same.

Is there any extension point or tweak we can do to use OOTB amazon S3 repository for S3 compatible storage?


Keep up to date on this post and subscribe to comments

September 29, 2019 - 9:57pm

Hi Abikash,

When you configure S3 repository you have the option to provide the location of the root folder on S3..

So for your private cloud you can mount the S3 folder to a folder in your application server location and then provide this location path as repository path.



September 30, 2019 - 7:30am
Response to Vikash Karn

Hello Vikash,

We mounted the S3 compatible storage to a drive( say A). Our bucket name was CMFFW. So, we provided A:\CMFFW in the "root path" but it is always throwing "The specified folder exists, but you have Insufficient permissions to read from it". We checked all the persmissions, there is no issue with it.

We are able to create repositry type "File System" and able to make it work when you upload attachment. But in this way if you have multi node enviornment then you need to mount it to each node. What is your view?

BR, Manish Kumar

September 30, 2019 - 9:35pm
Response to MKUMAR18

Yes for multinode environment you will have to mount the storage location in all the nodes to the same path in the server.

So all the nodes will be in sync with respect to the storage path. So it doesn't matter the file is being attached from what node it will be send to the same storage path.

October 1, 2019 - 10:53am
Response to Vikash Karn

Thank you for reply as I said when I mount the storage location it work as Repository type "File system". 

But when we are trying as Repository type "S3". It did not work, even when I specify root path. Any view on it?

Why I am more looking on Repository type "S3" as you have option of "Server side data encryption with KMS managed keys" and this is not there in case of "File system" as Repository.

October 2, 2019 - 7:41am
Response to MKUMAR18

You probably need to develop a custom repository type as described in this link - using Pega repository APIs: