FIPS-validated Prometheus monitoring and alerting toolkit container image, designed for secure enterprise environments requiring compliance with Federal Information Processing Standards. This hardened container provides robust metrics collection, alerting, and monitoring capabilities while maintaining FIPS 140-2 compliance.
Core capabilities and strengths of this container
Typical scenarios where this container excels
Download the container image from the registry
docker pull clnstrt-images.cleanstart.com/$ORGANIZATION/prometheus-fips:latestdocker pull clnstrt-images.cleanstart.com/$ORGANIZATION/prometheus-fips:2.45.0Run the container with basic configuration
docker run -d --name prometheus-fips \
-p 9090:9090 \
-v $(pwd)/prometheus.yml:/etc/prometheus/prometheus.yml \
clnstrt-images.cleanstart.com/$ORGANIZATION/prometheus-fips:latestDeploy with production security settings
docker run -d --name prometheus-fips-prod \
--read-only \
--security-opt=no-new-privileges \
--user 65534:65534 \
-p 9090:9090 \
-v $(pwd)/prometheus.yml:/etc/prometheus/prometheus.yml:ro \
-v prometheus-data:/prometheus \
clnstrt-images.cleanstart.com/$ORGANIZATION/prometheus-fips:latestMount local directory for persistent data
docker run -d \
-v prometheus-data:/prometheus \
-v $(pwd)/prometheus.yml:/etc/prometheus/prometheus.yml \
clnstrt-images.cleanstart.com/$ORGANIZATION/prometheus-fips:latestRun with custom port mappings
docker run -d -p 9090:9090 clnstrt-images.cleanstart.com/$ORGANIZATION/prometheus-fips:latestConfiguration options available through environment variables
/etc/prometheus/prometheus.yml/prometheus:9090Recommended security configurations and practices
Recommended security context for Kubernetes deployments
securityContext:
runAsNonRoot: true
runAsUser: 65534
runAsGroup: 65534
readOnlyRootFilesystem: true
allowPrivilegeEscalation: false
capabilities:
drop: ["ALL"]
seccompProfile:
type: RuntimeDefaultEssential links and resources for further information