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
| Component | Role |
|---|---|
| Management | Cluster, node, and ecosystem management. |
| Metering | Per-tenant usage and accounting metrics. |
| KMS | The Key Management Service: secure custody of object and cluster keys. See Encryption & Key Management. |
| IAM / Auth | Identity and authentication per realm or site, across one or more clusters. See IAM & Auth. |
| Load Balancer | Built-in, SNI-aware load balancer that distributes client traffic across the cluster’s nodes. |
| Health | Continuously measures object-store latency over time and flags high variance or problems. |
| Metrics | Exposes an OpenMetrics endpoint for monitoring with tools such as Grafana. |
| Scanner | Proactively monitors security posture, including firewall status and credential hygiene. |
Exaba One
Exaba One is the hosted portal for your Exaba deployments. It tracks each install, connects you to Exaba support, and provides monitoring and alerting at the deployment level (a deployment is one or more clusters, and a cluster is many nodes) and the cluster level. See Exaba One.
See also
- Architecture: how these components are arranged into nodes and clusters.
- Features: the full capability list.
- Durability: how erasure coding protects your data.