Apache Hop Data Orchestration

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

Overview

Apache Hop (the Hop Orchestration Platform) is an open source data engineering and data orchestration platform for visually designing and running data pipelines and workflows. It provides a browser-based, drag-and-drop editor to build, run and monitor data integration, transformation and orchestration logic, plus a headless execution server for scheduled and remote pipeline runs. This AMI delivers Hop fully installed and configured so a complete data orchestration platform is running within minutes of launch. The current release available is Apache Hop 2.18.1.

Why This AMI Over Alternatives

Unlike a bare Hop installation or a generic community image, this AMI eliminates the manual steps that slow down production readiness:

• No shared default credentials - A one-shot first-boot service generates a unique password per instance and writes it into both the web editor and the execution server, replacing the well-known stock defaults that ship with a manual install.
• Two runtimes, pre-wired - The Hop Web visual editor and the Hop Server execution server are both installed, ordered and supervised by systemd, so you can design a pipeline in the browser and run it on the server without wiring anything together yourself.
• Independently resizable storage - Hop projects, pipelines, workflows and the execution server configuration live on a dedicated EBS data volume, so you can resize storage without rebuilding the instance.
• Immediate productivity - Launch, retrieve your credentials, open the editor and start building pipelines without touching Java configuration, Docker, systemd units or reverse-proxy setup.

Application Stack

Apache Hop is installed from the official Apache distribution. The Hop Web visual editor runs as the official Apache Hop web container, reverse-proxied by nginx on port 80 with HTTP Basic authentication. The Hop Server execution server runs under a dedicated unprivileged service account and is reachable only through its own authenticated endpoint. Both runtimes bind the loopback interface and are fronted with authentication; the Hop projects, pipelines, workflows and server configuration live on a dedicated, independently resizable EBS data volume. Runs on OpenJDK 21.

Secure First Boot

On first boot a one-shot service generates a fresh password unique to that instance, applies it to both the web editor and the execution server, and writes the credentials to a root-only file. No shared or default credentials ship in the image. Because the Hop execution server can run pipelines remotely, replacing its stock default credentials on every instance is essential, and this AMI does it automatically.

Getting Started

1. Launch the AMI on your chosen EC2 instance type.

2. SSH into the instance and retrieve your generated credentials from the root-only file.

3. Browse to the instance public address and sign in to the Hop Web editor.

4. Open the bundled sample project, then design and run your first pipeline.

For evaluation, launch on a smaller instance type to explore the editor and test pipeline logic at minimal cost before scaling up for production workloads.

Example Use Case: Batch ETL Into a Data Warehouse

A data team can use Hop to read from operational databases and flat files, apply cleansing, lookups and transformations visually, and load the results into a warehouse or object storage on a schedule. The Hop Server runs the workflow unattended and exposes execution status, so engineers monitor and adjust pipelines without redeploying code.

Additional Use Cases

• Data integration between databases, APIs, files and cloud storage
• Scheduled and orchestrated multi-step data workflows
• Migration and consolidation of Pentaho/Kettle pipelines
• Reusable, parameterised pipelines promoted across environments

cloudimg Support

24/7 technical support by email and live chat. Our engineers assist with Hop deployment, upgrades, pipeline and workflow design, execution server configuration and performance tuning. Critical issues receive a one-hour average response time.

Apache Hop, Hop and Apache are trademarks of the Apache Software Foundation. All other 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.