Question

4
Replies
323
Views
Venkat Raman Kuntamukkala (VenkatK9)
Anthem

Anthem
US
VenkatK9 Member since 2013 2 posts
Anthem
Posted: January 9, 2020
Last activity: January 9, 2020
Posted: 9 Jan 2020 13:06 EST
Last activity: 9 Jan 2020 16:21 EST
Closed

File Listener setup on AWS S3 bucket is failing to start

Hi,


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?


https://community.pega.com/knowledgebase/articles/data-integration/configure-file-listener-associated-storage-destination


We ensured read/write/delete policies setup for IAM role attached to EC2. PegaRULES logs says as below.


2020-01-09 15:56:28,173 [ FILE-Thread-65] [ STANDARD] [ ] [ ] ( aws.s3.FileS3Adapter) INFO

File.FileListnerName|initialize - s3 meta data doesn't exist for container: dev-S3bucket and directory: dev-S3bucket/work_FileListnerName/

com.amazonaws.services.s3.model.AmazonS3Exception: Not Found (Service: Amazon S3; Status Code: 404; Error Code: 404 Not Found; Request ID: 555F75D2D0F072F0; S3 Extended Request ID:

u4dArFTaXPggBGbYuBvffbM8aTSu7CukhfkoSH9VWw929EhBfrz8D4uhJanNvioSKPr9jUQ2iqg=)

Hi,

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?

https://community.pega.com/knowledgebase/articles/data-integration/configure-file-listener-associated-storage-destination

We ensured read/write/delete policies setup for IAM role attached to EC2. PegaRULES logs says as below.

2020-01-09 15:56:28,173 [ FILE-Thread-65] [ STANDARD] [ ] [ ] ( aws.s3.FileS3Adapter) INFO
File.FileListnerName|initialize - s3 meta data doesn't exist for container: dev-S3bucket and directory: dev-S3bucket/work_FileListnerName/
com.amazonaws.services.s3.model.AmazonS3Exception: Not Found (Service: Amazon S3; Status Code: 404; Error Code: 404 Not Found; Request ID: 555F75D2D0F072F0; S3 Extended Request ID:
u4dArFTaXPggBGbYuBvffbM8aTSu7CukhfkoSH9VWw929EhBfrz8D4uhJanNvioSKPr9jUQ2iqg=)

2020-01-09 15:56:28,199 [ FILE-Thread-65] [ STANDARD] [ ] [ ] ( services.file.FileListener) ERROR File.ProcessManualStandaloneCAGFeed -
Unexpected exception caught during processing.
com.pega.pegarules.pub.PRException: Unable to create 'work' directory 'file://app-s3-alias:/dev-S3bucket/work_FileListenerName'.
at com.pega.pegarules.integration.engine.internal.services.file.FileActionImpl.initialize(FileActionImpl.java:194) ~[printegrint.jar:?]
at com.pega.pegarules.integration.engine.internal.services.file.FileActionImpl.<init>(FileActionImpl.java:128) ~[printegrint.jar:?]
at com.pega.pegarules.integration.engine.internal.services.file.FileListener.run_(FileListener.java:441) ~[printegrint.jar:?]
at com.pega.pegarules.integration.engine.internal.services.listener.ServiceListenerBaseImpl.run(ServiceListenerBaseImpl.java:455) ~[printegrint.jar:?]
at java.lang.Thread.run(Thread.java:748) [?:1.8.0_221]

Cloud Services Data Integration System Administration
Moderation Team has archived post, This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.