mimir-fips

Data

Fips

Stig

Updated in the last hour

Mimir-FIPS Overview

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

Mimir is a horizontally scalable multi-tenant time series database (TSDB) for metrics designed for long-term storage with Prometheus.

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 (v1.21 or higher is recommended)
Helm v3.8 or higher for OCI support (Installation instructions)
kubectl installed and configured

Step 1: Start Cluster

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

Step 2: Add Repository to your Local Client

Add the Helm chart to your local Helm client.

helm repo add grafana https://grafana.github.io/helm-charts
helm repo update

Step 3: Deploy via Helm Chart

helm install mimir grafana/mimir-distributed \
    --namespace mimir \
    --create-namespace \
    --set image.repository=reg.mini.dev/mimir-fips \
    --set image.tag=latest \
    --set rollout_operator.image.repository=reg.mini.dev/grafana-rollout-operator-fips \
    --set rollout_operator.image.tag=latest

Wait a minute and check that the Pods are up and running:

kubectl -n mimir get po

Confirm that Minimus images were deployed:

kubectl -n mimir describe pods | grep Image:

Step 4: Clean Up

Uninstall the chart to delete the namespace and its resources, including Pods, Deployments, Services, Secrets, ConfigMaps, etc.:

helm uninstall mimir -n mimir

Technical Considerations

The Mimir image provided by Minimus is a FIPS-validated, slim, security-hardened alternative to the public image from Docker Hub. The images are largely interchangeable, with a few differences as noted below.

Mimir-FIPS built by Minimus:

Runs as non-root by default as user 1000. By comparison, the public image runs as root.
Listens on port 8080/tcp but does not expose it by default. The public image exposes the same port by default.
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.