Re: Modifying putElasticSearchHTTP processor to use AWS IAM role based awscredentialprovide service for access

2020-09-09 Thread sanjeet rath
Thank you MIke for the quick reply. I was really struggling with this functionality. i have gone through the code ,what i understood is i should use the "nifi-elastic-search-restapi-processor" project. In it the JsonQueryelasticSearch processor, it uses the "Client Service" Controller service.

Re: Modifying putElasticSearchHTTP processor to use AWS IAM role based awscredentialprovide service for access

2020-09-09 Thread Mike Thomsen
Sanjeet, As provided, this won't integrate well with the existing NiFi processors. You would need to implement it as a controller service object and update the processors to use it. Also, if you want to use processors based on the official Elasticsearch client API, the ones under the "REST API

Modifying putElasticSearchHTTP processor to use AWS IAM role based awscredentialprovide service for access

2020-09-09 Thread sanjeet rath
Hi , We are using *AWS managed ElasticSearch* and our *nifi is hosted in EC2*. I have a use case of building a custom processor on top of putElasticSearchHTTP, where it will use aws IAM based role awscredentialprovider service to connect AWS ElasticSearch. This will be similar to PUTSQS where we