apache-pinot
The official Apache Pinot image — a real-time distributed OLAP datastore built for low-latency analytics on streaming and batch data, powering user-facing dashboards at scale.
What is Apache Pinot?
The Apache Pinot image packages Apache Pinot, a real-time distributed OLAP datastore designed to answer analytical queries with low latency and high concurrency. Pinot ingests data from streaming sources such as Apache Kafka and from batch sources such as Hadoop, S3, and Spark, stores it in columnar segments with rich indexing, and serves SQL queries through its broker. A cluster runs as controller, broker, server, and minion components, coordinated through ZooKeeper, all available from the same image. It is used by data engineering and analytics teams powering user-facing analytics, anomaly detection, and real-time business metrics.
What is Echo's Apache Pinot image?
Echo's Apache Pinot image is a hardened build of Apache Pinot 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 table and schema configs, ZooKeeper settings, ingestion jobs, and index configuration. 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 Pinot deployments, the distroless variant keeps all runtime operations — real-time and batch ingestion, segment management, query routing, and SQL execution — fully intact while minimizing exposure; the default variant suits data engineering and analytics teams that need shell access for inspecting tables, running admin commands, or debugging queries.
What is the difference between Echo's Apache Pinot image and the public Apache Pinot image?
Public Apache Pinot images ship on bases that include OS-level tooling convenient for development but which contribute CVEs that accumulate on a real-time analytics datastore used in production. Apache Pinot images run continuously with access to event data, ZooKeeper and deep store 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 Pinot 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 Pinot needs for real-time and batch ingestion, segment management, query routing, and SQL execution while removing the packages that don't belong in a production Apache Pinot real-time analytics datastore. 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 Pinot image with Echo's Apache Pinot image?
Yes. Echo's Apache Pinot image is a drop-in replacement. Update the FROM line in your Dockerfile and your workloads keep running. table and schema configurations, ZooKeeper coordination, Kafka ingestion, deep store settings, and SQL queries all continue to work without changes to your tables or applications.
Is Echo's Apache Pinot 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 Pinot workloads inside FedRAMP boundaries, where a real-time analytics datastore that ingests streaming data and serves high-concurrency queries to production applications must meet cryptographic requirements across the full stack — including the OpenSSL and TLS libraries bundled with the Apache Pinot image.
What is Echo's vulnerability management SLA on the Apache Pinot 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, ZooKeeper and deep store credentials, and TLS keys and is reachable over the network.
Is Echo's Apache Pinot 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 Pinot deployments, the distroless variant is the leaner, more secure choice; for data engineering and analytics teams that need shell access for inspecting tables, running admin commands, or debugging queries, the default variant is the right fit.
How does Echo achieve such a drastic CVE reduction in Apache Pinot?
Echo's Apache Pinot image is built from source with only the absolute essentials needed to run the Apache Pinot real-time analytics datastore, which significantly shrinks the attack surface. Echo also patches aggressively over time, with backports available so you can stay on the Apache Pinot 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 Pinot 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 Pinot under an ATO — whether that's real-time operational metrics, user-facing analytics, or streaming anomaly detection — Echo's hardened Apache Pinot image keeps the real-time analytics datastore layer in-boundary and compliant without requiring custom hardening scripts or manual base image patching between compliance cycles.
.avif)