apicurio-registry
The official Apicurio Registry image — a schema and API registry that stores and versions Avro, Protobuf, JSON Schema, and OpenAPI artifacts for event-driven and API-first architectures.
What is Apicurio Registry?
The Apicurio Registry image packages Apicurio Registry, a runtime registry for API and schema definitions. It stores and versions artifacts such as Apache Avro, Protobuf, and JSON Schema definitions as well as OpenAPI, AsyncAPI, and GraphQL specifications, applies validity and compatibility rules, and serves them through a REST API. It offers a Confluent-compatible schema registry API, so Kafka clients can use it as a drop-in registry, and supports storage in memory, SQL databases, or Kafka. It is used by data engineering and platform teams in event-driven architectures, commonly alongside Kafka and Strimzi.
What is Echo's Apicurio Registry image?
Echo's Apicurio Registry image is a hardened build of Apicurio Registry 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 storage configuration, compatibility rules, authentication settings, and registered artifacts. 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 Apicurio Registry deployments, the distroless variant keeps all runtime operations — artifact storage, versioning, rule validation, and REST and Confluent-compatible API requests — fully intact while minimizing exposure; the default variant suits data engineering and platform teams that need shell access for inspecting artifacts, checking configuration, or debugging client serialization.
What is the difference between Echo's Apicurio Registry image and the public Apicurio Registry image?
Public Apicurio Registry images ship on bases that include OS-level tooling convenient for development but which contribute CVEs that accumulate on a schema registry used in production. Apicurio Registry images run continuously with access to schema and API definitions, database credentials, and authentication settings. 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 Apicurio Registry 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 Apicurio Registry needs for artifact storage, versioning, rule validation, and REST and Confluent-compatible API requests while removing the packages that don't belong in a production Apicurio Registry schema registry. 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 Apicurio Registry image with Echo's Apicurio Registry image?
Yes. Echo's Apicurio Registry image is a drop-in replacement. Update the FROM line in your Dockerfile and your workloads keep running. REST and Confluent-compatible endpoints, compatibility rules, SQL or Kafka storage, and OIDC authentication all continue to work without changes to your Kafka clients or registered schemas.
Is Echo's Apicurio Registry 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 Apicurio Registry workloads inside FedRAMP boundaries, where a schema registry that serves the contracts that producers and consumers rely on for every message and API call must meet cryptographic requirements across the full stack — including the OpenSSL and TLS libraries bundled with the Apicurio Registry image.
What is Echo's vulnerability management SLA on the Apicurio Registry 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 schema and API definitions, database credentials, and authentication settings and is reachable over the network.
Is Echo's Apicurio Registry 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 Apicurio Registry deployments, the distroless variant is the leaner, more secure choice; for data engineering and platform teams that need shell access for inspecting artifacts, checking configuration, or debugging client serialization, the default variant is the right fit.
How does Echo achieve such a drastic CVE reduction in Apicurio Registry?
Echo's Apicurio Registry image is built from source with only the absolute essentials needed to run the Apicurio Registry schema registry, which significantly shrinks the attack surface. Echo also patches aggressively over time, with backports available so you can stay on the Apicurio Registry 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 Apicurio Registry 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 platform teams running Apicurio Registry under an ATO — whether that's governed event schemas, an API catalog, or contract validation for data pipelines — Echo's hardened Apicurio Registry image keeps the schema registry layer in-boundary and compliant without requiring custom hardening scripts or manual base image patching between compliance cycles.
.avif)