Were you able to resolve this? I think James is right about the Bucket vs Region relationship, AWS Signature Version 4 has less tolerance for bucket/region mismatches. (See this comment <https://github.com/aws/aws-sdk-java/blob/1.10.32/aws-java-sdk-s3/src/main/java/com/amazonaws/services/s3/AmazonS3Client.java#L518> in the AmazonS3Client source for more detail.)
If that's not it, AWS has a page on signature troubleshooting <http://docs.aws.amazon.com/general/latest/gr/signature-v4-troubleshooting.html#signature-v4-troubleshooting-key-signing> . Regards, Joe On Wed, Jul 20, 2016 at 6:15 PM, James Wing <[email protected]> wrote: > ListS3 processor is a great place to start. I can think of a couple of > likely causes: > > * Credentials - you might want to double-check how you specified the > credentials to make sure it is right. If you specify access key and secret > key, and the secret key is not correct, I believe you will get this error. > > * Region - you should make sure the region you specify in the processors > matches the S3 bucket's region. S3 is a bit weird about the rules for > buckets and regions, but it might help to check. > > Thanks, > > James > > On Wed, Jul 20, 2016 at 12:57 PM, Nabegh <[email protected]> wrote: > > > Hi James, > > > > I'm using nifi-0.7.0-RC2. I tried ListS3 processor and I received the > same > > error. > > > > Thanks > > > > > > > > -- > > View this message in context: > > > http://apache-nifi-developer-list.39713.n7.nabble.com/PutS3Object-error-tp12878p12880.html > > Sent from the Apache NiFi Developer List mailing list archive at > > Nabble.com. > > >
