Question

Amazon S3 Connectivity through PEGA

Hi Team,

We have business requirement to store Work item attachment to Amazon S3 bucket. To do this, we wanted to configure Amazon S3 as repository rule and enable them in Application rule so that PEGA by default store all work item attachment to Amazon S3 bucket instead of Pega DB.

While creating repository rule we are facing connectivity issue. We have given following parameters for repository rule but, at the time of saving the rule, connectivity fail exception is reported.

Bucket name <ValidBucket Name>

Authentication Profile with Access Key and Secrete Key- It is verified these detail are correct.

Root path - http://s3.amazonaws.com/<bucketName> and http://s3-<regionName>.amazonaws.com/<bucketName>

While saving this rule we connection error.

Later business suggest us to use Proxy and then try. We set Proxy as described in below two posts. we tried prconfig configuration caused login failure, with JVM parameters, no issue appearantly but connection was still failing.

prconfi setting for proxy-

https://community.pega.com/knowledgebase/articles/reverse-proxy-server-configuration

JVM setting for proxy

https://docs.oracle.com/javase/8/docs/technotes/guides/net/proxies.html

Any idea how to resolve this issue. Please find attached log file for error detail.

Error in log file during connectivity -

018-11-16 04:44:02,835 [ttp-nio-8984-exec-23] [TABTHREAD1] [ ] [ DMTApp:01.01.01] ( aws.s3.S3Factory) ERROR dmt-dev.corp.rno.apple.com|10.202.79.101 2304623688 - Unexpected exception attempting to connect to S3 bucket apple-sfo-uat at root path `http://s3.amazonaws.com/apple-sfo-uat'

com.amazonaws.SdkClientException: Unable to execute HTTP request: Connect to apple-sfo-uat.s3.amazonaws.com:443 [apple-sfo-uat.s3.amazonaws.com/52.216.132.187] failed: connect timed out

at com.amazonaws.http.AmazonHttpClient$RequestExecutor.handleRetryableException(AmazonHttpClient.java:1069) ~[aws-java-sdk-core-1.11.155.jar:?]

at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeHelper(AmazonHttpClient.java:1035) ~[aws-java-sdk-core-1.11.155.jar:?]

at com.amazonaws.http.AmazonHttpClient$RequestExecutor.doExecute(AmazonHttpClient.java:742) ~[aws-java-sdk-core-1.11.155.jar:?]

***Moderator Edit-Vidyaranjan: Updated SR details***

Group Tags

Correct Answer
December 31, 2018 - 2:13pm

Upon reviewing the associated SR, I see that the resolution was as follows:

"HTTPS proxy instead of HTTP proxy as JVM argument to resolve the issue"

Comments

Keep up to date on this post and subscribe to comments

December 31, 2018 - 2:13pm

Upon reviewing the associated SR, I see that the resolution was as follows:

"HTTPS proxy instead of HTTP proxy as JVM argument to resolve the issue"

Marissa | Community Moderator | Pegasystems Inc.