Re: How to access to an Amazon API?

2021-06-15 Thread Otto Fowler
That error means that we passed info into AWS api ( asked the region to find the resource ) and it said nope, and tried to guess. I would have to try to setup the processor with your configuration ( enough to try to parse, ok if it fails later because of cred or whatever ). > On Jun 15, 2021,

Regarding jira issue: NIFI-7856

2021-06-15 Thread sanjeet rath
Hi, The symptoms mentioned in the jira issue( *https://issues.apache.org/jira/browse/NIFI-7856 *), i am observing this in one of our PROD clusters. ERROR [Compress Provenance Logs-1-thread-2] o.a.n.p.s.EventFileCompressor Failed to compress

R: How to access to an Amazon API?

2021-06-15 Thread Luca Giovannini
Thank you Otto, I can confirm that the resource API is correct: I tested it successfully with Postman by doing a GET on the request URL (https://zsslnu1awf.execute-api.eu-west-1.amazonaws.com/prod/test) and providing AccessKey, SecretKey and AWS Region in the "Authorization" tab of the

Re: Using a corporate SSL signed certificate

2021-06-15 Thread Jens M. Kofoed
Hi Emmanuel I don't use the toolkit, I just do it manually. I have found that a normal server certificate, generated i Microsoft Windows is not working. The certificate for NiFi servers has to be both serverAuth and clientAuth. So I have created a new certificate profil in our PKI server for NiFi