logstash

The official Logstash image — Elastic's server-side data processing pipeline that ingests logs and events from many sources, transforms them, and ships them to Elasticsearch and other destinations.

logstash, elastic stack, log pipeline, elk, data ingestion, grok

What is Logstash?

The Logstash image packages Logstash, the data processing pipeline from the Elastic Stack that ingests data from many sources at once, transforms it, and sends it to a destination such as Elasticsearch, OpenSearch, Kafka, or object storage. Pipelines are defined in configuration files with input, filter, and output plugins — for example Beats, syslog, and Kafka inputs, grok and mutate filters, and Elasticsearch outputs — and run on a JVM. The image is configured through logstash.yml and pipeline files mounted into the container. It is used by observability, security, and platform teams that parse and enrich logs and events before indexing, and that want a reproducible, version-pinned log processing tier.

What is Echo's Logstash image?

Echo's Logstash image is a hardened build of Logstash on Echo's hardened base. Echo images are designed to be a drop-in replacement: swap the image reference in your Dockerfile or deployment manifest and CVEs go to zero without disrupting your pipeline configuration, plugins, logstash.yml settings, and persistent queue storage. Every image is tested across clouds, image use cases, and deployment targets. Echo ships every image in two variants:

  • Distroless variant — optimized for runtime use, with the smallest possible attack surface
  • Default variant — includes essential build tools, package managers, and shells for teams that need operational access

For production Logstash deployments, the distroless variant keeps all runtime operations — event ingestion, filtering and enrichment, plugin execution, queueing, and delivery to outputs — fully intact while minimizing exposure; the default variant suits observability and security teams that need shell access for testing pipeline configs, installing plugins, or debugging parsing rules.

What is the difference between Echo's Logstash image and the public Logstash image?

Public Logstash images ship on bases that include OS-level tooling convenient for development but which contribute CVEs that accumulate on a log processing pipeline used in production. Logstash images run continuously with access to log and event data, credentials for connected systems, and TLS keys. OS-level CVEs in the base image — particularly in libraries such as openssl, zlib, and libc, along with the bundled JVM dependencies — create exploitable paths that bypass application-layer controls entirely, allowing attackers to move from a network-reachable service to host-level access. For teams running Logstash across many environments, the image is also a steady source of scanner noise in the CI pipeline — every package in the base becomes a finding your security team must triage, even when none of it is reachable from the service. Echo's build retains everything Logstash needs for event ingestion, filtering and enrichment, plugin execution, queueing, and delivery to outputs while removing the packages that don't belong in a production Logstash log processing pipeline. As we covered in our post on how to protect your company from software supply chain attacks, long-running services that hold sensitive data and listen on the network are among the widest attack surfaces in the container stack. Echo commits to a 7-day SLA for critical and high severity vulnerabilities, and 10 days for medium, low, and unknown — with vulnerabilities triaged within 24 hours. Echo images are recognized by all major scanners and mirrored to all major registries, so they fit into existing pipelines without changing your registry, scanner, or runtime tooling.

FAQ

Can I replace my Logstash image with Echo's Logstash image?

Yes. Echo's Logstash image is a drop-in replacement. Update the FROM line in your Dockerfile and your workloads keep running. pipeline configuration files, input, filter, and output plugins, logstash.yml settings, and Beats and Elasticsearch connections all continue to work without changes to your grok patterns or pipelines.

Is Echo's Logstash image FIPS-validated?

Yes. Echo's FIPS-validated images use cryptographic modules with an active FIPS 140-3 CMVP certificate, making them fit for federal use — unlike FIPS-compliant images that haven't been validated. This matters for teams running Logstash workloads inside FedRAMP boundaries, where a log processing pipeline that receives logs and events from many sources and forwards them to indexing and storage systems must meet cryptographic requirements across the full stack — including the OpenSSL and TLS libraries bundled with the Logstash image.

What is Echo's vulnerability management SLA on the Logstash image?

Echo commits to a 7-day SLA for critical and high severity vulnerabilities, and 10 days for medium, low, and unknown — with vulnerabilities triaged within 24 hours. Patches are mirrored automatically into your private registry so you're always running a clean version — critical for a long-running service that holds log and event data, credentials for connected systems, and TLS keys and is reachable over the network.

Is Echo's Logstash image distroless?

Echo ships every image in two variants: a distroless variant optimized for runtime use, and a default variant that includes essential build tools, package managers, and shells. For production Logstash deployments, the distroless variant is the leaner, more secure choice; for observability and security teams that need shell access for testing pipeline configs, installing plugins, or debugging parsing rules, the default variant is the right fit.

How does Echo achieve such a drastic CVE reduction in Logstash?

Echo's Logstash image is built from source with only the absolute essentials needed to run the Logstash log processing pipeline, which significantly shrinks the attack surface. Echo also patches aggressively over time, with backports available so you can stay on the Logstash version your applications and their dependencies are certified against — avoiding a disruptive upgrade forced purely by OS-level vulnerabilities in the base image rather than by your own requirements.

Will Echo's Logstash image help us achieve FedRAMP?

Yes. The hard parts of FedRAMP — managing vulnerabilities, applying fixes, and using FIPS-validated cryptography — are baked into Echo images, including STIG-hardened configuration and ConMon/POA&M-ready reporting. For observability and security teams running Logstash under an ATO — whether that's centralized log ingestion, security event enrichment, or audit log pipelines in a regulated environment — Echo's hardened Logstash image keeps the log processing pipeline layer in-boundary and compliant without requiring custom hardening scripts or manual base image patching between compliance cycles.

‍

Interested in base images that start and stay clean?