Amazon ECR Reviews

We use the solution to manage microservices. 

The solution is straightforward to use.

The solution's support for system architecture could be better. Also, there could be specific training module videos included. It is time-consuming to refer to YouTube videos to figure out the solution's architecture.

The solution is very stable. It is well established within the AWS environment. I don't have to maintain the servers as well.

The solution is very scalable. It can handle as many containers as required.

The solution's initial support is good. I rate it an eight out of ten. At the same time, its support for system architecture needs improvement. It needs to include highly skilled executives for it. I rate it a seven out of ten.

The solution's initial setup process is simple. It takes a couple of minutes to complete and requires only one executive. I have to maintain the source code of the backend to generate containers for it.

The solution's price is reasonable compared to Google and Azure.

I evaluated Azure and Google platforms. In comparison, Amazon ECR is better in terms of all the features and support services they offer.

I rate the solution a ten. It is easy, reliable and well-integrated into the AWS infrastructure.

We use the solution for multi-architecture and microservices applications. We must create a Dockerfile for applications and build the image using Dockerfile. After that, push this Docker image on Amazon ECR, using AWS CI/CD and building processes. 

One feature of Amazon ECR that I find particularly useful is its web interface, which makes management easy. The ability to manage and support token image updates is crucial for us. Moreover, utilizing load balancers via AWS features allows us to manage all traffic. 

There are multiple roles, such as AM roles, security groups, etc., to improve security. We can get AWS-friendly dashboards. 

Amazon ECR needs to improve its downtime. 

I have been using the product for four years. 

I rate Amazon ECR's stability a nine out of ten. 

By creating multiple replicas of a service, such as the front end, running on different Docker images, we can easily increase the number of replicas from, for instance, four to five. This scaling process ensures there is no downtime. It is similar to Kubernetes ports.

I rate the tool's scalability a nine out of ten. Our organization has around ten users who manage and create resources like Amazon ECR. The number of users accessing ECR can vary, with some months experiencing heavier usage, particularly for e-commerce websites with heavy traffic. In contrast, other websites, like school websites, may have limited users.

I haven't contacted technical support since we can manage the tool ourselves. 

The tool's deployment time varies depending on the application and source code. Typically, it can take five to ten minutes for Docker images to be deployed. The duration largely depends on factors such as the size and complexity of the Docker images. It is easy. 

I rate the overall product 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 Amazon ECR to store images about containers. In general, I use ECR from the command line.

The most valuable feature is that Amazon ECR is very simple and useful. It is easy to use, and anyone can use it.

There could be improvements to the interface of AWS concerning ECR. It is not a very good interface.

I have been using Amazon ECR for two or three years.

I did not have any problems with the stability of Amazon ECR. It is very stable.

I did not have any problems with ECR in general and did not need to contact their customer support.

Positive

The pricing of Amazon ECR is cheap. It is very affordable.

I advise other people that Amazon ECR is very simple to use and is cheap.

I'd rate the solution eight out of ten.

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.

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 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.