1. Images & Charts
  2. kafka-proxy-fips
kafka-proxy-fips

kafka-proxy-fips

Fips
Infra
Stig
Updated 4 days ago

Kafka-Proxy-FIPS Overview

Secure your stack with a FIPS-validated, hardened Kafka-Proxy-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.


Kafka Proxy sits between Kafka clients and brokers, handling SASL/PLAIN authentication and SSL/TLS termination so clients can connect without managing certificates or credentials directly, while also rewriting broker metadata so it can be reached through local proxy addresses, including from clients running in Kubernetes. Use this image when you need to meet the requirements for FIPS-validated cryptographic protection.


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

For a quick test, run the proxy against a Kafka broker.

Create a shared network so the containers can reach each other by name:

docker network create kafka-proxy-net

Start a Kafka broker on the network, advertising itself as broker so it's reachable by other containers on the network:

docker run -d --rm --name broker --network kafka-proxy-net \
  -e KAFKA_ADVERTISED_LISTENERS=PLAINTEXT://broker:9092 \
  reg.mini.dev/kafka-fips

Run the proxy on the same network:

docker run --rm --network kafka-proxy-net \
  -p 30001:30001 \
  reg.mini.dev/kafka-proxy-fips \
  server \
  --bootstrap-server-mapping "broker:9092,0.0.0.0:30001" \
  --dial-address-mapping "broker:9092,broker:9092" \
  --debug-enable

The proxy listens on port 30001 and forwards traffic to broker:9092 while transparently handling authentication. Point a Kafka client at localhost:30001 to connect through the proxy.


Technical Considerations

The Kafka-Proxy-FIPS image provided by Minimus is a FIPS-validated, slim, security-hardened alternative to the public image.

Kafka-Proxy-FIPS built by Minimus:

  1. Runs as non-root by default.
  2. 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.


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.