Based on the initial input in the question, slightly adapted the following seems to work for me (1.27.0) docker run --rm --name nifi -p 8080:8080 \ -e NIFI_WEB_HTTP_PORT=8080 \ -e NIFI_WEB_HTTPS_PORT= \ -e NIFI_WEB_HTTPS_HOST= \ -e NIFI_SECURITY_KEYSTORE= \ -e NIFI_SECURITY_KEYSTOREPASSWD= \ -e NIFI_SECURITY_KEYPASSWD= \ -e NIFI_SECURITY_TRUSTSTORE= \ -e NIFI_SECURITY_TRUSTSTOREPASSWD= \ apache/nifi:1.27.0 --- --- from container nifi@xxxxxxxxxxxx:/opt/nifi/nifi-toolkit-current/bin$ ./cli.sh _ ___ _ Apache (_) .' ..](_) , _ .--. __ _| |_ __ )\ [ `.-. | [ |'-| |-'[ | / \ | | | | | | | | | | ' ' [___||__][___][___] [___]', ,' `' CLI v1.27.0 Type 'help' to see a list of available commands, use tab to auto-complete. Session loaded from /home/nifi/.nifi-cli.config #> nifi get-root-id xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx ... View more

Accept the answer to make it answered for others. You are correct, the particular implementation for your use case scenario can be accomplished in many ways. The morale should be that NiFi and other hadoop based components are true winners. Also working with new components keeps things exciting. You would not be making an unwise decision to embrace NiFi. ... View more