System Components

An Exaba deployment is made up of a small set of software components. This page is the component map; for how they are arranged into nodes and clusters, see Architecture.

Data path

The data path has two layers that scale independently: the C-node (compute) and the D-node (storage). See Architecture for how they are arranged into nodes and clusters.

Interfaces

  • S3 API: the primary client interface. Standard S3 tools, SDKs, and backup software connect here.
  • Admin Portal: the browser-based console for management and observability.
  • CLI (exaba-cli): command-line management and automation.
  • Management API: REST API for programmatic control and automation of the platform.

Platform services

ComponentRole
ManagementCluster, node, and ecosystem management.
MeteringPer-tenant usage and accounting metrics.
KMSThe Key Management Service: secure custody of object and cluster keys. See Encryption & Key Management.
IAM / AuthIdentity and authentication per realm or site, across one or more clusters. See IAM & Auth.
Load BalancerBuilt-in, SNI-aware load balancer that distributes client traffic across the cluster’s nodes.
HealthContinuously measures object-store latency over time and flags high variance or problems.
MetricsExposes an OpenMetrics endpoint for monitoring with tools such as Grafana.
AlertBuilt-in alerting that routes INFO, WARN, and ERROR events to messaging and on-call systems, and to Exaba One for remote monitoring.
ScannerProactively monitors security posture, including firewall status and credential hygiene.

Exaba One

Exaba One is the remote management and monitoring portal. It provides monitoring and alerting at the deployment level (a deployment is a group of clusters) and the cluster level, plus access to partner materials and billing details.

See also

  • Architecture: how these components are arranged into nodes and clusters.
  • Features: the full capability list.
  • Durability: how erasure coding protects your data.