Amazon ECR Reviews

Currently, I work primarily with AWS-related services, but not much that is new at the moment. I handle the same tasks regularly.

Other than EKS, I normally work with AWS services such as AWS EC2, S3, and related services.

For all Docker-based applications, we need to use Amazon ECR. Wherever we use containers, we use Amazon ECR.

Amazon ECR functions as part of the software development process. Before an application gets released, it has to be built from somewhere, and that location is Amazon ECR.

The most valuable feature of Amazon ECR is that we can push and pull faster than other similar products.

It means saving and retrieving more efficiently.

This is not manual dragging and dropping, but rather programmatic taking and saving.

I have used Amazon ECR with Lambda, EC2, and EFS. These are integrable services where you can call Amazon ECR from anywhere in AWS.

If my product is not always dependent totally on Amazon ECR only, but if the product is dependent on Amazon ECR only, then having a low time to load, low time to save, and a faster containerizing process time would affect the software's response time. This is important.

If Amazon ECR had CI/CD also integrated into it, then it would probably be better.

I have used Amazon ECR for around four years.

I don't recall right away, but I don't think there was too much latency with Amazon ECR. It is still fast in my view.

Amazon ECR is a reliable solution.

I think Amazon ECR is very scalable. I haven't had an instance of not being able to use it or it being slow. It can be scaled depending on the solution.

I'm happy with the integration quality; we can say it's good.

Neutral

I usually don't use the Amazon ECR interface at all; I do it all programmatically.

It is straightforward. Normally, you just need to create a repository and once the repository is created, you just need to use the proper policy and then the proper authentication mechanism to save and retrieve the data from there.

I don't have an exact idea of the cost related to Amazon ECR at this point, but I think these are cheap solutions compared to what we have to pay for other products in the market.

I can provide more detailed feedback if you send me the links to what I'm taking feedback on, and if I have the time available. That would be a better approach.

Those are the main things at the moment. The others are about Amazon ECR.

I think the storage cost is not that much affected by Amazon ECR because once we update something on the container, it will replace the original version. This doesn't affect the cost much in that matter.

For me, that is not a matter of consideration that much.

I have used the documentation provided by Amazon ECR, but only the very basic ones that are available in AWS itself.

The documentation is to the point, and I think for starting up and then setting up and using it, the documents are enough.

For me and my use case, those are sufficient. However, if somebody is working purely in great depth, then they may require some more resources. For me, they are already enough.

Amazon ECR is available in all regions.

I haven't had any issues with availability with Amazon ECR, but I usually, being in Finland, use the Ireland region, and it is available almost always. I have no issues with the availability of the service.

My overall rating for this review is 8.

The main use case for Amazon ECR is that whatever containerized image we are building will be pushed to Amazon ECR, and then it will get deployed into a Kubernetes cluster.

I appreciate that if my deployment is on Azure, I use ACR, and if my deployment is in AWS, I put all my containerized images into Amazon ECR, and then my DevOps pipeline takes that and gets deployed into the cluster.

Amazon ECR is a repository where you build the image and put it there.

Amazon ECR image scanning is very good.

Integration with other AWS services in CI/CD workflows is very good.

The lifecycle policies of Amazon ECR help manage storage costs in my project by maintaining version control over the containerized images that we are keeping there. It functions as a common repository area that can be used in multiple deployments, and version control can be maintained rather than keeping it local, which is a valuable portion of Amazon ECR.

The main benefits Amazon ECR provides include maintaining version control of the containerized images we are creating, which is a strong point, and it makes deployment to the cluster easy.

For potential areas of improvement in Amazon ECR, I need to check if AWS has features similar to Azure Defender for scanning, getting vulnerabilities, and patching recommendations.

Regarding additional functionality, it would be great to see auto-scanning and providing vulnerability assessment data in the next version of Amazon ECR. It would also be beneficial if patched versions could be updated automatically, specifically regarding a clean images feature that could be added when putting images into the repository.

I have been working with Amazon ECR for almost seven to eight years.

When it comes to stability, I would rate Amazon ECR as very good and would give it a nine.

As for scalability, I would rate Amazon ECR eight or nine for its ability to scale and expand.

I would rate Amazon technical support very high because their support team is very good. I can give it a nine or even a ten because many times when we raise issues, they immediately connect and share the architecture and reference architectures, which is very good for AWS.

Positive

The setup process for Amazon ECR is very simple.

When it comes to pricing for Amazon ECR, that is the only area AWS has to look into. Services like IoT services or SageMaker are very high, and many times customers complain that while the initial pricing is good, later the cost becomes too high to use AWS services. All hyperscalers have that problem, and specifically for AWS, they are good in the market, but they need to think about how to reduce customer costs in the long run.

I do not see any competitors on the market for Amazon ECR. I am actually using Azure, where ACR is available.

In comparison to Amazon ECR, it depends on the cloud provider. If your deployment architecture is fully in AWS, then it is better to go with Amazon ECR, which is how we are using it right now, but I did not compare with other products as all are registry options and just repositories to store images.

In comparison with Azure, Azure has one good point about Azure Defender, but I need to identify if AWS has anything equivalent to that.

Amazon ECR availability is good as we have used it across different global regions.

The solution is totally deployed on AWS cloud.

Generally, I would give AWS an eight to nine, which is very good, and I rate Amazon ECR a nine.

I would definitely recommend Amazon ECR to other users. I give this review an overall rating of nine.

Our solution serves as an image repository for container images. We utilize two regions, including Eli Orlando, and follow a shared strategy. We maintain two large ECRs and repositories for each application. We push images into these repositories and pull images from the EKS and QM clusters.

ECR is reliable, however, I don't consider it the best container registry available. The main reason is that it is not entirely based on the original Docker registry. For instance, I prefer Azure's ACR because, in ACR, there is no need to create repositories; I simply push. Logging into the repository and specifying the path automatically creates everything. This structure resembles an S3 setup with a container registry layout.

I suggest making it more aligned with the Docker registry version two API specification. If they achieve this, it would be excellent. Eli is an example of such an implementation.

I have been using the solution since 2018.

There are no issues. The service is remarkably stable. It's rare to see the registry experiencing downtime unless perhaps AWS itself is completely down. The service operates without even a minor hiccup.

The service is highly stable. Our container registry would remain operational unless AWS itself experiences a complete failure. The service does not encounter any hiccups.

The setup involves provisioning and immediate usage. Typically, it requires configuration concerning roles and RBAC. Apart from these details, there are no major complications.

In the ECR setup, we use a container registry per region. All accounts are within a shared account, which we call a shared account. We share the container registry across various accounts within our landing zone. It forms a part of our landing zone.

ECR, also known as Azure Container Registry, is an option.

The primary requirement is to create repositories before usage. Unlike a typical container registry where I provision and start pushing content, I need a predefined repository in this case. The repository acts like a sub-registry, providing a private registry for that specific repository. 

Given these insights, I would rate the solution as eight out of ten.

We have been using a couple of products, but mainly AWS managed services. These include AWS API Gateway, Amazon SNS, SQS, Amazon S3, Amazon RDS, AWS Lambda, and serverless services like containers. We use Amazon ECS with Fargate and Amazon ECR for container orchestration as we have been using Docker containers.

Amazon ECR has a native integration with all AWS services, making it convenient for use within the AWS ecosystem. It is managed by AWS and includes robust security features. 

The ability to store Docker images in ECR allows for seamless deployment with AWS templates. Amazon ECR supports deployment across multiple regions and provides high availability.

There were a few issues related to the roles, policies, and retrieval of data when trying to fetch images for deployment on Amazon ECS. This can involve permissions and configuration complexities.

We have been using the solution for the past two to four years.

Amazon ECR supports scalability through its native AWS integration, allowing deployment in single or multi-region architectures to ensure high availability.

The support team is good, though my interactions have been limited. Other teams interact directly with the support team for cloud-related issues. I've heard good feedback, and if I had to rate them, it would be somewhere between seven and eight out of ten.

Neutral

The setup process is straightforward, especially with AWS-native services. Deploying Docker images to ECR integrates well with the AWS environment.

Pricing varies based on the architecture and services utilized. AWS provides tools like a pricing calculator to manage costs. Serverless architecture can reduce costs, while services like Amazon ECS, if running 24/7, can incur more expenses.

I recommend using AWS services for their availability, scalability, performance, and observability. Understanding which services to use and transitioning to cloud-native architecture can enhance cost-effectiveness.  

I give ECR a rating of seven out of ten.

ECR is used as a container registry where we store all our Docker images. We build the pipeline using GitLab, which has a stage called the image build for Java, Python, and Golang-based images. These images are then pushed to the repository in ECR to deploy them in clusters.

What I like is that it is easy to use compared to other container registries. In a click, you are able to store your images and version them as well. You can push and pull images anytime, and it is easy to use. 

Additionally, it offers encryption of the image address using AWS KMS and access control through AWS IAM policy, ensuring high security. The high availability helps ensure the reliability and scalability of the container image storage. It offers image scanning to identify vulnerabilities in container images using Amazon Inspector, and it can be used for microservices deployment to store and manage Docker images for microservice architecture. 

Many companies are switching to microservice architecture rather than monolithic architectures. It integrates perfectly with Jenkins, GitLab, and AWS CodePipeline, offering hybrid deployment and pay-as-you-go pricing.

Improving the image scanning would be great since security is always a big deal. Providing more ways to scan the image integrated with ECR would enhance security in the software development life cycle.

I have been using ECR Elastic Container Registry for over four years.

I have not really encountered stability issues with ECR as long as I tag the image properly and give the correct image repository name.

The high availability ensures reliability and scalability of the container image storage.

They are doing a great job, however, there is room for improvement. We had an issue with AWS Kinesis regarding data storage and pricing. When I reached out, the response time was not very prompt, causing delays.

Neutral

I haven't really been involved with the billing as there is another team that deals with AWS billing.

I would advise them to go through the AWS documentation as it is very helpful. Additionally, attending their virtual conferences, workshops, and training could be beneficial. I rate Amazon ECR eight out of ten.

As a portfolio-based venture capital company, the primary role of Amazon ECR is storing container images. We previously stored images in Docker Hub, but due to security concerns in the market, we now use ECR. We deploy using a serverless architecture model with the help of Kubernetes or ECS Fargate, or any kind of Lambda function to connect deployment perspectives and store Docker containers.

Amazon ECR has provided us with efficient management and deployment of container images, enhancing security features and offering high availability and redundancy. It has optimized our operations by allowing focus on application performance rather than infrastructure management, resulting in a positive return on investment.

The integration of Amazon ECR with various AWS services, such as Elastic Kubernetes Service, AWS Lambda, and ECS container service, adds significant value. 

ECR provides robust security features, including image scanning and vulnerability assessment, supported by AWS identity and access management for fine-grained access control. 

It also offers 99.9% stability and cross-region features along with the ability to create public and private repositories.

Real-time alert mechanisms need improvement, as current custom mechanisms are inadequate. Deeper integration with other security tools would enhance usability. 

Additionally, an intuitive user interface, expanded searching and filtering features, and a more detailed cost breakdown system could benefit users.

We have been using the solution for more than six years.

The solution has a high level of stability, providing ninety-nine point nine nine nine percent availability and data durability. There have been no outages or issues, and its seamless redundancy assures consistent operation.

Amazon ECR offers excellent scalability by automatically handling loads. Its infrastructure burden is minimized with scalable storage and processing. Redundancy across multiple availability zones ensures high availability, allowing seamless scaling to meet heavy user demand.

Technical support is highly responsive and available through various communication channels, depending on the support agreement with AWS. Their assistance follows the SLA timeline effectively.

Positive

Previously, we used Docker Hub for containerization. We switched to Amazon ECR to ensure our images remain within the AWS ecosystem for better security and operational efficiency.

The initial setup was straightforward, with options like a free trial to explore features. Through the AWS console and IAM policies, integration with ECR is user-friendly. The CLI and SDK make repository creation and image management efficient.

One person is required to manage Amazon ECR effectively within the company.

We have experienced a positive return on investment due to enhanced efficiency in deployment and container management, along with robust security features.

Amazon ECR is cost-effective and I'd rate it nine out of ten in pricing satisfaction. However, more detailed cost analysis could enhance user experience in tracking expenses.

Evaluate image sizes for storage cost implications and understand potential data transfer fees. It is crucial for the team to be knowledgeable about AWS services to fully leverage their capabilities.

I'd rate the solution eight out of ten.

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. 

Amazon ECR is a solution for storing Docker containers and images I create. It's like an AWS version of Docker Hub, where I can store as many Docker containers as I need for any application and use these Docker images whenever I want. It also integrates with CodeDeploy. If there's a new commit or changes in the repository, the tool automatically updates the Docker images with these changes. So, I don't have to update them manually; it's all automated.

I use the solution with ECS because it supports auto-scaling. I configure auto-scaling groups to scale when traffic increases horizontally. It automatically creates new tasks and instances to handle more traffic. It also scales down when traffic decreases.

The autoscaling functionality is the main beneficial feature of Amazon ECR. It simplifies management, but some configurations can complicate things a bit.

If there were a way to use containers as tasks directly, that would simplify things. Currently, when we use EC2 instances, scaling horizontally means increasing the instance count by five times, which might not be cost-effective. Maybe using containers directly for tasks could be a better option.

Setting up this product initially does take quite a bit of time, and maintaining it also requires effort. Doing it via command line would be challenging, so I find it easier to manage through the interface.

The solution is stable, and I haven't faced any issues. 

I rate the tool's scalability an eight out of ten. 

AWS is amazing in terms of support. 

Positive

Regarding ROI, Amazon ECR is another option for container orchestration. It helps reduce development time, but since I'm the only one handling it on the team, it does require a significant time investment.

The main difference between Amazon ECR and other solutions, like Google Kubernetes Engine, is that I haven't personally used GKE. However, I know that GKE costs around $60 per month, which is quite cost-effective.

I rate the overall product a seven out of ten. 

Positive

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.