Posted: 3 Jun 2019 8:04 EDT Last activity: 5 Sep 2019 11:52 EDT
Amazon S3 Repository rule error - Could not connect to repository
I've been trying to setup an Amazon S3 repository and keep getting an error.
The S3 bucket policy is set to public, to allow all operations for testing. (s3_bucket_policy.txt)
The S3 bucket can be accessed just fine with other tools, such as Postman, using the same Access key ID.
When I try to create a Repository rule in Pega, I get a "Could not connect to repository" error on the rule form and it does not get saved. (repository_rule.jpg)
When I trace the save operation, I can see that Data-Repository.Validate fails. (tracer.jpg, tracer_error.jpg)
I've set all relevant loggers to ALL, and all I can see in logs (pega_log.txt), the most specific error message is:
We're facing the same issue as PeterB46... We've exhausted all possible solutions that we could think of from a Pega, AWS perspective and furthermore from a firewall and application server perspective. There's not enough documentation on this and the information on Pega Community is a bit lacking. We've even added a KMS Key and we're still not able to connect the repository and create the rule.
This also happened to me as well, and I actually opened a ticket with support for it to no avail. I also verified that the bucket is available through other tools and from the command line of the server where our Pega application lives.
I would be very interested to hear if you obtain a solution for this issue.
Just include the bucket name (without region - just the <Bucket Name>). Remove the rest of the url. See if KMS id needs to be given as input. I had given region and all initially when I received the error. The I just included bucket name and worked fine. Attached screenshot