Apache HBase NoSQL Big Data Store

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

## Apache HBase - Production-Ready Distributed NoSQL Store

Deploy a fully configured Apache HBase node on AWS in minutes - not hours. This image delivers HBase preinstalled and running as a managed system service in single-node standalone mode, so you can create tables and store rows immediately after launch, without standing up a multi-node Hadoop and HDFS cluster by hand.

### Why This Image Instead of a DIY Install

• Versus manual EC2 setup: Skip the hours of downloading, checksum-verifying, configuring HBase for standalone operation, writing a systemd unit, provisioning a data disk, and hardening the management console. This image handles all of that at launch.
• Versus a self-managed cluster: Get a single-instance standalone topology - the HBase Master, a RegionServer and an embedded ZooKeeper quorum in one JVM against the local filesystem - that behaves like a real HBase for development, testing, single-tenant stores and proof-of-concept work, with a clean upgrade path to a distributed deployment.
• Versus other community images: Benefit from a hardened first-boot process that generates a unique management password per instance (no shared or default credentials), a dedicated data volume for the store, and 24/7 professional support from cloudimg.

### Application Stack

• Apache HBase installed under /opt/hbase, run by a dedicated unprivileged service account
• One systemd service running the HBase Master, RegionServer and embedded ZooKeeper in standalone mode
• Headless OpenJDK 11 Java runtime
• All table data, the write-ahead log and the embedded ZooKeeper state on a dedicated EBS data volume - independently resizable for IOPS and capacity scaling
• nginx on port 80 publishing the read-only HBase Master status console behind HTTP Basic authentication, plus an unauthenticated health endpoint

### The HBase Data Model

HBase is a wide-column store modeled on Google Bigtable: tables are sparse, distributed, sorted maps indexed by row key, column family and timestamp. Use the HBase shell or the Java, REST and Thrift APIs to create tables, put and get rows, and run scans. It is well suited to very large tables with billions of rows and millions of columns, random real-time read and write access, and append-heavy time-series workloads.

### Security

Secure First Boot: A one-shot service generates a fresh management password per instance, writes it 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 HBase 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.

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

### Master Status Console

The HBase Master status UI is served on port 80 through nginx. Sign in with the generated credentials to inspect the cluster status, the RegionServer, region assignments, tables and storage utilisation.

### Use Cases

• Random real-time read and write access to very large sparse tables
• Development and testing against the HBase API before scaling to a distributed cluster
• Append-heavy time-series and event storage for analytics staging
• Proof-of-concept and evaluation of Apache HBase

### 24/7 cloudimg Support

Technical support by email and live chat covers deployment, schema and data-model design, capacity and data-volume sizing, scaling toward a distributed cluster on HDFS, and HBase 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.