Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Configuring a repository to ingest customer data

Updated on August 3, 2022

This content applies only to Pega Cloud environments

In a Pega Cloud implementation, you provide to the Pega Cloud services team, such information as SFTP DNS, credentials, the use of public certificates of your organization, and the path where the data is to be uploaded.

Pega Customer Decision Hub Implementation Guide

The Pega Cloud services team defines the S3 file repository in advance and preloads it in the File Storage landing page. To access the landing page, in the header of Dev Studio, click ConfigureSystemSettingFile Storage. The S3 file repository location is shared with your SFTP configuration team, who must configure their SFTP application to point to this location as the root directory for file destination paths.


If you use SFTP for other clouds, you need to manually create a repository. For instructions, see Creating a repository.

If your environment is not in Pega Cloud and the repository is to be shared across environments, you must manually update the root path to identify the environment. For example, if the same repository is to be shared by the development and QA environments:

  • Create folders named Dev and QA in the SFTP root folder.
  • Update the root path in the repository rule.

The following figure shows how a Dev folder is defined as the root path for the Dev repository in the QA environment for non-Pega Cloud implementations:

Sample repository configuration with a root path configured to Dev folder
Repository configuration window in Dev Studio with the Root path field set to Dev

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us