akhq-fips
AKHQ-FIPS Overview
Secure your stack with a hardened AKHQ-FIPS image freshly-built by Minimus. Minimus images always include the most up-to-date package version for all packages and dependencies contained in the image.
AKHQ is a web-based UI for managing and monitoring Apache Kafka clusters. It is used to browse topics, view messages, administer configurations and more.
FIPS 140-3 Certification
This image is FIPS-validated to ensure its cryptographic operations meet the Federal Information Processing Standards (FIPS) required for secure government and regulated environments. Its core cryptographic modules are validated under the NIST Cryptographic Module Validation Program (CMVP) and comply with the FIPS 140-3 standard.
To verify that the FIPS 140-3 provider is configured and active, follow the instructions in the FIPS compliance tab.
Try It Out
AKHQ needs an Apache Kafka broker to connect to. The steps below start a single-node Kafka cluster and AKHQ using Minimus images.
Step 1 - Create a Docker Network
Create a shared network so AKHQ can reach the Kafka broker by container name:
docker network create akhq-netStep 2 - Start a Kafka Broker
Start a single-node Kafka broker using the Minimus Kafka image. Kafka 3.3+ ships with KRaft, so no separate Zookeeper container is needed:
docker run -d --name kafka \
--net akhq-net \
-e KAFKA_NODE_ID=1 \
-e KAFKA_PROCESS_ROLES=broker,controller \
-e KAFKA_LISTENERS=PLAINTEXT://0.0.0.0:9092,CONTROLLER://0.0.0.0:9093 \
-e KAFKA_ADVERTISED_LISTENERS=PLAINTEXT://kafka:9092 \
-e KAFKA_CONTROLLER_QUORUM_VOTERS=1@kafka:9093 \
-e KAFKA_CONTROLLER_LISTENER_NAMES=CONTROLLER \
-e KAFKA_LISTENER_SECURITY_PROTOCOL_MAP=CONTROLLER:PLAINTEXT,PLAINTEXT:PLAINTEXT \
-e KAFKA_OFFSETS_TOPIC_REPLICATION_FACTOR=1 \
-e CLUSTER_ID=MkU3OEVBNTcwNTJENDM2Qk \
reg.mini.dev/kafka-fipsStep 3 - Start AKHQ
Run AKHQ with an inline configuration that points it at the Kafka broker:
docker run -d --name akhq \
--net akhq-net \
-p 8080:8080 \
-e AKHQ_CONFIGURATION="akhq:
connections:
local:
properties:
bootstrap.servers: kafka:9092" \
reg.mini.dev/akhq-fipsOnce both containers are running, open http://localhost:8080 to access the AKHQ web interface. You can browse topics, consumer groups, and cluster configuration.
Step 4 - Clean Up
Stop and remove the containers and network:
docker rm -f akhq kafka
docker network rm akhq-netTechnical Considerations
The AKHQ-FIPS image provided by Minimus is a slim, security-hardened alternative to the public image from Docker Hub. The images are largely interchangeable, with a few differences as noted below.
AKHQ-FIPS built by Minimus:
- Runs as non-root by default for a security-first approach that protects against privilege escalation attacks.
- Drill down on the version specification tab to see the default user, listening ports, entrypoint, volumes, environment variables, etc.
The Payoff
A hardened, minimal image that will remain more secure for the long run and accrue vulnerabilities at a slower rate.
- See the risk reduction dashboard for a detailed CVE comparison over the past 30 days.
- Review the compliance report to see the default hardening and security configurations for the image.
Terms & Info
Trademark
This catalog is published by Minimus. All product names, logos, and marks, other than those belonging to Minimus, shown are owned by their respective rights holders and appear here only to identify the open source software each image contains. Minimus claims no ownership of those marks and implies no affiliation with, endorsement by, certification by, or sponsorship by any rights holder.
Disclaimer
Images are provided "as-is" without warranty of any kind. "Hardened" refers to the security configuration applied at the time of build and does not constitute a guarantee of ongoing security or absence of vulnerabilities. The free tier is provided without support, SLA, or guaranteed patching timelines. Security updates may be applied to paid subscriptions before or instead of free tier images. By pulling or using any image you agree to our Terms of Use.