Apache Storm - Real-Time Stream Processing , cloudimg Support

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

## A Working Stream Processing Cluster in Minutes

Apache Storm is a distributed, fault-tolerant, real-time computation system used to process unbounded streams of data with low latency. This AMI ships a complete single-node Storm cluster - Nimbus, a Supervisor, the Storm UI and a bundled Apache ZooKeeper coordination service - already installed, configured and running the moment the instance boots. Submit topologies of spouts and bolts, watch tuples flow through the topology in real time, and monitor throughput, latency and worker health from the web UI.

## Who This Is For

• Data and platform engineering teams who need a running Storm cluster to develop and test streaming topologies without hand-rolling a deployment
• Developers learning Storm's spout and bolt programming model against a real cluster
• Operations teams running low-latency event processing, real-time analytics, continuous ETL or online machine learning pipelines
• Evaluators who want a working Storm environment to explore before committing to a multi-node cluster

## Application Stack

• Apache Storm 2.7.1 - Nimbus (master), Supervisor (worker with four worker slots) and the Storm UI
• Apache ZooKeeper 3.9.3 - single-node coordination service Storm requires
• nginx - reverse proxy on port 80 fronting the Storm UI with HTTP Basic authentication
• OpenJDK 17 runtime; Storm, ZooKeeper and the UI bind to loopback, nginx is the only external surface

## Secure By Default

The Storm UI and Nimbus Thrift API ship upstream with no authentication, and Nimbus can submit or kill topologies - a privileged control plane. This image does not leave that exposed:

• The Storm UI is bound to loopback and fronted by nginx with HTTP Basic authentication
• A loopback-only firewall keeps ZooKeeper, Nimbus Thrift, the Storm UI and worker slots unreachable off the instance regardless of security group
• Every instance generates its own administrator password on first boot, written to a root-only credentials file
• No shared or default credential exists in the AMI

## Ready To Explore On First Boot

First boot submits the bundled storm-starter WordCount topology, so the Storm UI shows a genuine running topology processing tuples immediately - real emitted and transferred counts to explore. Kill the demonstration topology and submit your own whenever you are ready.

## Getting Started

1. Launch the AMI on an m5.large instance or larger

2. SSH into the instance and read the generated administrator password from the root-only credentials file

3. Open your browser to the instance public address on port 80

4. Sign in as administrator and open the Storm UI

5. Watch the running WordCount topology, then submit your own topologies with the storm CLI

For a detailed walkthrough, see the user guide linked in the Additional Resources section.

## Recommended Instance Sizing

• Recommended: m5.large (2 vCPU, 8 GiB RAM) - comfortable for the Nimbus, Supervisor, UI and ZooKeeper JVMs
• Storage: OS disk plus one dedicated 30 GiB gp3 volume for Storm and ZooKeeper state, independently resizable
• Networking: open ports 80 and 443 in your security group for browser access; Storm, Nimbus and ZooKeeper are loopback only

## Use Case: Real-Time Event Processing

A team needs to enrich and aggregate a high-volume event stream with sub-second latency. They launch this AMI, develop a topology of spouts that read the stream and bolts that transform and aggregate it, submit it to Nimbus, and watch the Storm UI report per-bolt throughput and latency. Storm reschedules failed tasks automatically, so the pipeline keeps running as workers come and go.

## 24/7 cloudimg Support

Every deployment is backed by cloudimg engineers available around the clock via email and live chat. Support covers:

• Initial deployment and instance sizing guidance
• Scaling from this single-node cluster to a multi-node Storm and ZooKeeper deployment
• Topology submission, tuning parallelism, and troubleshooting worker and supervisor issues
• Storm UI authentication and TLS termination with Let's Encrypt or your own certificates
• ZooKeeper configuration, retention and troubleshooting
• Apache Storm and ZooKeeper version upgrades

Critical issues receive a one-hour average response time.

## Evaluation

This AMI uses standard AWS pay-as-you-go infrastructure billing. Launch an instance to evaluate Apache Storm, and terminate at any time with no long-term commitment.

Apache Storm and Apache ZooKeeper are trademarks of the Apache Software Foundation. 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.