grafana-alloy-iamguarded-fips

Chainguard Container for grafana-alloy-iamguarded-fips

OpenTelemetry Collector distribution with programmable pipelines

Chainguard Containers are regularly-updated, secure-by-default container images.

Download this Container Image

For those with access, this container image is available on cgr.dev:

docker pull cgr.dev/ORGANIZATION/grafana-alloy-iamguarded-fips:latest

Be sure to replace the ORGANIZATION placeholder with the name used for your organization's private repository within the Chainguard Registry.

Compatibility Notes

This is the FIPS-compliant, IAMGuarded variant of Grafana Alloy, optimized for enhanced security with least-privilege access controls and FIPS 140-2/140-3 cryptographic compliance. Key differences from the standard Grafana Alloy image:

• FIPS Compliance: Built with FIPS-validated cryptographic modules for environments requiring FIPS 140-2/140-3 compliance
• Custom Installation Path: Grafana Alloy is installed at /opt/iamguarded/grafana-alloy/bin/alloy instead of the standard location
• Non-Root User: Runs as UID/GID 1001 (non-root) by default for improved security
• Data Directory: Uses /opt/iamguarded/grafana-alloy/data for persistent data storage
• Cache Directory: Uses /tmp/iamguarded/pkg/cache for temporary cache files
• PATH Configuration: Custom PATH includes /opt/iamguarded/grafana-alloy/bin as the first directory

Getting Started

Pull and run the FIPS-compliant IAMGuarded Grafana Alloy image with a basic configuration:

docker run \
  -p 12345:12345 \
  cgr.dev/ORGANIZATION/grafana-alloy-iamguarded-fips:latest \
    run --server.http.listen-addr=0.0.0.0:12345 \
    --storage.path=/opt/iamguarded/grafana-alloy/data \
    /etc/alloy/config.alloy

After running the container, access the interactive debugging UI at http://localhost:12345.

Helm Chart Installation

For Kubernetes deployments, use the IAMGuarded Grafana Alloy Helm chart with the FIPS variant:

helm install grafana-alloy oci://cgr.dev/ORGANIZATION/iamguarded-charts/grafana-alloy \
  --namespace grafana-alloy \
  --create-namespace \
  --set "global.org=ORGANIZATION" \
  --set "image.repository=cgr.dev/ORGANIZATION/grafana-alloy-iamguarded-fips"

Be sure to replace ORGANIZATION with your Chainguard organization name.

For more details on the Helm chart configuration, see the IAMGuarded Grafana Alloy Helm Chart README.

Configuration

Custom Configuration

Mount your own Alloy configuration file:

docker run \
  -v $(pwd)/config.alloy:/etc/alloy/config.alloy:ro \
  -p 12345:12345 \
  cgr.dev/ORGANIZATION/grafana-alloy-iamguarded-fips:latest \
    run --server.http.listen-addr=0.0.0.0:12345 \
    --storage.path=/opt/iamguarded/grafana-alloy/data \
    /etc/alloy/config.alloy

Environment Variables

The IAMGuarded FIPS image sets a custom PATH:

PATH=/opt/iamguarded/grafana-alloy/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

FIPS Compliance

This image is built with FIPS-validated cryptographic modules and is suitable for environments that require FIPS 140-2 or FIPS 140-3 compliance. The FIPS-compliant cryptographic libraries ensure that all cryptographic operations meet federal security standards.

For the standard (non-FIPS) IAMGuarded variant, see grafana-alloy-iamguarded:

docker pull cgr.dev/ORGANIZATION/grafana-alloy-iamguarded:latest

Documentation and Resources

• Grafana Alloy Official Documentation
• Grafana Alloy GitHub Repository
• Getting Started with Grafana Alloy
• Deploying Grafana Alloy on Kubernetes

What are Chainguard Containers?

Chainguard's free tier of Starter container images are built with Wolfi, our minimal Linux undistro.

All other Chainguard Containers are built with Chainguard OS, Chainguard's minimal Linux operating system designed to produce container images that meet the requirements of a more secure software supply chain.

The main features of Chainguard Containers include:

• Minimal design, without unnecessary software bloat
• Daily builds to ensure container images are up-to-date with available security patches
• High quality build-time SBOMs attesting to the provenance of all artifacts within the image
• Verifiable signatures provided by Sigstore
• Reproducible builds with Cosign and apko (read more about reproducibility)

For cases where you need container images with shells and package managers to build or debug, most Chainguard Containers come paired with a development, or -dev, variant.

In all other cases, including Chainguard Containers tagged as :latest or with a specific version number, the container images include only an open-source application and its runtime dependencies. These minimal container images typically do not contain a shell or package manager.

Although the -dev container image variants have similar security features as their more minimal versions, they include additional software that is typically not necessary in production environments. We recommend using multi-stage builds to copy artifacts from the -dev variant into a more minimal production image.

Need additional packages?

To improve security, Chainguard Containers include only essential dependencies. Need more packages? Chainguard customers can use Custom Assembly to add packages, either through the Console, chainctl, or API.

To use Custom Assembly in the Chainguard Console: navigate to the image you'd like to customize in your Organization's list of images, and click on the Customize image button at the top of the page.

Learn More

Refer to our Chainguard Containers documentation on Chainguard Academy. Chainguard also offers VMs and Libraries — contact us for access.

Trademarks

This software listing is packaged by Chainguard. The trademarks set forth in this offering are owned by their respective companies, and use of them does not imply any affiliation, sponsorship, or endorsement by such companies.