Chakri, Can you check that your system's date/time is accurate? I have not tried this with S3, but I know that Twitter sends back a pretty similar response when we use GetTwitter on a node that has the wrong date/time. It has to do with the authentication protocol that is used requiring an accurate timestamp.
Please advise if your system date/time is correct. Thanks -Mark > On Oct 7, 2015, at 8:29 PM, Chakrader Dewaragatla > <[email protected]> wrote: > > Any one notice Nifi S3 processor broken with latest java version ? > (java-1.8.0-openjdk-1.8.0.60-14.b27) > S3 put error: > > 2015-10-08 00:28:30,745 ERROR [Timer-Driven Process Thread-6] > o.a.nifi.processors.aws.s3.PutS3Object > PutS3Object[id=1c0f0c5c-cbb9-4ed9-891c-0bd48ae69366] Failed to put > StandardFlowFileRecord[uuid=4a2455b1-d47f-4d6e-9847-a93a5e66d7a5,claim=StandardContentClaim > [resourceClaim=StandardResourceClaim[id=1444264110525-192, > container=default, section=192], offset=0, > length=10000000],offset=0,name=c2.txt,size=10000000] to Amazon S3 due to > com.amazonaws.services.s3.model.AmazonS3Exception: AWS authentication > requires a valid Date or x-amz-date header (Service: Amazon S3; Status Code: > 403; Error Code: AccessDenied; Request ID: 254510F6EE5E85B5), S3 Extended > Request ID: > +Q5lfeKce1HMGUjw9BCp8lg8wmIy/eIHKH62xsWteJzKmqbsWRSeGLo4p8h6R1BLd5KIFXjKOO4=: > com.amazonaws.services.s3.model.AmazonS3Exception: AWS authentication > requires a valid Date or x-amz-date header (Service: Amazon S3; Status Code: > 403; Error Code: AccessDenied; Request ID: 254510F6EE5E85B5), S3 Extended > Request ID: > +Q5lfeKce1HMGUjw9BCp8lg8wmIy/eIHKH62xsWteJzKmqbsWRSeGLo4p8h6R1BLd5KIFXjKOO4= > > > It works on other node with java version (java-1.8.0-openjdk-1.8.0.45-40.b14). > > Thanks, > -Chakri > > > > The information contained in this transmission may contain privileged and > confidential information. It is intended only for the use of the person(s) > named above. If you are not the intended recipient, you are hereby notified > that any review, dissemination, distribution or duplication of this > communication is strictly prohibited. If you are not the intended recipient, > please contact the sender by reply email and destroy all copies of the > original message.
