Share your experience using Amazon ECR

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