Selvam, For debugging purposes, I would highly recommend trying to use the AWS CLI to get the file onto whatever machine you are using. It is possible that there could be problems with the bucket policy, permissions, or even just some networking stuff blocking the file from coming through. This would stop the file from coming as it can’t travel the path to get to wherever you want it.
Best, Keren From: James Wing <[email protected]> Reply-To: "[email protected]" <[email protected]> Date: Thursday, October 6, 2016 at 12:43 PM To: "[email protected]" <[email protected]> Subject: Re: Fetchs3Object Selvam, Can you describe what is happening when you run FetchS3Object? Does the processor start? Are flowfiles routed to the failure relationship? Are there error messages? To test your configuration, I recommend using ListS3 to get flowfiles with attributes referencing the S3 objects, then use FetchS3Object with the following settings: Bucket: ${s3.bucket} Object Key: ${filename} Region: us-east-1 This might help sort out problems with permissions vs. processor configuration. Thanks, James On Thu, Oct 6, 2016 at 8:07 AM, Selvam Raman <[email protected]<mailto:[email protected]>> wrote: Hi, how can i access fetchs3 object from NIFI. what all are the parameters do i need to give. Can you please give me example as well if possible. i tried to using secret and access key, default provider. Nothing is working. -- Selvam Raman "லஞ்சம் தவிர்த்து நெஞ்சம் நிமிர்த்து" ________________________________________________________ The information contained in this e-mail is confidential and/or proprietary to Capital One and/or its affiliates and may only be used solely in performance of work or services for Capital One. The information transmitted herewith is intended only for use by the individual or entity to which it is addressed. If the reader of this message is not the intended recipient, you are hereby notified that any review, retransmission, dissemination, distribution, copying or other use of, or taking of any action in reliance upon this information is strictly prohibited. If you have received this communication in error, please contact the sender and delete the material from your computer.
