Amazon ECR Reviews

The solution is also used for managing containers and is integrated into our overall application hosting environment. It helps us store and manage Docker container images for our applications.

The platform's most valuable features are its elasticity and responsiveness. It is well-integrated with AWS services, and the quick turnaround time for support tickets is particularly notable. It helps in maintaining the smooth operation of our containerized applications.

The UI for managing ECR and other services could be improved. It could be user-friendly compared to other cloud services.

I have been working with Amazon ECR for approximately four to five years.

The platform consistently performs well. On the rare occasions when there are glitches, we are promptly informed. Notifications and updates are sent via email to all users of the services, ensuring that any issues are quickly addressed.

The platform is scalable. The continuous improvements across various services are commendable. The introduction of artificial intelligence has been particularly beneficial, with several of our teams leveraging AI and machine learning technologies. The automation capabilities embedded in each service are outstanding, allowing us to utilize tools such as Terraform to automate and streamline our operations effectively. Overall, the scalability and its AI and automation features significantly enhance our operational efficiency.

The technical support services are excellent. 

Positive

The setup process is simple, but the user interface could be improved for better management.

The product is expensive. 

I rate Amazon ECR an eight out of ten. 

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. 

We use Amazon ECR to deposit and retrieve images. We rely on it for CodeBuild instances and EKS, getting images for our use cases. Every image stored in ECR is versioned, allowing us to roll back if needed. My role involves managing as a platform manager.

Amazon ECR has been valuable in handling and storing images, ensuring they are scanned internally and providing a reliable container registry service.

The main feature I value is the ability to deposit and retrieve images. We use Amazon ECR for storing and retrieving code build images or those for EKS parts. Each image is versioned, which helps in managing different versions effectively.

There were some initial connectivity issues, especially when accessing ECR from our on-prem setup. It had to connect via the VPC or use some means to access it externally. Simplifying the interface or easing the deployment process would be beneficial.

We have been utilizing Amazon ECR for a few years now.

Amazon ECR delivers what is expected in terms of availability.

The technical support is generally good, but I felt the support team might lack hands-on experience with different organizations' infrastructure.

Neutral

We initially used a local repository for storing images before moving to Amazon ECR. We did not use Docker Hub or any external cloud solutions.

The initial setup involved addressing connectivity issues and ensuring ECR worked within the VPC.

We use many tools internally and work closely with AWS. Specifics about an external implementation team are not mentioned.

For anything on AWS, a native solution with APIs would be preferable.

I'd rate the solution eight out of ten.

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.

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.

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.