nifi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From James Wing <>
Subject Re: Nifi Debugging AWS PutS3 processor
Date Fri, 09 Sep 2016 20:39:08 GMT
I'm sorry to hear you're having trouble with PutS3.  A few questions:

   - Which version of NiFi are you using?
   - Have you configured the Proxy Host/Port or Endpoint Override URL
   settings on your PutS3 processor?
   - Are there larger exception stack traces in the nifi-app.log files you
   can share?
   - Some of the errors mention Multi-part Upload.  Are large flowfiles
   failing, but smaller files successful?
   - The errors in the screenshot reflect two IP addresses, but it may just
   be a small sample.  Are the errors evenly distributed across all the
   cluster nodes?



On Fri, Sep 9, 2016 at 11:19 AM, jmurakami <>

> Hi. I am currently using the putS3 processor and getting an
> AmazonClientException error: Connection Timed Out. We are running the flow
> on a Nifi cluster (of 3 instances and a cluster manager). We see the error
> attached below and about a third of the data not being put into the bucket.
> We were able to use the aws cli in an instance in our Nifi cluster and
> successfully put data into our S3 bucket, so the security groups, Nacl,
> subnets, and bucket policies should be okay. I don't believe it is a
> credential or key error since some of the data was put into the bucket
> already. We are using IAM roles to allow access to the S3 bucket.
> Has anyone else encountered this error?
> <
> n13311/Screen_Shot_2016-09-06_at_10.png>
> Or any advice about how to go about this error would help. Thanks!
> --
> View this message in context: http://apache-nifi-developer-
> Sent from the Apache NiFi Developer List mailing list archive at

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message