Seeking Workaround for Custom S3 Endpoint in Pega 8.7 and below

General
1

Hi everyone,

We are currently working on a requirement to connect Pega to an internal S3-compatible storage (MinIO) rather than the public Amazon AWS cloud.

We noticed that in Pega 8.6 and 8.7, the ‘Service Endpoint’ field is missing from the Repository UI, whereas in newer versions like Pega '24, this field is readily available. Since we are operating on 8.7 and below, the system seems to default all requests to the public AWS URL.

Has anyone successfully implemented a custom S3 endpoint in Pega 8.7 or below?

2

Hello Yudhi,

Its likely that you will need a custom repository implementation, if OOTB repository doesnt have needed config. In your case, you can extend the existing S3 logic as its all already there. Refer the below documentation.