S3putobject credential file vs access key secret key

[#1]

I want to use the credential file in s3putfile so i don’t have to put access key and security key in the processor. However, when provide the path to my credentials file, NiFi complains the access key and security key are null. Isn’t that the entire point to have crendentials in a file instead of residing inside the processor. Feedback/help appreciated.

[#2 · Accepted solution]

@sunile.manjee

-

Does the content of your credentials file look like the following:

[default]
aws_access_key_id=<access key>
aws_secret_access_key=<security key>

-

Make sure this credentials file is readable by the NiFi service user.

-

Thank you,

Matt

[#3]

@Matt Clarke my properties file is owned by nifi user

and the content is exactly as you posted but with my creds. However, on nifi it does not like the access key and secret key is empty

and here is the properties in the processor:

Again the creds are in the Credentials File so why it is asking me to input access key and secret key? those exists in credentials file.

[#4]

@sunile.manjee

-

I was playing around with PutS3Object and do not see same issue.

Your configuration screen putS3Object processor configuration above shows values being set for both "Access Key' and 'Secret Key'.

Only way I can reproduce what you see is if you checked the box "Set Empty String" for the 'Access Key' and 'Secret Key'. The empty string is being treaded like a null value and process validates that as being configured (that is why it shows "Sensitive value set").

-

What you want to do is select field and hit your delete key to clear it out rather then checking the box. The "Access Key' and 'Secret Key' fields should show "No Value Set" instead. At that point your processor should validate correctly.

-

Thanks,

Matt

[#5]

@sunile.manjee

I updated my last response, let me know if this resolves your issue.

[#6]

@Matt Clarke your suggestion worked. I also found the properties the processor expect is slightly different

[default]
accessKey=<access key>
secretKey=<security key>

[#7]

@sunile.manjee

Good catch. Thank you for sharing.