cortex
The official Cortex image — a horizontally scalable, multi-tenant, long-term storage backend for Prometheus metrics, run as a set of microservices.
What is Cortex?
The Cortex image packages Cortex, a CNCF project that provides horizontally scalable, highly available, multi-tenant, long-term storage for Prometheus metrics. Cortex receives metrics through Prometheus remote write and serves PromQL queries, and it can run as a single binary or as separate microservices such as distributor, ingester, querier, query-frontend, compactor, and store-gateway. It stores blocks in object storage such as Amazon S3, Google Cloud Storage, or Azure Blob Storage and enforces per-tenant limits. It is used by observability and platform teams that need metrics at a scale and retention beyond a single Prometheus server.
What is Echo's Cortex image?
Echo's Cortex image is a hardened build of Cortex 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 tenant limits, object storage configuration, ring settings, and remote write endpoints. 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 Cortex deployments, the distroless variant keeps all runtime operations — remote write ingestion, block storage, PromQL queries, compaction, and ring membership — fully intact while minimizing exposure; the default variant suits observability and platform teams that need shell access for debugging component health, inspecting rings, or testing queries.
What is the difference between Echo's Cortex image and the public Cortex image?
Public Cortex images ship on bases that include OS-level tooling convenient for development but which contribute CVEs that accumulate on a metrics storage backend used in production. Cortex images run continuously with access to tenant metrics data, object storage credentials, and TLS keys. OS-level CVEs in the base image — particularly in libraries such as openssl, zlib, and libc, along with the Go runtime 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 Cortex 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 Cortex needs for remote write ingestion, block storage, PromQL queries, compaction, and ring membership while removing the packages that don't belong in a production Cortex metrics storage backend. 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 Cortex image with Echo's Cortex image?
Yes. Echo's Cortex image is a drop-in replacement. Update the FROM line in your Dockerfile and your workloads keep running. Prometheus remote write, PromQL queries, tenant limits, object storage backends, and ring configuration all continue to work without changes to your Prometheus servers or dashboards.
Is Echo's Cortex 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 Cortex workloads inside FedRAMP boundaries, where a metrics storage backend that receives and stores metrics from many tenants and serves queries to dashboards and alerting must meet cryptographic requirements across the full stack — including the OpenSSL and TLS libraries bundled with the Cortex image.
What is Echo's vulnerability management SLA on the Cortex 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 tenant metrics data, object storage credentials, and TLS keys and is reachable over the network.
Is Echo's Cortex 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 Cortex deployments, the distroless variant is the leaner, more secure choice; for observability and platform teams that need shell access for debugging component health, inspecting rings, or testing queries, the default variant is the right fit.
How does Echo achieve such a drastic CVE reduction in Cortex?
Echo's Cortex image is built from source with only the absolute essentials needed to run the Cortex metrics storage backend, which significantly shrinks the attack surface. Echo also patches aggressively over time, with backports available so you can stay on the Cortex 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 Cortex 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 platform teams running Cortex under an ATO — whether that's centralized multi-tenant metrics, long-term retention for compliance, or a large-scale monitoring platform — Echo's hardened Cortex image keeps the metrics storage backend layer in-boundary and compliant without requiring custom hardening scripts or manual base image patching between compliance cycles.
.avif)