An Amazon ECR private repository contains your Docker images, Open Container Initiative (OCI) images, and OCI compatible artifacts. You can create, monitor, and delete image repositories and set permissions that control who can access them by using Amazon ECR API operations or the Repositories section of the Amazon ECR console. Amazon ECR also integrates with the Docker CLI, so that you can push and pull images from your development environments to your repositories.
Topics
Private repository concepts
-
By default, your account has read and write access to the repositories in your default registry (
aws_account_id.dkr.ecr.region.amazonaws.com -
Repositories can be controlled with both user access policies and individual repository policies. For more information, see Private repository policies in Amazon ECR.
-
Repository names can support namespaces, which you can use to group similar repositories. For example, if there are several teams using the same registry, Team A can use the
team-anamespace, and Team B can use theteam-bnamespace. By doing this, each team has their own image calledweb-appwith each image prefaced with the team namespace. This configuration allows these images on each team to be used simultaneously without interference. Team A's image isteam-a/web-app, and Team B's image isteam-b/web-app. -
Your images can be replicated to other repositories across Regions in your own registry and across accounts. You can do this by specifying a replication configuration in your registry settings. For more information, see Private registry settings in Amazon ECR.
