rmq-messaging-topology-operator-fips

Data

Fips

Stig

Updated in the last hour

RMQ-Messaging-Topology-Operator-FIPS Overview

Secure your stack with a hardened RMQ-Messaging-Topology-Operator-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.

RabbitMQ Messaging Topology Operator is a Kubernetes operator that lets developers create and manage RabbitMQ messaging topologies within a RabbitMQ cluster using a declarative Kubernetes API. It works alongside the RabbitMQ Cluster Operator.

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

Prerequisites

A running Kubernetes cluster
RabbitMQ Cluster Operator FIPS installed in the cluster
A RabbitMQ FIPS cluster deployed using the Cluster Operator
cert-manager FIPS v1.2.0 or above installed in the cluster
kubectl installed and configured
Helm v3.8 or higher for OCI support (Installation instructions)

Step 1: Start Cluster

If you have a cluster to work with, skip this step. Otherwise, start a Minikube cluster. Deployment instructions

Step 2: Create a Namespace

Create a namespace for the operator:

kubectl create namespace rabbitmq-system

Step 3: Prepare the Manifest

Download the operator manifest:

curl -sL https://github.com/rabbitmq/messaging-topology-operator/releases/latest/download/messaging-topology-operator-with-certmanager.yaml \
  -o messaging-topology-operator.yaml

Next, we need to edit the file messaging-topology-operator.yaml to point to the Minimus registry:

      containers:
        - image: reg.mini.dev/rmq-messaging-topology-operator-fips:latest

If you have yq installed, you can run the following command to make the change:

yq -i '
  select(.kind == "Deployment" and .metadata.name == "messaging-topology-operator") 
  |= .spec.template.spec.containers[0].image = "reg.mini.dev/rmq-messaging-topology-operator-fips:latest"
' messaging-topology-operator.yaml

Step 4: Install the RabbitMQ Messaging Topology Operator

Apply the manifest:

kubectl apply -f messaging-topology-operator.yaml

Wait a minute and check that the operator Pod is up and running:

kubectl -n rabbitmq-system get po

The operator Pod should be listed and running, for example:

NAME                                                   READY   STATUS    RESTARTS   AGE
messaging-topology-operator-7d4b6f8c9f-x2k4n           1/1     Running   0          1m

Verify that the expected Minimus image is in use:

kubectl -n rabbitmq-system describe deploy messaging-topology-operator | grep Image:

It should return:

Image:           reg.mini.dev/rmq-messaging-topology-operator-fips:latest

Step 5: Create a Messaging Topology Resource

With the operator running, you can declaratively manage RabbitMQ resources such as queues, exchanges, bindings, users, vhosts, policies, permissions, federations, etc.

For example, create a queue by saving the following to test-queue.yaml. Add in you RabbitMQ cluster name:

apiVersion: rabbitmq.com/v1beta1
kind: Queue
metadata:
  name: test-queue
spec:
  name: test-queue
  rabbitmqClusterReference:
    name: <your-rabbitmq-cluster-name>

Apply it:

kubectl apply -f test-queue.yaml

Check the queue status:

kubectl get queues

For more examples, see the upstream examples and the usage guide.

Technical Considerations

The RMQ-Messaging-Topology-Operator-FIPS image provided by Minimus is a slim, security-hardened alternative to the public image. The images are largely interchangeable, with a few differences as noted below.

RMQ-Messaging-Topology-Operator-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.