Configuring a repository to ingest customer data
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.
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 . 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:
Previous topic Configuring the data ingestion process Next topic Configuring a file listener to ingest customer data