apache-druid
The official Apache Druid image — a high-performance, column-oriented analytics database designed for sub-second queries on streaming and batch event data at scale.
What is Apache Druid?
The Apache Druid image packages Apache Druid, a real-time analytics database built for fast aggregations and filtering over large volumes of event data. Druid combines columnar storage, time-based partitioning, and indexing to answer interactive queries in milliseconds, and it ingests data from streaming sources such as Apache Kafka as well as from batch files. A Druid cluster runs as several processes — coordinator, overlord, broker, historical, middle manager or indexer, and router — which can be run from the same image with different commands, backed by metadata storage and deep storage. It is used by data engineering and analytics teams that power dashboards, user-facing analytics, and operational monitoring with a reproducible, version-pinned image.
What is Echo's Apache Druid image?
Echo's Apache Druid image is a hardened build of Apache Druid 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 runtime properties, extensions, metadata and deep storage settings, and ingestion specs. 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 Apache Druid deployments, the distroless variant keeps all runtime operations — data ingestion, segment loading, query routing, SQL and native queries, and compaction — fully intact while minimizing exposure; the default variant suits data engineering and analytics teams that need shell access for inspecting cluster state, submitting ingestion specs, or debugging query performance.
What is the difference between Echo's Apache Druid image and the public Apache Druid image?
Public Apache Druid images ship on bases that include OS-level tooling convenient for development but which contribute CVEs that accumulate on a analytics database used in production. Apache Druid images run continuously with access to event data, metadata store and deep storage credentials, 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 Apache Druid 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 Apache Druid needs for data ingestion, segment loading, query routing, SQL and native queries, and compaction while removing the packages that don't belong in a production Apache Druid analytics database. 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 Apache Druid image with Echo's Apache Druid image?
Yes. Echo's Apache Druid image is a drop-in replacement. Update the FROM line in your Dockerfile and your workloads keep running. runtime.properties settings, extensions, ingestion specs, metadata and deep storage connections, and SQL queries all continue to work without changes to your datasources or dashboards.
Is Echo's Apache Druid 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 Apache Druid workloads inside FedRAMP boundaries, where a analytics database that ingests and serves analytical queries over sensitive operational and user event data must meet cryptographic requirements across the full stack — including the OpenSSL and TLS libraries bundled with the Apache Druid image.
What is Echo's vulnerability management SLA on the Apache Druid 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 event data, metadata store and deep storage credentials, and TLS keys and is reachable over the network.
Is Echo's Apache Druid 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 Apache Druid deployments, the distroless variant is the leaner, more secure choice; for data engineering and analytics teams that need shell access for inspecting cluster state, submitting ingestion specs, or debugging query performance, the default variant is the right fit.
How does Echo achieve such a drastic CVE reduction in Apache Druid?
Echo's Apache Druid image is built from source with only the absolute essentials needed to run the Apache Druid analytics database, which significantly shrinks the attack surface. Echo also patches aggressively over time, with backports available so you can stay on the Apache Druid 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 Apache Druid 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 data engineering and analytics teams running Apache Druid under an ATO — whether that's operational analytics, user-facing dashboards, or streaming event analysis for a government program — Echo's hardened Apache Druid image keeps the analytics database layer in-boundary and compliant without requiring custom hardening scripts or manual base image patching between compliance cycles.
.avif)