logstash-fips

packaged by Chainguard

Chainguard Container for logstash-fips

Logstash is a server-side data processing pipeline that ingests data from multiple sources, transforms it, and sends it to your chosen destination

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/logstash-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

Chainguard's logstash-fips container image is comparable to the upstream image, with the following differences:

• Like all other Chainguard Containers, logstash-fips features a stripped down, minimal design
• It has few-to-zero CVEs
• It does not run as the root user
• Cryptography uses the BouncyCastle FIPS providers (BCFIPS, BCJSSE) in approved-only mode, including in Ruby plugins through a FIPS build of jruby-openssl
• Elastic's FIPS validation plugin checks the JVM crypto setup (BC-FIPS providers in approved-only mode, FIPS jruby-openssl) at startup, and Logstash exits if it fails
• The JVM trust store is /etc/ssl/certs/java/cacerts.bcfks (BCFKS) and the security properties are the JDK's /usr/lib/jvm/java-21-openjdk/conf/security/java.security; files mounted at the config/security/cacerts.bcfks and config/security/java.security paths used by Elastic's logstash-observability-sre image are ignored
• Algorithms that FIPS does not approve are refused, for example MD5 in the fingerprint and anonymize filters
• Passphrases for encrypted TLS private keys must be at least 14 characters
• logstash-keystore uses BCFKS; keystores created by non-FIPS Logstash cannot be read and must be recreated
• Plugins installed with logstash-plugin run in FIPS mode unless they bundle their own copy of jruby-openssl; check for this after installing additional plugins

Getting Started

Create a simple config file

Create a pipeline that reads from standard input and prints each event:

cat > logstash.conf <<EOF
input {
  stdin { }
}

output {
  stdout { codec => rubydebug }
}
EOF

Run the container

Mount the pipeline over the image's default pipeline and run Logstash:

docker run --rm -it \
  -v $(pwd)/logstash.conf:/usr/share/logstash/pipeline/default.conf \
  cgr.dev/ORGANIZATION/logstash-fips:latest

Documentation and Resources

• Official Documentation
• GitHub Repository
• Overview & Download Page (Elastic)
• Reference Guide (Elastic)

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.