NATS FIPS-validated messaging system container providing secure, high-performance cloud native messaging infrastructure. Features FIPS 140-2 compliance, built-in security controls, and enterprise-grade reliability for mission-critical deployments requiring regulatory 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/nats-fips:latestdocker pull clnstrt-images.cleanstart.com/$ORGANIZATION/nats-fips:latest-devRun the container with basic configuration
docker run -d --name nats-fips -p 4222:4222 clnstrt-images.cleanstart.com/$ORGANIZATION/nats-fips:latestDeploy with production security settings
docker run -d --name nats-fips-prod \
--read-only \
--security-opt=no-new-privileges \
--user 1000:1000 \
-p 4222:4222 -p 8222:8222 \
-v nats-data:/data \
clnstrt-images.cleanstart.com/$ORGANIZATION/nats-fips:latestMount local directory for persistent data
docker run -d --name nats-fips \
-v $(pwd)/nats-data:/data \
-v $(pwd)/config:/etc/nats \
clnstrt-images.cleanstart.com/$ORGANIZATION/nats-fips:latestRun with custom port mappings
docker run -d --name nats-fips \
-p 4222:4222 \
-p 8222:8222 \
-p 6222:6222 \
clnstrt-images.cleanstart.com/$ORGANIZATION/nats-fips:latestConfiguration options available through environment variables
nats-fipsnats-cluster42228222Recommended security configurations and practices
Recommended security context for Kubernetes deployments
securityContext:
runAsNonRoot: true
runAsUser: 1000
runAsGroup: 1000
readOnlyRootFilesystem: true
allowPrivilegeEscalation: false
capabilities:
drop: ["ALL"]
seccompProfile:
type: RuntimeDefaultEssential links and resources for further information