Apache Ozone Distributed Object Store

This is a repackaged open source software product wherein additional charges apply for cloudimg support services.

## Apache Ozone - Production-Ready Distributed Object Store

Deploy a fully configured, S3-compatible distributed object store on AWS in minutes - not hours. This image delivers Apache Ozone preinstalled and running as managed system services, so you can start creating buckets and storing objects immediately after launch, without standing up a multi-node Hadoop or Ozone cluster by hand.

### Why This Image Instead of a DIY Install

• Versus manual EC2 setup: Skip the hours of downloading, checksum-verifying, configuring the Ozone Manager, Storage Container Manager, Datanode, Recon UI and S3 Gateway, writing systemd units, provisioning a data disk, and hardening credentials. This image handles all of that at launch.
• Versus a self-managed cluster: Get a single-instance all-roles topology tuned for single-node writes (RATIS factor one) that behaves like a real Ozone cluster for development, testing, single-tenant object storage and proof-of-concept work, with a clean upgrade path to a multi-node deployment.
• Versus other community images: Benefit from a hardened first-boot process that generates a unique management password and unique S3 access key and secret per instance (no shared or default credentials), a dedicated data volume for the object store, and 24/7 professional support from cloudimg.

### Application Stack

• Apache Ozone installed under /opt/ozone, run by a dedicated unprivileged service account
• Five systemd services: the Ozone Manager, the Storage Container Manager, a Datanode, the Recon management UI and the S3 Gateway
• Headless OpenJDK Java runtime
• All object store metadata and container data on a dedicated EBS data volume - independently resizable for IOPS and capacity scaling
• nginx on port 80 publishing the read-only Recon management console behind HTTP Basic authentication, plus an unauthenticated health endpoint

### S3-Compatible Object Storage

The Ozone S3 Gateway exposes the Amazon S3 REST API, so existing S3 tooling - the AWS CLI, S3 SDKs and S3-compatible applications - works against Ozone unchanged. Create volumes and buckets, then put and get objects using the per-instance access key and secret. Ozone is also HDFS compatible through the ofs and o3fs file system schemes for Hadoop and Spark workloads.

### Security

Secure First Boot: A one-shot service generates a fresh management password and a unique S3 access key and secret per instance, writes them to a root-only file, and stages the nginx credential store before the console is reachable. No shared or default credentials ship in the image.

Network Isolation: Every Ozone service binds to loopback only. The single public surface is nginx on port 80 (basic auth) and SSH on port 22. Deploy in a private VPC subnet and use security groups to restrict access. The S3 Gateway is reached over an SSH tunnel.

Encryption at Rest: The dedicated data volume holding the object store can leverage AWS EBS encryption. Enable EBS encryption when launching the instance or use encrypted snapshots.

### Recon Management Console

The Recon web UI is served on port 80 through nginx. Sign in with the generated credentials to inspect the cluster overview, datanodes, pipelines, containers and storage utilisation.

### Use Cases

• Single-tenant, S3-compatible object storage for applications and backups
• Development and testing against the Ozone and S3 APIs before scaling to a multi-node cluster
• Data-lake and analytics staging storage for Hadoop and Spark workloads
• Proof-of-concept and evaluation of Apache Ozone

### 24/7 cloudimg Support

Technical support by email and live chat covers deployment, S3 gateway and client configuration, capacity and data-volume sizing, scaling toward a multi-node cluster, and Ozone administration.

All product and company names are trademarks or registered trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.