Solution: docker run --name nifi-ssl \ -v /home/ec2-user/project/nifi-standalone/certs:/opt/certs \ -v /home/ec2-user/project/nifi-standalone/conf:/opt/conf \ -p 8080:8443 \ -e NIFI_WEB_PROXY_HOST=11.111.111.111:8080 \ -e AUTH=tls \ -e KEYSTORE_PATH=/opt/certs/keystore.jks \ -e KEYSTORE_TYPE=JKS \ -e KEYSTORE_PASSWORD=passwordFROMnifi.properties \ -e TRUSTSTORE_PATH=/opt/certs/truststore.jks \ -e TRUSTSTORE_PASSWORD=passwordFROMnifi.properties \ -e TRUSTSTORE_TYPE=JKS \ -e INITIAL_ADMIN_IDENTITY='CN=admin, OU=nifi' \ -d \ apache/nifi:latest ... View more

The main point that is always communicated is that running our version in a Data Flow platform, brings you direct integration with other components. Both functional and nonfunctional (e.g. with Ranger and Atlas). That being said, as you can see there are also improvements to the product itself, but I am not aware of a clear public list with this, because it fluctuates a lot over time (First we discover points, and then we commit many of these back to the apache project eventually). Of course having the latest Apache Nifi can have some benefits, but overall I recommend using the latest Cloudera version of Nifi as that one has seen more testing and is less likely to see surprises. ... View more