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.

My current company uses monolithic and microservices architecture based on customers' wants or needs. My company's usage of Docker is now limited, and I have full permission to use Amazon ECR.

What I like most about Amazon ECR is that it's swift.

One area for improvement in Amazon ECR is its complexity. It's pretty complex for newbies, particularly learning about private repositories, including how to access Amazon ECR through AWS Identity and Access Management (IAM). However, after your hands-on as a newbie, it becomes easy to use Amazon ECR.

Amazon ECR also lacks documentation that would make learning easier for newbies. I have to teach others about IAM and its purpose, how to use it, and the access key to access private images in Amazon ECR.

I want Amazon ECR to integrate with other repositories and cloud services. For example, I should be able to see the containers and images uploaded to the containers. I should see uploaded images to Docker, Azure Container Registry, etc. because that would make it easier for me to select the images for deployment. That's the feature that would be most useful for developers.

I've been using Amazon ECR since July 2022. I'm even using it today.

Amazon ECR is stable, with no downtime so far. This is also the case with Azure Container Registry. Stability-wise, Amazon ECR is top-notch, and I can say the same for Azure Container Registry.

Amazon ECR is scalable, but my company is currently in the POC stage on the pay-as-you-go plan, so it has limited users. Currently, this scale is sufficient for my company for Docker and Kubernetes architecture.

I have yet to contact the support team for Amazon ECR.

My company uses both Amazon ECR and Azure Container Registry, and I can see the difference. Amazon ECR is very fast. It's five or six seconds faster than Azure Container Registry, so I recommend it.

The company uses Amazon products, so it had the idea to use Amazon ECR. My company also found Azure Container Registry more costly than Amazon ECR.

Amazon ECR has a straightforward setup, plus Amazon has a guide on how to create, upload, pull and push, etc. There's also a guide on commands, which makes the tool easy to set up.

The deployment time is wholly based on the docker image size and the location. For example, the pulling and pushing time takes longer if the docker image is greater than 2 GB or 3 GB. Including the Docker push and pull, and the Kubernetes cluster run, deployment takes about five to six minutes. If the docker image is below 500MB, the deployment time would only take two minutes.

My company currently has Amazon ECR under the pay-as-you-go model. The tool is more affordable than Azure Container Registry, and it's worth the money.

My current project has six Amazon ECR users, primarily two developers, and four cloud engineers.

Before jumping into Amazon ECR, you must have a strong understanding of IAM, what Docker is, and how a container registry works, mainly how it stores artifacts and images, including how you can access Amazon ECR through IAM policies. Most people who jump right into Amazon ECR without the required knowledge usually face deployment issues caused by IAM policies, denied permissions or authorizations, etc., mainly because most companies use private container registries for security purposes. If you're concerned about security, you should first learn about IAM and role-based access policies.

With my recent experience using Amazon ECR, I can rate it ten out of ten. I haven't faced any single issue or downtime from it. I'm delighted with the service.

My company is an Amazon ECR customer.

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.

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.

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.

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.