Douklar docs

What Douklar is, what it moves, how a move works, and what it deliberately does not do.

From install to a recorded run in Activity, one S3 bucket from one account to another, in about ten minutes.

Run the Douklar stack on one Linux host with Docker, then sign in to the console.

One profile per AWS account, its credentials, and the checks that keep them valid.

Find the resources in each account and map each source to its destination.

The read-only checks that run before any write, and the review step that lists what will be written.

How a reviewed run is queued, executed, verified and retried.

The durable record of every run, and how to re-run or retry from it.

The dedicated console for large S3 copies with AWS S3 Batch Operations, from readiness to completion report.

When a move needs a permission in an account you do not run, Douklar shows the exact statement for that account's admin to apply.

Choose the identity provider for the console, set the values Douklar reads, and map your admin group.

Keep Douklar's state in Amazon RDS, Supabase or another PostgreSQL instead of the local container.

Plan and run syncs, manage config and verify ECR mappings from a terminal.

Every area of the web console, what you do there, and which role can open it.

The files Douklar reads and the environment variables an operator sets most often, with their defaults.

What each profile needs in AWS, read and write, for discovery, preflight and each kind of move.

The error codes the console's API returns, with the HTTP status, whether a retry can help, and what to do.

Ceilings, timeouts and known gaps that bound what a run can do.

The words Douklar uses, and what each one means in the product.

What happens between pressing Run and reading the record: the queue, the worker, the states a run can end in, and where the bytes go.

Symptom, check, fix for the problems the install and the first runs meet most often.