Amazon Elastic Container Registry (ECR) Reviews & Product Details

Amazon ECR has become our standard private container registry for storing Docker and OCI-compatible images. I particularly like its seamless integration with ECS, EKS, CodePipeline, CodeBuild, IAM, and vulnerability scanning capabilities. The console is intuitive for managing repositories, lifecycle policies, image tags, and scan results, while the Docker CLI experience remains familiar for developers.

Performance has been consistently excellent with fast image push and pull operations across production deployments. Native integration with AWS services eliminates the need to manage registry infrastructure, and lifecycle policies automatically clean up unused images to optimize storage costs. Pricing is straightforward and cost-effective since charges are based primarily on image storage and data transfer. Amazon Inspector integration also strengthens security by automatically identifying vulnerabilities within container images. Although ECR itself does not include AI features, it integrates naturally with Amazon Q-assisted CI/CD workflows and Bedrock-powered application deployments. Review collected by and hosted on G2.com.

Cross-region replication and repository permission management require careful planning in large multi-account environments. Advanced collaboration features are also less extensive than some third-party container registries. Review collected by and hosted on G2.com.

The integration with rest of AWS ecosystem is what I like the most. We are running our workloads on ECS and EKS, so having the container registry inside same AWS environment makes everything very smooth. Image pulls are fast, authentication is handled through IAM, no separate login system to manage.

The image vulnerability scanning is something I was not expecting to be so useful but it has become part of our regular workflow now. Every time we push a new image, scan runs automatically and we can see if there are any critical issues before deployment. That has saved us few times from pushing problematic images to production.

UI is simple and straightforward. It is not very fancy but for what we need, finding images, checking tags, reviewing scan results, it gets the job done without confusion. My team members who are not very deep into DevOps side, they can also navigate it without much hand holding.

Private registry with fine grained IAM permissions is also very helpful. We have different teams working on different services and we can control exactly who can push and who can only pull. That level of access control was not possible when we were on DockerHub.

The AI and intelligence side of ECR is honestly not very deep. It is mainly a storage and registry service, so do not expect any smart features out of the box.

Overall the biggest benefit is that ECR just works quietly in background without giving any trouble. In our deployment pipeline it is one less thing to worry about, and for a busy engineering team that peace of mind has real value. Review collected by and hosted on G2.com.

Main frustration is the pricing visibility. Data transfer costs and storage costs are not very straightforward to estimate upfront. Few times our monthly bill came higher than expected and we had to dig through Cost Explorer to understand what exactly happened. A clearer cost breakdown inside ECR console itself would help a lot.

Lifecycle policies are useful but the configuration is not very intuitive. First time setting up automatic cleanup of old images, I had to read documentation multiple times to get it right. For something that should be a basic hygiene feature, it should be much simpler to configure.

The console UI is quite basic. Most operations require going to CLI or writing scripts. For team members who are not very command line comfortable, this creates dependency on DevOps person for even simple tasks like checking image details or manually deleting old tags.

Cross region replication took us lot of trial and error to set up correctly for our multi region deployment. Documentation exists but it does not cover all the edge cases we ran into. Support response was also not very fast when we raised ticket.

Error messages during image push or pull failures are sometimes very vague. It will say authentication failed or access denied but not give enough detail to immediately understand what exactly went wrong. Debugging these issues wastes good amount of time.

Overall ECR is reliable service but these rough edges around cost transparency, usability and error reporting need improvement for it to be truly production team friendly without heavy DevOps involvement. Review collected by and hosted on G2.com.

AWS Cloud is scalable , reliable and has massive service ecosystem. It allows you to spin up environments within minutes and automate deployments with cloud formation of terraform and manage infrastructure through a highly configurable IAM model Review collected by and hosted on G2.com.

The pricing structure can be confusing and hard to estimate for complex setups Review collected by and hosted on G2.com.

What I like best about ECR is its ability) to integrate with other AWS services, like ECS, EKS, and Lambda, which makes containerized application workflows smooth. It also provides scalable storage for container images without having to manage the infrastructure. Review collected by and hosted on G2.com.

I felt it was very much less flexible than other registries than Docker Hub, Nexus, JFrog Artifactory. Review collected by and hosted on G2.com.

ECR completely managed by AWS and it is very easy to use Review collected by and hosted on G2.com.

To be honest I haven't seen any dislikes as such. ECR ie going in right direction and is and other registries which are available in market Review collected by and hosted on G2.com.

1. As the name suggests, Amazon Elastic Container Registry is a hub to store images and it seamlessly integrates with other AWS services because of the AWS ecosystem.

2. It provides public, private, and secure image storage options.

3. It also provides versioning options for the image.

4. Integrates with AWS IAM for fine-grained access control.

5. It scales horizontally to store an increasing number of images.

6. It also provides options to delete images after a specific amount of time, which saves a lot of space and billing.

7. Provides private repository options which ensure secure access to images by user and service only. Allows tagging options.

8. Amazon Container Registry works really well in CICD implementations as it integrates really well with lots of CICD tools.

9. Overall, it is very easy to use. Review collected by and hosted on G2.com.

1. I dislike that AWS ECR is region-specific and if we need to implement a multi-region deployment, we need to make a copy of the image in all those regions.

2. There is one issue that we faced: there is a limitation to the number of layers in a Docker image. If we need to store large images, then it is difficult.

3. Also, the costing is complicated as it depends on the size of the image and the number of times it is accessed. Review collected by and hosted on G2.com.

Scalable solution best cloud and nice service Review collected by and hosted on G2.com.

Costly but need to improve to other regions Review collected by and hosted on G2.com.

As it's from AWS and AWS already has a powerful EKS (Elastic k8s service) which works really well with ECR for storing the container images and allows building and deploying the application in an easy manner. Its time-based deletion policy helps you delete and save the cost of storing the images in ECR. It has good AWS CLI support and documentation to download and upload images to ECR as well as perform other operations. It supports both public and private repositories. Review collected by and hosted on G2.com.

Although it supports public repositories to host public images, it is still not as widely adopted as Docker Hub. Sometimes it's slow, especially when you want to download and upload images from locations far from its hosted repositories, which is the case for most distributed development teams. Review collected by and hosted on G2.com.

Amazon ECR is one of the best Docker container registry I have been using as an option to store any type of docker images for my project. It easily integrates with other resources of AWS ecosystem for eg Amazon Elastic container service,Amazon Elastic Kubernate service etc. Its highly scalable so I can store any number of docker images without worrying about storage space.While pulling the docker images from registry its very easy and reliable and having very low latency. Review collected by and hosted on G2.com.

ECR is a pay as you go service, so I have found it little bit costly and risky for newbies for storing large number of images without having any idea of the total bill.Also pulling the images from ECR through cli is little bit complex. Beside these there is nothing such to dislike about ECR. Review collected by and hosted on G2.com.

It is very helpful for integration with amazon services like ec2, ecs and eks. It helped me in building custom images that was used by eks cluster where the implementation was easy as the deployment only needed appropriate access to the ecr image. Review collected by and hosted on G2.com.

That compared to other cloud platforms like azure ACR (az acr import command), it does not have a feature to import/copy the images from docker hub to ACR. One need to login to docker, pull the image to local, then login to ecr and then push it to the registry which i feel might be great if there is a single command to achieve this. Review collected by and hosted on G2.com.