I get an error when using client side encryption with Customer Master Key (in PutS3Object in NiFi 1.10.0).
Processor works perfectly when encryption is not used.
The examplary AES key that I use is randomly generated: 6XtOQkXcvELfF5224T8mricDrSEeFh3rR1CEE4qBTIo=
PutS3Object[id=3b697bed-016e-1000-7492-a2311ff00e42] Failed to put StandardFlowFileRecord[uuid=432a81c7-3879-4474-af23-11e202aa385b,claim=StandardContentClaim [resourceClaim=StandardResourceClaim[id=1572954920976-1, container=default, section=1], offset=969, length=17],offset=0,name=test.json,size=17] to Amazon S3 due to Unable to execute HTTP request: Connect to xxx.s3.eu-west-1.amazonaws.com:443 [xxx.s3.eu-west-1.amazonaws.com/xx.xxx.xx.xxx] failed: connect timed out: com.amazonaws.SdkClientException: Unable to execute HTTP request: Connect to xxx.s3.eu-west-1.amazonaws.com:443 [xxx.s3.eu-west-1.amazonaws.com/xx.xxx.xx.xxx] failed: connect timed out
Does anyone knows how to handle that?
... View more
Hi, I have a simple task that is not so obvious when trying to get things done. I have to encrypt flowfiles with SHA256_256AES before puting in on S3 bucket and later decrypt it with Snowflake.
When using SHA256_256AES I need to provide password and optionally Raw Key (hexadecimal) and Snowflake requires 128,192 or 256 bits key.
My question is: is NiFi generating key itself when none is provided? Or do I have to generate key myself somehow? Below I attach processor configuration.
The key specified in query is exemplary to show accepted length.
... View more