Apache Iggy Message Streaming Platform

AWS Streaming & Messaging

persistent message streaming in rust, with a browser console for streams and topics

Base
Hardened build
minimal ports, security patches applied at build time
Access
Unique credentials
generated on first boot, readable only by root
Verified
Boots working
services pass a health gate before release
Support
24/7, 365 days
by email and live chat, 24 hour response SLA

Overview

Apache Iggy is a persistent, high throughput message streaming platform written in Rust. It stores messages as append only segments organised into streams, topics and partitions, and serves them over a fast TCP binary transport and an HTTP REST API, with built in users, authentication and consumer groups. Producers publish messages to topics and consumers read them by offset with consumer groups, so teams can build event driven pipelines, log and telemetry transport, and real time data flows. A web console signs in, browses streams, topics and partitions, and inspects messages, while client SDKs connect over the binary TCP transport or the HTTP API.

Why the cloudimg image

cloudimg packages Apache Iggy and its official web console as a ready to run appliance: the server and console run as managed services behind an nginx reverse proxy, a unique administrator password is generated on first boot and written to a root only file with no default login, stream data lives on a dedicated independently resizable volume, and the image is built on a hardened, fully patched base with a paired step by step deployment guide and 24/7 support.

Common uses

  • Event driven microservices and asynchronous messaging between services
  • High throughput log, metric and telemetry transport into analytics and storage
  • Real time data pipelines and stream processing for events and IoT

Key features

  • Ready-to-use streaming platform on first boot. Apache Iggy - the server and its web console - is installed, configured and running behind nginx. Create a stream and topic, then produce and consume persistent messages over the HTTP REST API or the fast TCP binary transport immediately, with no manual setup.
  • Secure by default where upstream is not. The image ships no baked Iggy password and the well-known iggy/iggy development credential is never set. Every instance generates a unique administrator password on first boot and initialises the Iggy root user with it, writing the plaintext only to a root-only file. The build proves the per-instance credential works and that iggy/iggy and unauthenticated requests are rejected before capture.
  • 24/7 cloudimg support with a one-hour average response for critical issues. Engineers assist via email and live chat with deployment sizing, TLS termination in front of the web console and API, security-group hardening, Iggy configuration and streaming-model guidance, and version upgrades. Stream data lives on a dedicated, independently resizable EBS volume.

See it running

Real screenshots taken while testing this image against its deployment guide.

Apache Iggy Message Streaming Platform screenshot 1 Apache Iggy Message Streaming Platform screenshot 2 Apache Iggy Message Streaming Platform screenshot 3 Apache Iggy Message Streaming Platform screenshot 4

Description

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

## A Working Message Streaming Platform in Minutes

Apache Iggy is a persistent, high-throughput message streaming platform written in Rust. It stores messages as append-only segments organised into streams, topics and partitions, and serves them over a fast TCP binary transport and an HTTP REST API, with users, authentication and consumer groups. This AMI ships Apache Iggy 0.8.0 as a self-contained single-node appliance - the Iggy server and its web console are installed, configured and running behind nginx the moment the instance boots, so you can create a stream, produce messages and consume them straight away.

## Who This Is For

  • Platform and streaming teams who want a lightweight, self-hosted streaming backbone without operating a heavyweight broker cluster
  • Developers building event-driven applications who need a fast persistent log with a simple HTTP and TCP API
  • Evaluators who want a working Iggy environment to explore the streams, topics and consumer-group model before committing

## Application Stack

  • Apache Iggy 0.8.0 - the streaming server, HTTP REST API on loopback and TCP binary transport on port 8090
  • Apache Iggy web console - a browser UI to sign in, browse streams and topics and inspect messages
  • nginx - reverse proxy on port 80, forwarding the web console and the HTTP API same-origin with WebSocket upgrades
  • The Iggy HTTP API and the web console bind to loopback; nginx is the only web surface, and QUIC is disabled to shrink the attack surface

## Secure By Default

Apache Iggy's root user is created only on first server startup against an empty data directory, and upstream development images use a well-known iggy/iggy credential. This image does not ship that:

  • The AMI ships with an empty data volume and no baked Iggy password
  • Every instance generates its own administrator password on first boot and initialises the Iggy root user with it
  • The plaintext password is written to a root-only credentials file, so no shared or default credential exists in the image
  • The well-known iggy/iggy development credential is never set, and the build proves it is rejected before the image is captured

## Production-Grade Storage Layout

Stream data - the append-only segments, topics, partitions and the users store - lives on a dedicated gp3 EBS volume mounted at /var/lib/iggy and bind-mounted into the server, kept off the OS disk and independently resizable. A customer instance reproduces the identical layout on first boot.

## 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 and sign in as the Iggy root user

4. Create a stream and a topic, then send and consume messages over the HTTP API or connect an Iggy SDK client to the TCP transport on port 8090

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)
  • Storage: OS disk plus a dedicated gp3 volume for stream data, independently resizable
  • Networking: open port 80 for the web console and port 8090 for the Iggy TCP transport in your security group, ideally restricted to your own client address ranges; the raw HTTP API is loopback only

## 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, TLS termination in front of the web console and API, security-group and network hardening, Iggy configuration and streaming-model guidance, and 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 Iggy and terminate at any time with no long-term commitment.

Apache Iggy is a trademark 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.

Related technologies

message streamingmessage brokerevent streamingpersistent streamsrust streaming servermessage queueevent drivenappend only logstream processingtcp transportpub subconsumer groupsiot telemetryreal time ingestionlightweight broker