Douklar 4.0.0, 23 October 2026.A new CLI, douklar, and retry of unfinished objects from a finished S3 Batch job.Read the release notes

Douklar

Douklar and native ECR and S3 replication

Replication keeps a destination current with every new push or write; Douklar moves what already exists, once.

Douklar console Sync page: a Scope, Review, Run stepper with a cross-account source account and one selected target account.Douklar console Sync page: a Scope, Review, Run stepper with a cross-account source account and one selected target account.

Sync

  • Every run goes through three steps: choose the scope, review the plan, then run it.

  • Pick the mode. Regions for ECR, CodeCommit and DynamoDB are set here; S3 bucket Regions are found for you.

  • One run can copy to more than one target account.

Captured from the console with sample data.

Which to use

Native ECR and S3 replication
Use replication for a copy that stays current.
Douklar
Use Douklar for a one-time move of what is already there, such as a split, a promotion or a carve-out.

What it does

Amazon ECR replication and S3 Replication copy new images and new objects to another Region or account as they arrive. The source account’s owner sets them up.

Where it is the better tool

  • They are managed by AWS and run continuously, with nothing to host.
  • They are the right tool when a destination must stay in step with every new push or write.

Where Douklar is different

  • ECR replication does not backfill images that already exist, and it does not rename repositories. Douklar copies selected existing tags, with their referrers, and can rename on the way.
  • Douklar works from one profile in each account, so the accounts do not have to share an Organization or an owner.
  • One Douklar run can carry ECR, S3, CodeCommit and DynamoDB together, with one record of the run.

Keyboard shortcuts

g h
Home
g c
The console
g m
Use cases
g d
Docs
g r
Releases
/ or Ctrl K
Search the docs (on docs pages)
t
Switch light and dark
?
Show this list