OLake - Database to Lakehouse Replication

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

## Database to Lakehouse Replication in Minutes

OLake is an open source ETL and change data capture platform that continuously moves data out of operational databases such as PostgreSQL, MySQL, MongoDB, Oracle, and SQL Server and lands it in Apache Iceberg or as Parquet in object storage, where analytics engines can query it directly. Everything is driven from a web console: register a source, register a destination, discover the tables and columns available, choose which streams to replicate and in which mode, then run the job and watch its history. OLake supports both full refresh loads and change data capture (CDC), which reads the database write-ahead log so inserts, updates, and deletes stream into the lakehouse continuously without rescanning the source.

## Useful the Moment It Boots

To make the platform demonstrable immediately, the image bundles both ends of a pipeline: a demo PostgreSQL source seeded on first boot with a synthetic dataset generated on the instance itself, and an S3-compatible object store destination, both already registered in the console. A real end-to-end replication can be run within minutes of boot and before any of your own systems are connected. This built-in evaluation environment lets you validate the full workflow - source discovery, stream selection, job execution, and history review - without provisioning external infrastructure.

## Application Stack

• OLake 0.4.9 - React web console, API, and worker, run as official upstream containers pinned by digest
• Temporal - workflow engine with a PostgreSQL-backed visibility store (no Elasticsearch)
• PostgreSQL 16 - Temporal metadata store plus a separate bundled demo source
• SeaweedFS - Apache-2.0 S3-compatible object store as the demo lakehouse destination
• nginx - reverse proxy on port 80, the single public front door; every backend binds to loopback or the docker gateway

## Secure by Default

Upstream ships published default credentials and an empty credential encryption key. This image ships none of them. Every instance generates its own console administrator password, database passwords, credential encryption key, and object storage key pair on first boot, written to a root-only file, so no two instances share a login and none of the published defaults survive anywhere in the image. The console refuses unauthenticated requests, and each component is pinned by image digest so what you run is exactly what was built, tested, and scanned.

## AWS Integration

Container image layers and volumes live on a dedicated, independently resizable EBS data volume rather than the OS disk, giving you flexibility to scale storage as replication workloads grow. OLake writes Parquet and Apache Iceberg output to S3-compatible storage, making it straightforward to point the destination at Amazon S3 for production lakehouse architectures queried by Amazon Athena, Amazon Redshift Spectrum, or other analytics engines.

## Get Started

Launch the AMI, retrieve your unique per-instance credentials from the root-only credentials file, log into the web console, and run your first replication against the bundled demo source in minutes. When you are ready for production, register your own database sources and point the destination at your S3 bucket. Every deployment is backed by 24/7 cloudimg support and a paired step-by-step deployment guide to help you through initial setup and ongoing operations.