Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Unable to connect to S3 bucket using proxy configuration



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

  1. Create a new Repository rule.
  2. Fill the required details for the Amazon S3 repository type.
  3. 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.


Perform the following local-change:

Use HTTPS proxy instead of HTTP proxy as the JVM argument.


Published January 5, 2019 - Updated December 2, 2021

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration 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.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us