Apache Ignite In-Memory Database

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

## Overview

Apache Ignite is the open source distributed in-memory database and compute platform that stores data as key-value entries and queryable SQL tables across a cluster, serving reads and writes at memory speed. This AMI delivers a fully configured, security-hardened single Ignite node with native persistence, ready to accept authenticated SQL and thin-client connections within minutes of launch - eliminating the hours of manual installation, Java tuning, and authentication setup a bare install demands.

## Why This Image Over Alternatives

Unlike community Ignite builds that leave authentication disabled and cluster ports wide open - so anyone on the network can read, write, or run compute tasks against the grid - this image enables Ignite authentication and binds every data-grid port to loopback only. The thin-client SQL port, discovery, and communication ports are never exposed on the security group; remote access is over an SSH tunnel or a private network you control. Native persistence lives on a dedicated, independently resizable data volume rather than the OS disk, so data survives restarts and backups stay simple.

## What Is Included

• Apache Ignite installed from the official Apache binary release, running as a single node with native persistence
• OpenJDK 11 runtime with the JVM flags Ignite requires
• Bundled control.sh and sqlline.sh CLIs for cluster administration and SQL
• Dedicated data volume for the work directory, persistence store, and write-ahead log
• Authentication enabled with a unique credential generated on first boot

## Secure First Boot

On first boot a one-shot service activates the cluster, generates a cryptographically strong password unique to that instance, applies it to the Ignite authentication subsystem, and writes it to a file readable only by root. The default ignite credential is rotated away and no shared or default database password ever ships in the image.

## AWS Integration Points

• Amazon EBS - Ignite native persistence lives on a dedicated EBS volume; use EBS Snapshots for point-in-time backups or resize storage independently of the OS disk.
• Amazon VPC - Deploy within private subnets and control access with security groups; the data-grid ports are loopback-only by default and reached over an SSH tunnel or private ENI.
• Amazon CloudWatch - Forward Ignite JVM and system logs to CloudWatch for centralized monitoring and alerting.
• AWS Backup - Schedule automated, policy-driven backups of the data volume without custom scripting.

## Ready To Use

Connect over SSH, read the generated password, and open sqlline to create caches and tables, insert data, and query it back. The node runs as a single-node cluster by default; expand to a multi-node cluster by binding Ignite to a private address and updating the discovery configuration.

## Use Cases

• Distributed caching - Put a memory-speed cache in front of a slower system of record to cut latency for read-heavy web and mobile backends.
• In-memory SQL analytics - Run ad hoc and operational SQL over a distributed, memory-resident dataset for fast dashboards and reporting.
• High-throughput key-value store - Serve session state, user profiles, and feature data with predictable low latency.
• Compute grid workloads - Co-locate computation with data for parallel processing close to where it lives.

## cloudimg Support

24/7 technical support by email and live chat. Our engineers assist with deployment, cluster expansion, data modeling, performance tuning, and administration. Critical issues receive a one-hour average response time.

To discuss your architecture or plan a multi-node deployment, contact our team through the support channels listed below.

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.