Amazon ECR Reviews

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.

Today, I am a solutions architect working for a Brazilian company. We generally work with ECS, application load balancers, Lambda, WAF, Shield, and GuardDuty. We also use databases like RDS and Aurora for both NoSQL and SQL environments and SageMaker for AI. 

I utilize ECR to register my images when deploying to ECS. Usually, I conduct a lot of proof of concept work, and that's why I use it to make my pipeline to demonstrate to future clients how to deploy a Docker ECS infrastructure.

The ECR solution is good. It is integrated with AWS, and it's free. Everything is free, which makes it nice to use. 

Since I hosted my image in ECR, it stayed there for my project until deployment, with no charges incurred for storage during that period. This makes it a cost-effective option, especially useful when making images private without added costs.

If I could use less code and have more of the user interface provide predictions of the coding required in my CLI or Terraform, that would be nice. This would reduce the time spent searching for information and expedite the deployment of my ECR images using my setup.

I have been working with ECR for the past six months.

There were no downtimes or performance issues with Amazon ECR.

I have not tried to scale it. My process is straightforward and simple.

I haven't had to escalate any questions about the ECR product specifically. My experience with AWS's basic support has been positive; they were prompt and precise, helping me with other issues.

Positive

I use either Docker Hub or ECR to manage images.

The initial setup involved pushing my image using the CLI to the cloud, which was complex and required checking the documentation. A tunnel was needed because my services were global, while my Docker images were private, adding complexity.

When using ECR, pricing is not an issue for me, as it does not charge for private images, unlike other services.

I recommend ECR to companies aiming to keep images private without incurring costs. Money is a big issue in cloud economics, and ECR is cost-effective.

I'd rate it eight 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.