You might try capturing flow logs for your VPC. It can be a bit tedious, but it might confirm which connections to S3 are successful and which are blocked by your network configuration, if any. I must admit to being puzzled by the intermittent nature of the problem.
https://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/flow-logs.html On Mon, Sep 12, 2016 at 8:29 AM, Joe Skora <jsk...@gmail.com> wrote: > Julie, > > If some traffic gets through and some times out, it sounds like a network > problem. > > I would check the system memory/load and network load, either can cause > network response and timeout problems. > > JoeS > > On Mon, Sep 12, 2016 at 8:44 AM, jmurakami <julie.murak...@capitalone.com> > wrote: > > > Good morning, > > > > After changing the endpoint override property, I still have some requests > > of > > the PutS3 processor failing with the same error Connection Timed Out. The > > errors are coming from all three of the instances running Nifi in our > > cluster. > > > > I was also wondering what the Communications Timeout property does. I had > > changed it and noticed the number of requests that were failing dropped, > > however there were still a tenth of requests failing. > > > > Thanks, > > Julie > > > > > > > > -- > > View this message in context: http://apache-nifi-developer- > > list.39713.n7.nabble.com/Nifi-Debugging-AWS-PutS3-processor- > > tp13311p13338.html > > Sent from the Apache NiFi Developer List mailing list archive at > > Nabble.com. > > >
