File Listener setup on AWS S3 bucket is failing to start
We have set up file listener to poll a AWS S3 bucket as defined in below article. The connectivity test from listener rule was success but not able to start the listener instance. Is there any other configuration we are missing here?
A sanity check: have you actually confirmed that an independent AWS S3 client (either simple java code or an AWS client plugin for eclipse) can create work directory using the same IAM user? If yes, then we need to investigate further within Pega (btw, what is your Pega version?). Otherwise, it is a generic AWS S3 bucket setup issue.
Kevin - thank you for your response. We are on Pega 8.3.1. Creating folder from AWS CLI works fine but haven't tried from any third party S3 client as we have a security requirement to seek S3 object permissions from attached IAM role of EC2.
Also on another note, lets say we have to store files on S3, I understand that standard way to set it up is to configure Repository rule and add authentication profile with secret id/ access key. But again, as we have enterprise security requirement to not rely on programmatic IAM user, is there a way Pega can assume attached IAM role of EC2 to connect to S3?