Installing NiFi on containers, Windows and restricted networks, building custom distributions, and automating flow deployment with the NiFi CLI and Git-based registry clients.
Using the apache/nifi image: generated single-user credentials, environment variables for ports, TLS and LDAP, JVM heap settings, persisting repositories and configuration in volumes, and why the image targets standalone mode.
Promoting flows from development to production with a Git registry client, pull requests and the NiFi CLI: versioned process groups, parameter context per environment, automated import, flow analysis rules as a gate and rollback.
Scripting NiFi operations with the Toolkit CLI and REST API: deploying versioned flows, starting and stopping process groups, managing cluster nodes, secure connections with proxied entities and property renames that break scripts.
Running NiFi without internet access: verified offline binaries, custom distributions with the NARs you need, NAR providers pointed at internal stores, Python processor dependencies, and certificate and time sources on isolated networks.
Adding optional bundles that are not in the convenience binary, such as graph, media or gRPC support, by building the nifi-assembly module with Maven profiles, and maintaining that build across upgrades.
Installing custom and optional NARs without restarts through the autoload directory and external resource providers: polling interval, conflict resolution, startup blocking and the NiFi Registry NAR provider.
Putting NGINX, HAProxy or a cloud load balancer in front of NiFi: root path mapping, proxy headers, allowed proxy hosts, sticky sessions for clusters, TLS termination choices and the 401 errors that missing affinity causes.
Installing and running NiFi on Windows Server: Java 21, the nifi.cmd commands that replaced the old batch scripts, running as a service, antivirus exclusions and file path handling.
Keeping nifi.properties, bootstrap.conf, authorizers.xml and state-management.xml consistent across nodes and environments, placing repositories outside the install directory and reviewing property changes at each upgrade.
Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.