# Amazon Elastic Container Registry (Amazon ECR)

Cloud service · AWS. Updated 2026-11-12. Page: https://blowstack.com/tools/cloud-services-hub/amazon-elastic-container-registry-(amazon-ecr)

> Amazon Elastic Container Registry (Amazon ECR) is a fully managed Docker container registry that makes it easy for developers to store, manage, and deploy Docker container images.

Practice exams covering Amazon Elastic Container Registry (Amazon ECR): [CLF-C02 AWS Certified Cloud Practitioner](https://blowstack.com/practice-exams/aws-certified-cloud-practitioner), [SOA-C03 AWS Certified CloudOps Engineer - Associate](https://blowstack.com/practice-exams/aws-certified-cloudops-engineer-associate), [DVA-C02 AWS Certified Developer - Associate](https://blowstack.com/practice-exams/aws-certified-developer-associate), [DOP-C02 AWS Certified DevOps Engineer - Professional](https://blowstack.com/practice-exams/aws-certified-devops-engineer-professional), [MLA-C02 (beta) AWS Certified Machine Learning Engineer - Associate](https://blowstack.com/practice-exams/aws-certified-machine-learning-engineer-associate), [SCS-C03 AWS Certified Security - Specialty](https://blowstack.com/practice-exams/aws-certified-security-specialty), [SAA-C03 AWS Certified Solutions Architect - Associate](https://blowstack.com/practice-exams/aws-certified-solutions-architect-associate), [SAP-C02 AWS Certified Solutions Architect - Professional](https://blowstack.com/practice-exams/aws-certified-solutions-architect-professional).

## 9 key features of Amazon Elastic Container Registry (Amazon ECR)

Amazon Elastic Container Registry (Amazon ECR) is a fully managed Docker container registry that allows users to easily store, manage, and deploy Docker container images.

1. **Fully Managed**: Amazon ECR is a fully managed container registry that makes it easy for developers to store, manage, and deploy Docker container images. It eliminates the need to operate your own container repositories or worry about scaling the underlying infrastructure.
2. **Highly Scalable**: ECR can scale seamlessly to meet your development workflow's demand, regardless of the volume of container images or the frequency of requests. This ensures that your deployment scales efficiently with your application.
3. **Integrated with Amazon ECS and EKS**: ECR is deeply integrated with Amazon Elastic Container Service (ECS) and Amazon Elastic Kubernetes Service (EKS), providing a simplified development workflow where you can easily push your images to ECR and pull them directly from your Amazon ECS or EKS clusters.
4. **Private Registries**: ECR provides private container registries that allow you to host your Docker images in a secure and scalable environment. You can control access to your images using AWS Identity and Access Management (IAM) policies.
5. **Security Scanning**: Amazon ECR supports automatic scanning for operating system vulnerabilities and scans initiated through an API command. Enhanced image scanning can be enabled through Amazon Inspector.
6. **Cross-Region Replication**: ECR supports cross-region replication enabling automatic replication of your container images to other AWS Regions. This improves the load times of your applications and enhances disaster recovery strategies.
7. **Immutable Image Tags**: ECR supports immutable image tags, which prevent image tags from being overwritten. This ensures that your deployments are consistent and reduces the risk of accidental overwrites of working container images.
8. **Lifecycle Policies**: You can define rules that clean up older images automatically, ensuring efficient usage of storage and keeping your repositories organized. Lifecycle policies help in managing the lifecycle of images stored in your registry, such as expiring old images based on specific criteria.
9. **Encrypted at Rest and In-Transit**: Amazon ECR automatically encrypts images at rest using Amazon S3 server-side encryption or AWS KMS encryption and transfers container images over HTTPS.

## Where Amazon Elastic Container Registry (Amazon ECR) is used

Amazon Elastic Container Registry (Amazon ECR) enables secure, scalable, and efficient storage, management, and deployment of container images for applications running on a wide range of AWS services and on-premises environments.

1. **Continuous Integration and Continuous Deployment (CI/CD)**: Amazon ECR can be integrated with CI/CD pipelines to automate the build, test, and deployment process of containerized applications. Developers can push their Docker or OCI images to ECR after a successful build, and orchestration services like Amazon ECS or Kubernetes can pull these images to deploy updates automatically.
2. **Secure Storage of Container Images**: Amazon ECR provides a secure location to store, manage, and deploy Docker and Open Container Initiative (OCI) images. It uses AWS Identity and Access Management (IAM) to control access to the images, ensuring that only authorized users or services can push or pull images. ECR also offers vulnerability scanning to detect security issues within your images.
3. **Application Version Control and Rollbacks**: By leveraging ECR, teams can easily manage different versions of their container images, allowing for easy rollbacks to previous versions in case of failures or issues with the latest deployments. ECR supports image tagging, which simplifies the process of version control and deployment strategies like canary or blue-green deployments.
4. **Geographically Distributed Deployments**: ECR can replicate container images across multiple AWS regions, facilitating faster image pulls for geographically distributed applications and reducing latency. This capability supports building highly available, fault-tolerant applications and ensures that global users experience minimal delays.
5. **Easy Integration with AWS Ecosystem**: ECR seamlessly integrates with other services in the AWS ecosystem, such as Amazon Elastic Container Service (ECS), Amazon Elastic Kubernetes Service (EKS), AWS Lambda for serverless applications, and AWS Fargate for running containers without managing servers. This integration allows for a smooth deployment process and easy scaling of applications as needed.

## How Amazon Elastic Container Registry (Amazon ECR) is priced

Amazon ECR pricing is based on the amount of data stored in your repositories and the data transferred to the internet, with no upfront fees or commitments, and offers a free tier for certain amounts of storage and data transfer.

- **Data Transfer**: Amazon ECR charges for data transferred to the internet. Transfer from a private repository is billed to the AWS account that owns it. Transfer from a public repository is free up to the applicable limits; beyond those limits, it is billed to the AWS account downloading from the repository.
- **Storage Pricing**: ECR charges a monthly fee for the storage space your container images occupy. This fee is based on the amount of data stored, measured in gigabytes per month.
- **Image Scanning**: Amazon ECR offers image scanning on push to detect vulnerabilities. Basic image scanning is free. Enhanced scanning through Amazon Inspector charges for initial image scans and eligible rescans, and the cost is based on the number of images scanned.
- **Archive Storage and Retrieval**: Archive storage has a minimum billable duration of 90 days; deleting an image earlier incurs a prorated charge for the remaining days. Retrieving archived images incurs a per-GB retrieval charge.
- **Managed Signing**: ECR managed signing is charged per successfully generated image signature. Failed signing attempts, including failures caused by misconfigured permissions, are not charged.
- **KMS and Dual-Layer Encryption**: SSE-KMS incurs AWS KMS charges for generating or retrieving data keys. DSSE-KMS incurs those KMS charges plus an additional per-GB fee for its second encryption and decryption layer.
- **AWS Free Tier**: Starting July 15, 2025, new AWS customers can receive up to $200 in Free Tier credits applicable to eligible services including ECR. The free plan lasts six months after account creation, and credits must be used within 12 months of account creation.

## Services Amazon Elastic Container Registry (Amazon ECR) works with

- **[Amazon Elastic Kubernetes Service (Amazon EKS)](https://blowstack.com/tools/cloud-services-hub/amazon-elastic-kubernetes-service-(amazon-eks))**: Amazon EKS integrates with Amazon ECR to store and retrieve container images for Kubernetes clusters.
- **[AWS Fargate](https://blowstack.com/tools/cloud-services-hub/aws-fargate)**: AWS Fargate integrates with Amazon ECR to pull container images required to run serverless container-based applications.
- **[Amazon Elastic Container Service (Amazon ECS)](https://blowstack.com/tools/cloud-services-hub/amazon-elastic-container-service-(amazon-ecs))**: Amazon ECS uses Amazon ECR to store and retrieve Docker container images for your applications.
- **[AWS Identity and Access Management (IAM)](https://blowstack.com/tools/cloud-services-hub/aws-identity-and-access-management-(iam))**: IAM integrates with Amazon ECR to manage access permissions for container repositories.
- **[AWS CodePipeline](https://blowstack.com/tools/cloud-services-hub/aws-codepipeline)**: AWS CodePipeline uses Amazon ECR to automate build, test, and deploy cycles for containerized applications.
- **[AWS CodeBuild](https://blowstack.com/tools/cloud-services-hub/aws-codebuild)**: AWS CodeBuild can use Amazon ECR to retrieve and push Docker images as part of a continuous integration process.
- **[Amazon CloudWatch](https://blowstack.com/tools/cloud-services-hub/amazon-cloudwatch)**: Amazon CloudWatch integrates with Amazon ECR to provide monitoring, logging, and alerting for container repositories.
- **[AWS CloudTrail](https://blowstack.com/tools/cloud-services-hub/aws-cloudtrail)**: AWS CloudTrail integrates with Amazon ECR to log API calls and track changes made to container repositories.
- **[AWS Lambda](https://blowstack.com/tools/cloud-services-hub/aws-lambda)**: AWS Lambda can use container images stored in Amazon ECR to run serverless functions.
- **[Amazon S3](https://blowstack.com/tools/cloud-services-hub/amazon-s3)**: Amazon S3 can be used with Amazon ECR to store and retrieve large amounts of image layers and artifacts.
- **[AWS Secrets Manager](https://blowstack.com/tools/cloud-services-hub/aws-secrets-manager)**: AWS Secrets Manager integrates with Amazon ECR to securely manage and retrieve container registry credentials.
- **[Amazon VPC](https://blowstack.com/tools/cloud-services-hub/amazon-vpc)**: Amazon VPC integrates with Amazon ECR to enable private connections to the container registry.
- **[Amazon Bedrock AgentCore](https://blowstack.com/tools/cloud-services-hub/amazon-bedrock-agentcore)**: Amazon ECR stores container images for agents deployed to Amazon Bedrock AgentCore Runtime. AgentCore retrieves the image specified for a runtime and uses it to run the agent.
- **[Amazon Braket](https://blowstack.com/tools/cloud-services-hub/amazon-braket)**: Amazon ECR stores custom container images for Amazon Braket Hybrid Jobs. A hybrid job can reference an ECR image containing its algorithm code and required libraries.
- **[Amazon Corretto](https://blowstack.com/tools/cloud-services-hub/amazon-corretto)**: Amazon ECR Public distributes official Amazon Corretto container images. These images provide Java runtimes that can be used directly or as base images for containerized applications.
- **[Amazon EC2](https://blowstack.com/tools/cloud-services-hub/amazon-ec2)**: Amazon ECR supplies container images to container runtimes on EC2 instances. Instance IAM roles can grant permission to authenticate to ECR and pull images without storing long-term AWS credentials on the instances.
- **[Amazon ECS Anywhere](https://blowstack.com/tools/cloud-services-hub/amazon-ecs-anywhere)**: Amazon ECR supplies images for ECS Anywhere tasks running on external servers. Task execution roles authorize the ECS agent to pull private images from ECR.
- **[Amazon EKS Anywhere](https://blowstack.com/tools/cloud-services-hub/amazon-eks-anywhere)**: Amazon ECR Public hosts EKS Anywhere component images, and EKS Anywhere workloads can also pull application images from ECR repositories. Private application images require appropriate ECR authentication and repository permissions.
- **[Amazon EKS Distro](https://blowstack.com/tools/cloud-services-hub/amazon-eks-distro)**: Amazon ECR Public hosts the Kubernetes component images published with Amazon EKS Distro releases. Deployments can pull these versioned images to run the corresponding Kubernetes distribution.
- **[Amazon EMR](https://blowstack.com/tools/cloud-services-hub/amazon-emr)**: Amazon ECR stores custom images for Amazon EMR on EKS and EMR Serverless. These images can package application dependencies and runtime customizations that EMR uses when executing jobs.
- **[Amazon EventBridge](https://blowstack.com/tools/cloud-services-hub/amazon-eventbridge)**: Amazon ECR sends events to EventBridge for operations such as image pushes, image scans, replication, and pull-through cache activity. EventBridge rules can route matching events to targets that notify operators or automate deployment and remediation.
- **[Amazon GameLift](https://blowstack.com/tools/cloud-services-hub/amazon-gamelift)**: Amazon ECR stores game-server container images used by Amazon GameLift container fleets. GameLift container group definitions reference these images when deploying and scaling containerized game servers.
- **[Amazon GuardDuty](https://blowstack.com/tools/cloud-services-hub/amazon-guardduty)**: Amazon ECR hosts security-agent container images used by GuardDuty Runtime Monitoring for supported ECS and EKS environments. Those environments need access to the relevant ECR repositories to retrieve the agent images.
- **[Amazon Inspector](https://blowstack.com/tools/cloud-services-hub/amazon-inspector)**: Amazon ECR enhanced scanning uses Amazon Inspector to identify vulnerabilities in operating-system and supported programming-language packages within container images. Inspector can continuously rescan eligible images as vulnerability information changes.
- **[Amazon Lightsail](https://blowstack.com/tools/cloud-services-hub/amazon-lightsail)**: Amazon ECR Public can supply public images for Lightsail container service deployments. A Lightsail deployment references the public image URI to launch the application container.
- **[Amazon SageMaker](https://blowstack.com/tools/cloud-services-hub/amazon-sagemaker)**: Amazon ECR stores the built-in and custom container images that SageMaker uses for training, processing, and inference. SageMaker job and model configurations reference ECR image URIs to select their execution environments.
- **[Amazon SageMaker Data Wrangler](https://blowstack.com/tools/cloud-services-hub/amazon-sagemaker-data-wrangler)**: Amazon ECR hosts Data Wrangler processing container images used to execute data-preparation flows. Exported flows can run as SageMaker Processing jobs using the appropriate Data Wrangler image.
- **[AWS Amplify](https://blowstack.com/tools/cloud-services-hub/aws-amplify)**: Amazon ECR Public can host custom build images for Amplify Hosting. Amplify uses the configured image to provide the operating-system packages and build tools required by an application's build.
- **[AWS App Runner](https://blowstack.com/tools/cloud-services-hub/aws-app-runner)**: Amazon ECR supplies container images for App Runner services. App Runner can automatically deploy new images pushed to supported same-account private ECR sources, or deploy images through manually initiated deployments.
- **[AWS Audit Manager](https://blowstack.com/tools/cloud-services-hub/aws-audit-manager)**: Amazon ECR repository compliance evaluations can become automated audit evidence in Audit Manager through AWS Config and Security Hub integrations. This supports controls covering settings such as image scanning and tag immutability.
- **[AWS Batch](https://blowstack.com/tools/cloud-services-hub/aws-batch)**: Amazon ECR stores container images referenced by AWS Batch job definitions. Batch compute environments pull these images when starting jobs, with IAM permissions controlling access to private repositories.
- **[AWS Clean Rooms](https://blowstack.com/tools/cloud-services-hub/aws-clean-rooms)**: Amazon ECR stores custom machine-learning algorithm images used by AWS Clean Rooms ML. Configured model algorithms reference ECR images that provide the code and dependencies for collaborative model training.
- **[AWS CloudFormation](https://blowstack.com/tools/cloud-services-hub/aws-cloudformation)**: CloudFormation provisions Amazon ECR repositories and registry configuration as managed resources. Templates can define repository policies, lifecycle policies, encryption, image scanning, replication, and other supported settings.
- **[AWS CodeDeploy](https://blowstack.com/tools/cloud-services-hub/aws-codedeploy)**: Amazon ECR stores application images referenced by ECS task definitions used in CodeDeploy blue/green deployments. CodeDeploy deploys replacement ECS task sets using those definitions and shifts traffic to the new application version.
- **[AWS Config](https://blowstack.com/tools/cloud-services-hub/aws-config)**: AWS Config records supported Amazon ECR repository configurations and evaluates them against compliance rules. Managed rules can check settings such as image scanning, tag immutability, lifecycle policies, and encryption.
- **[AWS Control Tower](https://blowstack.com/tools/cloud-services-hub/aws-control-tower)**: Control Tower provides controls for Amazon ECR repository security settings. Its proactive controls can reject CloudFormation deployments that do not meet requirements such as image scanning or immutable image tags.
- **[AWS Deep Learning Containers](https://blowstack.com/tools/cloud-services-hub/aws-deep-learning-containers)**: Amazon ECR distributes AWS Deep Learning Containers with preconfigured machine-learning frameworks and dependencies. Training and inference platforms pull these images to run supported deep-learning workloads.
- **[AWS Distro for OpenTelemetry](https://blowstack.com/tools/cloud-services-hub/aws-distro-for-opentelemetry)**: Amazon ECR Public hosts AWS Distro for OpenTelemetry Collector images. Container deployments pull these images to run collectors that receive, process, and export application telemetry.
- **[AWS Elastic Beanstalk](https://blowstack.com/tools/cloud-services-hub/aws-elastic-beanstalk)**: Amazon ECR supplies private container images to Elastic Beanstalk Docker environments. The environment's EC2 instance profile authorizes image pulls when Elastic Beanstalk deploys or updates the application.
- **[AWS Fault Injection Service](https://blowstack.com/tools/cloud-services-hub/aws-fault-injection-simulator-(aws-fis))**: Amazon ECR hosts helper container images used by supported AWS Fault Injection Service actions against EKS pods. Cluster nodes must be able to retrieve these images for the fault-injection actions to run.
- **[AWS Glue](https://blowstack.com/tools/cloud-services-hub/aws-glue)**: Amazon ECR Public distributes AWS Glue development container images. These images provide Glue libraries and dependencies for developing and testing ETL scripts locally.
- **[AWS IoT Greengrass](https://blowstack.com/tools/cloud-services-hub/aws-iot-greengrass)**: Amazon ECR supplies private container images to Greengrass Docker components. The Greengrass Docker application manager uses the core device's AWS permissions to obtain ECR credentials and download the required images.
- **[AWS IoT SiteWise](https://blowstack.com/tools/cloud-services-hub/aws-iot-sitewise)**: Amazon ECR supplies container images used by SiteWise Edge data-processing components. SiteWise Edge gateways use their Greengrass permissions to authenticate to ECR and retrieve the required images.
- **[AWS Key Management Service (AWS KMS)](https://blowstack.com/tools/cloud-services-hub/aws-key-management-service-(aws-kms))**: Amazon ECR can encrypt repository contents using AWS KMS keys. ECR uses KMS grants to encrypt images as they are stored and decrypt them when authorized clients retrieve them.
- **[AWS Marketplace](https://blowstack.com/tools/cloud-services-hub/aws-marketplace)**: Amazon ECR stores container images delivered through AWS Marketplace container products. Sellers submit their product images through the Marketplace publishing workflow, and authorized buyers retrieve the images for deployment.
- **[AWS Organizations](https://blowstack.com/tools/cloud-services-hub/aws-organizations)**: Amazon ECR repository policies can use AWS Organizations condition keys to restrict access to accounts in a particular organization or organizational unit. This allows centralized repositories to serve approved organizational accounts without listing every account individually.
- **[AWS PrivateLink](https://blowstack.com/tools/cloud-services-hub/aws-privatelink)**: Amazon ECR supports interface VPC endpoints powered by AWS PrivateLink for its API and Docker registry endpoints. These endpoints let workloads access private repositories without sending registry traffic through an internet gateway.
- **[AWS Resource Groups and Tag Editor](https://blowstack.com/tools/cloud-services-hub/aws-resource-groups-and-tag-editor)**: Amazon ECR repositories can be organized into tag-based resource groups. Tag Editor can find supported ECR repositories and manage their tags alongside other AWS resources.
- **[AWS Security Hub](https://blowstack.com/tools/cloud-services-hub/aws-security-hub)**: Security Hub evaluates Amazon ECR repository security settings through controls covering areas such as scanning, tag immutability, lifecycle policies, and encryption. It can also consolidate Inspector vulnerability findings for ECR images.
- **[AWS Security Token Service (AWS STS)](https://blowstack.com/tools/cloud-services-hub/aws-security-token-service-(aws-sts))**: Amazon ECR supports access using temporary credentials issued by AWS STS. Authenticated access to ECR Public also requires the STS GetServiceBearerToken permission alongside the ECR Public authorization-token permission.
- **[AWS Signer](https://blowstack.com/tools/cloud-services-hub/aws-signer)**: AWS Signer can sign container images stored in Amazon ECR using Notation and the AWS Signer plugin. Signatures are stored alongside the image as OCI artifacts so deployment workflows can verify image authenticity.
- **[AWS Step Functions](https://blowstack.com/tools/cloud-services-hub/aws-step-functions)**: Step Functions can invoke supported Amazon ECR API operations through AWS SDK service integrations. A workflow can start an image scan, inspect its results, and conditionally continue a release or cleanup process.
- **[AWS User Notifications](https://blowstack.com/tools/cloud-services-hub/aws-user-notifications)**: Amazon ECR events can be selected in AWS User Notifications notification configurations through EventBridge event rules. This allows repository activity, such as image pushes or completed scans, to generate notifications through configured delivery channels.
- **[EC2 Image Builder](https://blowstack.com/tools/cloud-services-hub/ec2-image-builder)**: Amazon ECR supplies base images and receives output images for EC2 Image Builder container pipelines. Image Builder can build, test, and distribute versioned container images to configured ECR repositories.
- **[Red Hat OpenShift Service on AWS (ROSA)](https://blowstack.com/tools/cloud-services-hub/red-hat-openshift-service-on-aws-(rosa))**: Amazon ECR supplies container images to workloads running on ROSA clusters. Private repositories can be accessed using ECR authentication credentials configured as OpenShift image pull secrets.

## What is Amazon Elastic Container Registry (Amazon ECR)

Amazon Elastic Container Registry (ECR) is a fully managed Docker container registry that makes it easy for developers to store, manage, and deploy Docker container images. It's integrated with Amazon Elastic Container Service (ECS), but can also be used with any Docker-based application.

Amazon ECR also supports pushing and pulling Open Container Initiative (OCI) images and artifacts, and can translate between Docker Image Manifest V2, Schema 2 images and OCI images on pull.

Amazon ECR eliminates the need for you to operate your own container repositories or worry about scaling the underlying infrastructure. It handles the complexity of managing the storage and enables you to securely store, organize, and manage your containers in a highly scalable and secure environment. Amazon ECR uses AWS Identity and Access Management (IAM) to control access to your containers, ensuring that only authorized users or services can access your images. This tight integration with AWS security model means you can create policies to control access to your images, ensuring that sensitive software stays secure. Additionally, ECR automatically encrypts your images at rest and provides methods to encrypt the data in transit, adding an extra layer of security.

ECR managed signing automatically signs images as they are pushed, using the identity of the entity pushing the image. Image signing lets you verify that images come from trusted sources.

ECR also supports dual-layer server-side encryption with keys stored in AWS Key Management Service (DSSE-KMS), adding a second layer of encryption and decryption.

Basic image scanning has a non-adjustable quota of 100,000 images per 24 hours per account and Region, counting both scan-on-push and manual scans.

A significant benefit of using Amazon ECR is its scalability. It scales automatically to meet your storage requirements, removing the hassle of planning for capacity and managing infrastructure to store your container images. This is particularly beneficial for organizations that may experience variable demand for their applications. With ECR, you can focus on developing your applications rather than managing the infrastructure needed to store and share container images.

The default quota is 100,000 images per repository in each supported Region. This quota is adjustable.

The maximum image layer size is 52,000 MiB, and this quota is not adjustable.

ECR offers two storage classes: Standard, the default for active container images, and Archive, for inactive images requiring long-term storage. Archived images must be retrieved before they can be pulled.

Another key feature of Amazon ECR is its integration with Amazon ECS and Amazon Elastic Kubernetes Service (EKS), which simplifies your development to production workflow. You can easily push your Docker images to Amazon ECR and then deploy them to Amazon ECS or EKS with a simple set of commands. This integration streamlines the process of container management, from storage to deployment, making it faster and more efficient. Moreover, Amazon ECR supports private image repositories, enabling you to securely share container software within your organization or with select partners without making it public. This feature is especially useful for organizations that need to enforce strict access controls and comply with regulatory requirements.

Amazon ECR also offers public repositories, whose images anyone can pull without an AWS account or IAM credentials. Public repository images are available in the Amazon ECR public gallery.

In conclusion, Amazon Elastic Container Registry provides a secure, scalable, and easy-to-use environment for storing and managing Docker container images. Its deep integration with AWS services, such as IAM, ECS, and EKS, alongside features like automatic encryption, private repositories, and highly scalable infrastructure, makes it an attractive solution for developers looking to streamline their container management processes. Whether you're a small developer team or a large enterprise, Amazon ECR offers the tools and security you need to manage your container images efficiently.
