Amazon ECR vs Harbor
Comparing Amazon ECR with self-hosted Harbor: IAM against Harbor projects, RBAC and OIDC, image scanning, replication and pull-through caching, where each registry can run, and the operating work Harbor adds.
Amazon ECR
Amazon Elastic Container Registry is AWS's managed container registry, billed for storage and data transfer; these pages cover running a self-hosted Harbor registry instead, for hybrid, multi-cloud or on-premises estates.
Migrate from Amazon ECR to Harbor
Moving images from Amazon ECR to Harbor using Harbor's pull-based replication from an AWS ECR endpoint: filtering repositories and tags, credentials, cutting over Kubernetes image references and CI push targets, and lifecycle policies to re-create.
Amazon ECR cost vs self-hosted Harbor
Cost of ownership by component: ECR storage and cross-region or internet data transfer against Harbor's servers, object storage, database, backups and the people who run it, with the cases where ECR stays cheaper.
Self-hosted Amazon ECR alternative for hybrid and multi-cloud
For estates that run clusters on premises or across several clouds: why one self-hosted Harbor registry, replicating to and caching from cloud registries, can replace per-cloud registries, and what ECR still does better inside AWS.
