Amazon ECR Reviews

Our complete DevOps pipeline is set up, and the images are pushed through that to Amazon ECR.

The most valuable feature of the solution is the scanning of images for vulnerabilities.

Amazon ECR should include integration with Docker Hub.

I have been using Amazon ECR for three to four years.

Amazon ECR is a stable solution.

I rate the solution’s stability a nine out of ten.

The solution's initial setup is simple.

The solution's pricing depends upon the region. The solution's prices are high in India as compared to the US.

Amazon ECR is well integrated with other Amazon products. Amazon ECR is deployed on the cloud in our organization. I would recommend the solution to other users. Amazon ECR is a mature product that is quite well integrated with other services. Amazon ECR's smooth integration allows you to use it quickly in your workflow.

Overall, I rate the solution a nine out of ten.

I'm using Amazon ECR to deploy our images on the ECS platform.  

In the case of Amazon ECR, there are various valuable features we can see. Currently, there are image-scanning capabilities that we use. We push Docker images to our ECR repository; then, the scanning process takes place. We also have the option to choose between private or public repositories. So, there are basically four to five functionalities, and we use all of them.

The user interface is quite good, and it is very user-friendly.

The solution provides us with image scanning. It would be great if they can also provide a reference to fix the errors or vulnerabilities in the images rather than just notifying us about them. For example, they just provide us with the issue only. But in case they provide us a way to fix the issue directly, that will be a good addition.

I have been using this solution for a year. 

I haven't faced any scalability issues until now, so I would rate it ten out of ten.

Over 15 resources are working on ECR itself. These users are responsible for deploying their code to ECR, and from there, the code is further used in services like Amazon EKS or Amazon ECS based on specific requirements.

It's quite straightforward. The initial setup will take nearly about one hour only. We just create a repository and then we deploy the code in there. Less than one hour could be enough.

The deployment was done in-house. We make use of Jenkins for Continuous Integration/Continuous Deployment (CI/CD) to build and deploy our images to Amazon ECR.

It's not that expensive. We just have to store the image there, and the cost is based on monthly storage. For storing around 200 to 300 megabytes per month, it costs around $10 only, so it's not that expensive.

I would rate it ten only because we didn't face any challenges. The user interface is smooth and straightforward, so there are no issues with the solution.

I would say that it's an excellent platform, just like Docker. It provides us a way to store and manage our container images. Moreover, it easily integrates with other AWS solutions. So if someone is already using AWS solutions, Amazon ECR is the best way to go.

I use ECR as a service that stores and manages container images.

My primary use case for CloudFormation is for the automation of infrastructure.

The most valuable aspect of ECR is its user-friendliness.

I like CloudFormation for its simple language. It also has a very good graphical interface for diagramming my infrastructure.

The Amazon ECR interface could benefit from improvements to enhance user experience.

CloudFormation has a learning curve.

I have been using ECR for almost three years.

I have been using CloudFormation for two years.

I would rate the stability of ECR ten out of ten.

I did not have any problem with the stability of CloudFormation.

If I need to use different clouds, for example, GCP and AWS and Azure, I prefer to use Terraform.

The deployment of ECR is straightforward.

The price of Amazon ECR is cheap.

I would rate ECR ten out of ten.

My advice about ECR is that it is very simple to use and is cheap. 

While CloudFormation is useful for managing resources exclusively within AWS, Terraform is a more versatile choice when working with a multi-cloud environment, such as AWS, GCP, and Azure.

The most valuable feature of Amazon ECR is its ease of use and the centralized management console.

Amazon ECR should improve the integration with Amazon CloudWatch. For example, allowing us to monitor the queues better. Additionally, some of the features could be made more accessible. 

I have been using Amazon ECR for approximately two years.

Amazon ECR is highly scalable, it is one of the main features.

There is no setup for Amazon ECR it is ready to use being in the cloud.

I rate Amazon ECR a ten out of ten.

Amazon ECR helps to centralize our Docker images in one place, which is very useful to us. It helps to store our images in a private repository and connect with other products in AWS. 

The most tool's valuable feature is image scanning. 

Amazon ECR's manipulation capability of tags needs to be improved. 

I have been working with the solution for seven years. 

I rate the solution's stability a ten out of ten. 

I rate the product's scalability a nine out of ten. 

We were using an on-prem solution and needed to move to the cloud. Our first option was Amazon ECR since we were an AWS customer. 

Amazon ECR's deployment was easy. 

We have seen ROI with the tool's use. 

Amazon ECR does not have a high cost. 

You must pay attention to resource quotas such as tag and image limits. I rate the solution a nine out of ten.