Support Article
Unable to connect to S3 bucket using proxy configuration
SA-69615
Summary
The requirement is to connect Amazon S3 buckets using a proxy configuration that is set as a JVM argument. However, this causes all the connections to pass through the proxy. The proxy configuration must be set only for Amazon S3 connections.
Error Messages
Couldn't connect to repository
Steps to Reproduce
- Create a new Repository rule.
- Fill the required details for the Amazon S3 repository type.
- Save or Test connectivity. Error displays on the screen and connection does not succeed.
Root Cause
Cannot connect to Amazon S3 bucket from Pega through the proxy because the functionality is not present.
Resolution
Perform the following local-change:
Use HTTPS proxy instead of HTTP proxy as the JVM argument.
Published January 5, 2019 - Updated December 2, 2021
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.