Limits
Ceilings, timeouts and known gaps that bound what a run can do.
These are design values, not measured capacity. No throughput benchmarks are published.
S3
| Path | Limit |
|---|---|
| Worker relay | One-hour cooperative deadline per mapping; refused when selected bytes plus 1 GiB exceed free space; one mapping stages per staging root at a time |
| Server-side copy | Refused above 2,000,000 listed objects, 10,000 selected objects or 30,000 planned requests per mapping, or an object over 48.8 TiB; multipart from 8 MiB |
| S3 Batch | 5 GiB per object for Copy (AWS limit); manifest up to 32 GiB; scan ceilings of 10,000,000 entries per side |
| Local upload | Up to 100 GiB per file; multipart from 16 MiB; presigned URLs live 5 minutes |
CodeCommit
Clone and fetch time out at 2,700 seconds; push timeout scales with size (900 seconds per GiB, at most 10,800). Mirror warns at 2,048 MiB and aborts above 4,000 destination refs. Incremental pushes go in batches of 25 refs.
DynamoDB
A full Scan per mapping (consumes read capacity; no snapshot isolation), an
approximate item-count precheck, and a TTL exclusion window of up to 1,825
days before the cutoff.
ECR
Referrer traversal stops at 100 pages or 5,000 rows and 1,000 graph nodes. Copy timeouts scale with image size.
Platform
- One backend process and one sync worker; running several replicas is not supported.
- Run logs keep 5,000 lines per run and 200,000 rows overall.
- Browser sessions last about 30 days; AWS SSO storage defaults to 8 hours.
Known gaps
- No scheduling, and no external notifications or webhooks.
- No signature trust verification for images, and no S3 content checksums.
- No automatic restore of archived objects.
- AWS China and GovCloud partitions are not supported.
- No multi-cloud or generic registry support.
- English only; desktop browser widths only.