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

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.

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.

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.

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.