Nandor's answer is correct. However MSK IAM is not the only possible authentication option and there are options (mTLS, SASL/SCRAM) where this specific bundle build is not required.
Le mar. 4 juil. 2023 à 11:26, Nandor Soma Abonyi <[email protected]> a écrit : > Hi, > > Actually, there is a little bit of secret. The library that supports iam > authentication for an msk cluster is not part of the default bundle. You > need to build NiFi from source with `include-kafka-aws` maven profile > enabled. Then if NiFi runs in an EC2 instance and IAM roles are correctly > set, no configuration will be required on the NiFi side. For advanced > configuration, for example, when NiFi runs outside of AWS, I recommend > studying the default credential chain (link > <https://docs.aws.amazon.com/sdk-for-java/v1/developer-guide/credentials.html>), > which the library also uses. > > Nandor > > On 2023. Jul 4., at 10:53, Pierre Villard <[email protected]> > wrote: > > No specific secret. It should be fairly straightforward. > How is your MSK configured (wrt authentication)? How are you configuring > your Kafka processors? and if you get errors, what are those? > > Pierre > > Le mar. 4 juil. 2023 à 00:47, David Grootwassink <[email protected]> > a écrit : > What is the secret to connecting NiFi Kafka processors to the AWS Managed > Kafka service? > > Thanks > > >
