Amazon ECR Reviews

I use Amazon ECR for the containerization of different applications to be deployed. Using Amazon ECR is one of the best ways to deploy architecture, as it reduces development time and increases output. Amazon ECR is very flexible.

The most valuable feature of Amazon ECR is how it organizes the code and the infrastructure. It's dedicated to shipping out applications faster, and you don't have to depend heavily on third-party providers to get the work done.

A lot of documentation is very beneficial for command-line tools like Amazon ECR. Improving the documentation for easy understanding will help bring in more clients to use Amazon ECR.

I have been using Amazon ECR for one year.

If you do not have a good, knowledgeable team to back you up, you can cause your company to lose a lot of money. Amazon ECR needs a whole team to manage it, especially when deploying a very complex application.

I rate Amazon ECR an eight out of ten for stability.

I rate Amazon ECR a nine out of ten for scalability.

The solution's initial setup is easy on the web interface but complex on the command line. You need to have prior experience in working with Docker in order to get the container set up.

The solution's deployment doesn't take that long. The deployment time depends on your internet latency. If your internet is slow, the deployment will take more time.

Users should have good knowledge of Docker and understand the whole concept of containerization when deploying different applications. Even though it may have a complex architecture, they would get it done because Amazon ECR's web interface is pretty straightforward.

Overall, I rate Amazon ECR a nine out of ten.

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.

If you are in an AWS environment and running a Kubernetes cluster, Amazon ECR is very easy to use.

The integration with AWS services is very easy, and the deployment and initial setup are pretty straightforward.

Ease of use and no configuration required make Amazon ECR very easy to use.

There is no room for improvement mentioned; it's good as is.

There are no issues with the stability while using ECR.

Amazon ECR is pretty scalable.

The support is great with Amazon.

Positive

The initial setup is pretty straightforward.

The pricing of ECR is average compared to its competitors.

If they are in the AWS tech stack, I definitely recommend Amazon ECR.

I'd rate the solution nine out of ten.

We use ECR to host file images for our products. We are working on a few in-house products related to GenAI and agentic application. For any website or application that we're creating, we create Docker images for that.

Having a place where we can store or host our images on the same platform as our primary infrastructure is very beneficial for management, cost management, and privacy.

The Docker compatibility that ECR offers is probably the most beneficial aspect of this solution. Docker is one of the most popular platforms for containerization, and having compatibility with that is significant.

The documentation could be improved, and I would say this about all AWS services. Even though AWS covers pretty much every use case there is for a particular product, the documentation for these services lacks in some way. Additionally, they could offer backwards compatibility to other containerization platforms and maybe provide legacy support.

It's just been a month since I got familiar with ECR.

I've never had a problem with ECR. It hasn't given me any downtime, availability issues, or reliability issues since I've been working with it.

Our DevOps engineers handle scalability, so I haven't encountered any issues.

While I have not used customer service for this particular service, I have used AWS support for a few other services.

Positive

Before ECR, for my personal projects, I used to go with Docker Hub.

The initial setup was pretty straightforward. The AWS console itself is a wonderful tool to access AWS services, and that has never given me any problems either.

There is a team that handles the maintenance.

I haven't explored setup costs a lot. So far, it's not very expensive to host images on ECR.

Any user who is going for this particular service should first look into the cost and analyze the cost inflicted on their account for their use case.

I'd rate the solution nine out of ten.

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.

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. 

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.