Question
File storage in Pega 7.4- Can I edit path for pegacloudcustomerroot variable.
Hi,
We are running on Pega 7.4 version in PegaCloud. In file storage tab I have variable called pegacloudcustomerroot with the location to Amazon S3 bucket.
Questions:
1. Can I change value of that parameter? I am not able to find it in DSS. Our goal is to have access from two development environments to one shared locations on Amazon S3.
2. If there is no possibility to change that parameter, do I have any other options to create another file storage with different locations. If so, how to do this?
Thank you in advance.
Jakub
***Edited by Moderator Marissa to update platform capability tags***
Accepted Solution
Hi Jakub
The variable pegacloudcustomerroot is for internal use only and cannot be modified.
To help customers with file storage Pega provides Pega Cloud File Storage. For each environment it provides cloud file storage that is pre-configured, secure and isolated. This storage is intentionally isolated per environment in order to prevent interference across environments (e.g., dev systems cannot corrupt or access production).
With Pega 7.4 the concept of repositories was added so you can easily access Pega Cloud File Storage and a variety of 3rd party file stores (e.g., private AWS S3 bucket, Sharepoint, Box.com). The pegacloudfilestorage repository is pre-configured by default. You can easily add repositories for 3rd party file stores.
We currently do not allow multiple environments to access the same folder in Pega Cloud File Storage (for data security reasons). However, you can configure a repository in two environments that points to the same 3rd party file store (e.g., private AWS S3 bucket, Sharepoint or Box.com). This will allow you to share files/folder between environments.
Useful articles:
https://community.pega.com/knowledgebase/articles/pega-cloud-file-storage
Charlie Nuzzolo
Product Manager, Cloud Engineering
Hi,
As per my view, providing a DSS for shareable may not be practical. Dynamic storage location change may cause exposing entire filesystem.
I would suggest creating Cloud Ticket to get some help/inputs on this. If it's needed, it may be changeable by Cloud teams.
~N